[
https://issues.apache.org/jira/browse/CXF-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801999#action_12801999
]
Gary Gregory edited comment on CXF-2595 at 1/19/10 12:29 AM:
-------------------------------------------------------------
Almost; the issue is that the version is TOO specific, for example:
cxf-api-2.2.6-SNAPSHOT
"-2.2.6-SNAPSHOT" is appended to all project names, which becomes invalid as
soon as 2.2.6 comes out and the "2.2.x" branch is working on 2.2.7.
It would be better with "cxf-api-2.2.x-SNAPSHOT" or "cxf-api-2.2-SNAPSHOT"
I can see that the pom.xml contains:
<version>2.2.6-SNAPSHOT</version>
So, after reading the Maven docs
(http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html), I
found the solution:
{quote}
mvn -Psetup.eclipse -Declipse.projectNameTemplate=[artifactId]-2.2.x
{quote}
was (Author: ggreg...@seagullsw.com):
Almost; the issue is that the version is TOO specific, for example:
cxf-api-2.2.6-SNAPSHOT
"-2.2.6-SNAPSHOT" is appended to all project names, which becomes invalid as
soon as 2.2.6 comes out and the "2.2.x" branch is working on 2.2.7.
It would be better with "cxf-api-2.2.x-SNAPSHOT" or "cxf-api-2.2-SNAPSHOT"
I can see that the pom.xml contains:
<version>2.2.6-SNAPSHOT</version>
So perhaps inventing something like this would be better:
-Declipse.postfixProjectName=2.2.x
> Facilitate multi-branch development in Eclipse
> ----------------------------------------------
>
> Key: CXF-2595
> URL: https://issues.apache.org/jira/browse/CXF-2595
> Project: CXF
> Issue Type: Improvement
> Reporter: Gary Gregory
>
> It looks like CXF uses the Maven POM project/artifactId to name Eclipse
> projects when the CXF maven tool is used:
> bq. mvn -Psetup.eclipse
> This is great until you want to use the same Eclipse workspace to work on
> multiple branches.
> For example, I want to be able to compare debug runs in CXF 2.2.x and 2.3.x.
> Switching workspaces is a pain and does not allow having two debug sessions
> running at the same time.
> What about having the CXF {{setup.eclipse}} tool generate the Eclipse project
> name to include the branch name?
> For example, instead of {{cxf-api}}, use {{cxf-api-2.2.x}}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
