[
http://jira.codehaus.org/browse/MECLIPSE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86128
]
Daniel Brolund commented on MECLIPSE-134:
-
Oops, didn't re-read the post after having changed some paths. The first
[
http://jira.codehaus.org/browse/MECLIPSE-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86127
]
Daniel Brolund commented on MECLIPSE-134:
-
A workaround could look like this:
Set the property myTarget to the empt
[ http://jira.codehaus.org/browse/MECLIPSE-134?page=comments#action_84475 ]
Aaron Digulla commented on MECLIPSE-134:
> you can already use the "outputDir" parameter
I tried that and it didn't work. Can you please post an example?
Also, i
[ http://jira.codehaus.org/browse/MECLIPSE-134?page=comments#action_81487 ]
Aaron Digulla commented on MECLIPSE-134:
It's not just mvn clean which can irritate Eclipse. mvn cobertura recompiles
the sources with instrumentation which can c
[ http://jira.codehaus.org/browse/MECLIPSE-134?page=comments#action_74240 ]
Richard Home commented on MECLIPSE-134:
---
... but then the outputDir option fixes this, so it is not a bug.
> target/classes not acceptable for eclipse
> ---
[ http://jira.codehaus.org/browse/MECLIPSE-134?page=comments#action_74233 ]
Richard Home commented on MECLIPSE-134:
---
I don't think this is a "minor" problem. Although you can manually set up a
separate bin directory for Eclipse, it rather d
[ http://jira.codehaus.org/browse/MECLIPSE-134?page=comments#action_72058 ]
Andrea Aime commented on MECLIPSE-134:
--
I totally agree on this one.
There is another way to break things: enable workspace automated refresh, then
do a "mvn clean
