[
https://issues.apache.org/jira/browse/CXF-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556566#action_12556566
]
Daniel Kulp commented on CXF-1357:
----------------------------------
I'd be opposed to making that the default for a variety of reasons:
1) No other maven based project would work that way. One of the nice things
about maven is it's relative consistency.
2) To me, that would suck. I LIKE the fact that they share the classes
directory. I can develop/build in eclipse, then run "mvn test" on the command
line and maven doesn't waste time compiling anything.
Usually, you don't have to have eclipse do a full clean. Usually, you can
just hit F5 (refresh) on the affected projects which is less time.
> Setting CXF eclipse output directory to be eclipse-classes instead of target
> ----------------------------------------------------------------------------
>
> Key: CXF-1357
> URL: https://issues.apache.org/jira/browse/CXF-1357
> Project: CXF
> Issue Type: Improvement
> Components: Build system
> Reporter: willem Jiang
> Assignee: willem Jiang
> Fix For: 2.0.4, 2.1
>
>
> It is painful when you run mvn clean install in the trunk, If eclipse already
> starts and caches the target directory classes.
> Since mvn will delete the classes in the target directory, and eclipse will
> lost the reference of these classes.
> If you want to eclipse work again, you have to clean the project and let
> eclipse automatic build the project again, but this is a time consuming work.
> I suggest to set the mvn eclipse plugin's configuration output directory to
> be eclipse-classes not the default target directory , so eclipse output
> directory and mvn output directory will not share the same directory.
> So this issue will be solved.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
