This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
|Summary:||Project level license header is ignored when using the implement interface function|
|Component:||Completion & Templates||Assignee:||Dusan Balek <dbalek>|
|Severity:||normal||CC:||brettryan, lvaills, tkellerer|
|Issue Type:||DEFECT||Exception Reporter:|
Description IrianR 2015-07-14 14:20:07 UTC
[ BUILD # : 201507040001 ] [ JDK VERSION : 1.8 ] STEPS: * Open a java project with custom license header set * Create a brand new Interface * Select the interface name and click on the light bulb to show suggestions * Select the suggestion to implement the interface ACTUAL: When creating the new interface the custom license is correctly applied. When creating the implementation the default License is applied. EXPECTED: In both cases the custom license should be applied.
Comment 1 Dusan Balek 2015-07-16 12:46:21 UTC
Fixed in jet-main. http://hg.netbeans.org/jet-main/rev/ce4cda7683f5
Comment 2 Quality Engineering 2015-07-18 01:46:54 UTC
Integrated into 'main-silver', will be available in build *201507180001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/ce4cda7683f5 User: Dusan Balek <email@example.com> Log: Issue #253466 - Project level license header is ignored when using the implement interface function - fixed.
Comment 3 IrianR 2015-07-21 09:02:25 UTC
I've tried to verify this in build 201507200001, but it seems that now the project level license configuration is ignored even for new classes. I've tried selecting one of the already existing global licenses, and also specifying a project level license file, but none gets picked up. During the test I've encountered an exception: http://statistics.netbeans.org/analytics/exception.do?id=786285 but I've got it only once so I doubt it's related.
Comment 4 brettryan 2015-08-17 09:18:32 UTC
*** Bug 254410 has been marked as a duplicate of this bug. ***
Comment 5 brettryan 2015-08-17 09:20:50 UTC
I can verify this IrianR's last comment. Creating a new class does not use project specific templates. Note that my tests are with maven projects.
Comment 6 IrianR 2015-08-17 09:30:48 UTC
(In reply to brettryan from comment #5) > I can verify this IrianR's last comment. Creating a new class does not use > project specific templates. > > Note that my tests are with maven projects. It appears this has been fixed in the latest dev builds, just verified in Build 201508160002.
Comment 7 brettryan 2015-08-17 09:33:30 UTC
Thanks Irian, just waiting to get home to switch from beta to dev builds.