[
https://issues.apache.org/jira/browse/CXF-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797738#action_12797738
]
Daniel Kulp commented on CXF-2595:
----------------------------------
I personally prefer NOT having the versions there as I have separate workspaces
for the various branches I need.
Question: could you use the eclipse.addVersionToProjectName flag to the
eclipse plugin?
You should be able to do:
mvn -Psetup.eclipse -Declipse.addVersionToProjectName=true
You could also add something to your .m2/settings.xml like:
{code:xml}
<activeProfiles>
<activeProfile>extra</activeProfile>
</activeProfiles>
<profiles>
<profile>
<id>extra</id>
<properties>
<eclipse.workspace>/home/dkulp/working/workspace</eclipse.workspace>
<downloadSources>true</downloadSources>
<eclipse.workspace.dir>/home/dkulp/working/workspace</eclipse.workspace.dir>
<eclipse.addVersionToProjectName>true</eclipse.addVersionToProjectName>
</properties>
</profile>
</profiles>
{code}
to make it always do that.
> 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.
