[jbosstools-issues] [JBoss JIRA] (JBIDE-18135) License header plugin

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-18135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996097#comment-12996097 ] 

Max Rydahl Andersen commented on JBIDE-18135:
---------------------------------------------

suggested implementation is to add custom variable resolver like shown at http://web.archive.org/web/20100414054049/http://dev.eclipse.org/blogs/jdtui/2007/12/04/text-templates-2/ and http://thomaswabner.wordpress.com/2009/08/21/use-your-own-variable-in-eclipse-code-templates/ that would insert the right license based on context.

i.e. 

${license} would locate nearest LICENSE.header in the filesystem (even beyond the project root since it might be in a multi-module project) and insert its content.

Could also take argument to control the file: 

${license:java.license} 

note: This file would then need to have the proper comment syntax already applied (unless we make a ${comment:${license}} that would handle comments dynamically based on file type.
 

> License header plugin
> ---------------------
>
>                 Key: JBIDE-18135
>                 URL: https://issues.jboss.org/browse/JBIDE-18135
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>            Reporter: Kabir Khan
>
> In WIldFly we have split out the core from the EE part of the project, and there is a plan to relicense the core. I and others who work on WildFly using Eclipse seem to like having both the 'core' and 'EE' projects open in the same workspace. once the relicensing has happened, it will become problematic to maintain the licenses in the mixed workspace.
> We would like to be able to configure some code templates adding the 'core' licenses when a new file is added to the 'core' projects, and to add the lgpl header when a new file is added to the the 'ee' projects.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)