Hi, I have the same viewpoints as the thread starter. The separate output folders was what made m2eclipse usable for me in the first place. Without separate output folders the tools keeps interfering with each other, especially when using aspectj and jaxb2 in projects. The problem I see is that classes frequently has numerous spurious error markings in eclipse, especially for generated dependencies from jaxb. To solve this I have to clean/rebuild all projects, and refresh, sometimes repeating the cycle several times. If I stop eclipse and restart, the errors reappears. A fairly frustrating way to start the day.
Still, I have used m2eclipse for long periods, but always given up en the end as this became too much of a hassle. Most of the colleagues on my team also tried m2eclipse but given up because of the above mentioned problems. The separate output folders made it functional for a long period. Now I guess I'll have to go back to q4e or eclipse:eclipse *shudder*. Couldn't the old behaviour at least be an configurable option? Regards, André Velle Eugene Kuleshov wrote: > > Benjamin Lerman wrote: >>> Yes, this is intentional. Can you explain why you want to separate >>> eclipse and maven output folders? >>> >> Well, someone (you ?) already did that for me: >> >> http://docs.codehaus.org/display/M2ECLIPSE/Separate+Eclipse+and+Maven+output+folders >> >> (cf. the end). >> >> I prefer not to have Side effect from a tool to the other. I use a lot >> of mvn clean test, or mvn clean package while working on eclipse and >> because clean will delete the target, eclipse get confused quite often. >> > Note that as of version 0.9.4, released last week, m2eclise does not > allow to specify separate output folders for Eclipse project, because it > caused way too many issues in project configuration. See more details > in this dev-list thread http://markmail.org/message/733lqtw5moa4cim4 >> Until this version, I had no problems having the 2 tools compile to 2 >> different locations, but now the launcher does not get the right class >> path. > I am not sure what "this version" is referred to. If you have issues > with launch configuration in m2eclipse 0.9.4 (though you may need to run > "update project configuration" and recreate or reset classpath in the > launch config after that), then please open a JIRA issue and provide > test project that would allow us to reproduce. See the following wiki > page for some hints. > http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues > > Thanks > > Eugene > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://www.nabble.com/Separate-build-directory-for-eclipse-and-maven-tp17750114p17770237.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
