[
https://issues.apache.org/jira/browse/ISIS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13569788#comment-13569788
]
Dan Haywood commented on ISIS-227:
----------------------------------
On 3 February 2013 10:38, Minto van der Sluis <[email protected]> wrote (on the dev
mailing list):
Hi Dan,
Can you explain why ISIS-227 was needed? I understand what it does, but
not why it was needed.
~~~~
Dan's reply:
It's a fix for the way that I work, and perhaps others do too.
I usually work in Eclipse and rely on m2e to configure the classpaths of the
projects, but Eclipse's incremental compiler doing the actual compilation.
However, every now and then I like to go over to the cmd line and do a build
from there; Eclipse doesn't distinguish between the regular classpath
(src/main/java) and the test classpath (src/test/java) and so a
misconfiguration in a pom.xml may build in Eclipse but not in Maven.
Anyway... by default both Maven and m2e configure the target directory as the
destination for class files. Doing a build from the cmd line confuses Eclipse,
requiring (for me at least) a refresh all projects followed by a clean followed
by a build all.
With ISIS-227, Eclipse compiles into target-ide whereas Maven compiles into
target. Thus the two build environments don't confuse each other.
> Separate out Eclipse (m2e) target classes from Maven cli,so co-exist better.
> ----------------------------------------------------------------------------
>
> Key: ISIS-227
> URL: https://issues.apache.org/jira/browse/ISIS-227
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-1.0.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Use the m2e.version property to activate a profile such that Eclipse/M2E
> builds into "target-ide/..." while the Maven command line continues to build
> into the regular "target/..."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
