cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CXF-2595) Facilitate multi-branch development in Eclipse
Date Wed, 13 Jan 2010 22:35:54 GMT

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

Daniel Kulp commented on CXF-2595:
----------------------------------


With eclipse.addVersionToProjectName, can this issue be marked resolved?


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


Mime
View raw message