Hi Dan, Thanks for you explanation.
Hmm, I also prefer to use the command-line. So I guess it should also improve my merged CLI - IDE experience. Regards, Minto Op 3-2-2013 15:51, Dan Haywood schreef: > 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. > > I've copied-n-pasted the above as a comment onto the ticket. > > Dan > > On 3 February 2013 10:38, Minto van der Sluis <mi...@xup.nl> wrote: > >> Hi Dan, >> >> Can you explain why ISIS-227 was needed? I understand what it does, but >> not why it was needed. >> >> Regards, >> >> Minto >> >> -- >> ir. ing. Minto van der Sluis >> Software innovator / renovator >> Xup BV >> >> Mobiel: +31 (0) 626 014541 >> >> -- ir. ing. Minto van der Sluis Software innovator / renovator Xup BV Mobiel: +31 (0) 626 014541
