[ http://jira.codehaus.org/browse/MNGECLIPSE-75?page=comments#action_58865 ]
Jimisola Laursen commented on MNGECLIPSE-75: -------------------------------------------- Hmm.. I must have missed out it then (non of your last comments has any question marks btw). What question are you awaiting an answer to? Don't forget that you have two different users commenting on this issue. Are you refering two this comment: "I am not saying that it won't be fixed. But it would be nice if you can confirm that your XmlBeans stuff is getting properly into the sources once target folder is set properly." If so, then that was a comment to Jochen's attachment and his project. Hi did not use XmlBeans - that was me. If the above was your question, then here is my answer: 1. "Update Sources" did not add target/test-xmlbeans-source with default output folder (MNGECLIPSE-75-XMLBEANS) 2. "Update Sources" did not add target/test-xmlbeans-source with output folder changed to MNGECLIPSE-75-XMLBEANS/target/eclipse How is the Eclipse Maven Plugin and Eclipse suppose to co-work? I would like to see a completely transparent environment (with Maven console and Eclipse + this plugin), but is this possible with the Eclipse's internal compiler? > 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 > > > 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]
