[ 
https://issues.apache.org/jira/browse/CXF-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797832#action_12797832
 ] 

Gary Gregory commented on CXF-2595:
-----------------------------------

I did not know about {{eclipse.addVersionToProjectName}}, thank you for the tip.

I do not think I want the trunk projects to carry a version number though. I do 
like having it all versions in one workspace to able to easily compare and port 
code around. I am thinking about a set up like this:
- I'll close all CXF 2.2.x projects in Eclipse.
- Run {{mvn -Psetup.eclipse -Declipse.addVersionToProjectName=true}} for 
branches I want (just 2.2.x really), my first run was just {{mvn 
-Psetup.eclipse}}
- Import all 2.2.x branch projects which will have the version numbers.
- Run {{mvn -Psetup.eclipse}} for trunk.
- Import all 2.3.x trunk projects which will not have the version numbers.

Presumably when 2.3.x is released, it will be branched and I can get the 2.3.x 
branch and run {{mvn -Psetup.eclipse -Declipse.addVersionToProjectName=true}} 
and keep trunk as is.

> 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.

Reply via email to