[ http://jira.codehaus.org/browse/MNGECLIPSE-75?page=comments#action_60431 ]
Eugene Kuleshov commented on MNGECLIPSE-75: ------------------------------------------- Ray, there is an issue with doing things this way. The trouble is that Eclipse before 3.2M5 very much don't like if somebody else is messing up with its classes. For example, if you run Maven build and then will try to refresh Eclipse files there is a good chance that you'll see all kind of weird errors in Problems view and you will have to explicitly run project clean. And because of that it is better to keep classes compiled by Eclipse and by Maven separate. So, I am leaning towards single output folder like target/eclipse, which will also most likely improve performance of cleanup on full rebuild. the best approach would be to add a preference on Maven preferences panel "Share output folder", so user could choose to use shared target directory between Maven and Eclipse or not. > Update source folders action should set default output folder > ------------------------------------------------------------- > > Key: MNGECLIPSE-75 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-75 > Project: Maven 2.x Extension for Eclipse > Type: New Feature > Versions: 0.0.5 > Environment: Linux. JDK 1.5. XmlBeans 2.x. > Reporter: Jimisola Laursen > Assignee: Eugene Kuleshov > Attachments: MNGECLIPSE-75.tar.gz, mngeclipse-75-xmlbeans-testcase.zip, > set-output-folder.patch > > > I have a problem with Maven2, XmlBeans Maven Plugin and this plugin (Eclipse > Maven Plugin). However, I do believe that the problem will exist when > generating sources in other ways as well. I assume that you are familiar > with XmlBeans (if not, it's Java Binding tools that creates Java classes for > an XML Schema). > In my project I use XmlBeans when performing unit tests. Hence, the XmlBeans > Maven Plugin generates Java code under /target/test-xmlbeans-source. The > actual problem is that Eclipse needs the generated Java code otherwise it > generates errors since it can't find the classes used by the unit tests. I > want the Maven plugin to add classes of auto-generated source code to Eclipse > class paths (dependency). Is there a solution for this? > Like I hinted above this is not a XmlBeans specific problem as a project can > have other tools generating code using e.g. XSLT, AntLR etc (my project uses > XSLT as well). There are many advantages using Maven and two important ones > are with it and Eclipse: > 1) the project is built the same (i.e. using the exact same setup of > libraries, library versions etc) whether is it inside or outside Eclipse > 2) all developers have the exact same setup (same version of dependencies etc) > Are there any other known (potential) issues preventing Eclipse and Maven > from working seamlessly? > Can the Eclipses built-in compiler cause problems? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
