[ BUILD # : 201507040001 ]
[ JDK VERSION : 1.8 ]
* 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
When creating the new interface the custom license is correctly applied.
When creating the implementation the default License is applied.
In both cases the custom license should be applied.
Fixed in jet-main.
Integrated into 'main-silver', will be available in build *201507180001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Dusan Balek <email@example.com>
Log: Issue #253466 - Project level license header is ignored when using the implement interface function - fixed.
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:
but I've got it only once so I doubt it's related.
*** Bug 254410 has been marked as a duplicate of this bug. ***
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.
(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.
Thanks Irian, just waiting to get home to switch from beta to dev builds.
*** Bug 254830 has been marked as a duplicate of this bug. ***