[
http://jira.codehaus.org/browse/MECLIPSE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180781#action_180781
]
Christophe Hamerling commented on MECLIPSE-578:
-----------------------------------------------
In fact we should be able to access to all the POM attributes so that we can
define the template like we want.
Tags, trunk or branches is a good starting point
> Create a new variable to hold branch name of the project scm
> ------------------------------------------------------------
>
> Key: MECLIPSE-578
> URL: http://jira.codehaus.org/browse/MECLIPSE-578
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : .project
> Affects Versions: 2.7
> Reporter: Christophe DENEUX
>
> The configuration parameter 'projectNameTemplate' is able to use the
> following strings to define the project name pattern: groupId, artifactId,
> version. When using a pattern ad '[artifactId]-[version]', it is needed to
> re-generate Eclipse files when changing the version. To avoide this
> re-generation, I think a new variable [branch] holding the SCM branch name or
> "trunk" should be added.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
