[ http://jira.codehaus.org/browse/MNGECLIPSE-75?page=comments#action_58850 ]
Jimisola Laursen commented on MNGECLIPSE-75: -------------------------------------------- Eugene, * In respone to your first 2nd last comment: The first test project was not mine - it was Jochen's. Two different persons, but with similar problems. I know that I don't need to run mvn from (shell) console for get source folders in Eclipse. The reason that I did is that I wanted to attach you its output in order for you to see that it works outside of Eclipse. The problem still exists as far as I am concerned. That is, even if I generate the sources from outside (with mvn) they are not pickup by Eclipse when I use "Update Sources". src/test/java/ValidateXmlBeansProblemTest.java: "TestDocument cannot be resolved to a Type" the problem is not only that generation as you mention in the last comment, but the fact that the plugin does not seem to make Eclipse aware of the generated source code * In respone to your last comment: I am _very_ new to Maven and even if I am aware of the different goals and their order I don't follow you on how I should verify it by trying to use the xmlbeans goal. How do I do this? I'll file a bug, but I would like to know how to verify as well. Plugin does not execute generate-test-sources and generate-test-resources-goals"? Last, I am usually very concerned about names but "process" or "generate" does not matter as long as it works :) (who is "we" btw?) > 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 > Priority: Blocker > 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]
