maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Tsang (JIRA)" <>
Subject [jira] Commented: (MNGECLIPSE-75) Update source folders action should set default output folder
Date Thu, 09 Mar 2006 06:54:23 GMT
    [ ] 

Ray Tsang commented on MNGECLIPSE-75:

Eugene,  I see the problem.  I just made a patch that adds the "Share output folder" option,
as well as a default output folder if it's not shared.

I also noticed the output folder for resources were set to themselves for a reason, I've also
restored that behavior when output folders are not shared.

> Update source folders action should set default output folder
> -------------------------------------------------------------
>          Key: MNGECLIPSE-75
>          URL:
>      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,, 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
> 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:
For more information on JIRA, see:

View raw message