[
http://jira.codehaus.org/browse/MECLIPSE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrie Treloar closed MECLIPSE-338.
-----------------------------------
Resolution: Won't Fix
This is not a bug, your files are just misconfigured.
See
http://maven.apache.org/plugins/maven-eclipse-plugin/examples/prevent-module-references.html
You need to change your configuration in Master/pom.xml to:
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<useProjectReferences>false</useProjectReferences>
</configuration>
</plugin>
{code}
And then when you run {code}mvn eclipse:eclipse{code} the .classpath files
will be how you want them to (this is the output I have):
{code:xml}
<classpath>
<classpathentry kind="src" path="src/main/java"/>
<classpathentry kind="output" path="target/classes"/>
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
<classpathentry kind="var" path="M2_REPO/x/y/z/Base/0.1/Base-0.1.jar"/>
<classpathentry kind="var" path="M2_REPO/junit/junit/4.4/junit-4.4.jar"/>
</classpath>
{code}
> eclipse:eclipse behaves differently in multiproject setting vs. iterating
> single projects (when explicitly avoiding inter-project dependencies)
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-338
> URL: http://jira.codehaus.org/browse/MECLIPSE-338
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: multiproject
> Affects Versions: 2.4
> Environment: Win XP Professional, Java 1.5_09, maven 2.0.6
> Reporter: Andreas Zielke
> Priority: Minor
> Attachments: mvnexample.zip
>
>
> I have a flat multiproject setting and would like to avoid project
> dependencies, to be closer to the production setting. (The motivation may be
> arguable, but anyway.) So I configured
> {{
> <eclipse.useProjectReferences>false</eclipse.useProjectReferences>
> }}
> in the master project pom.
> When I call mvn eclipse:eclipse in the "child" projects, no inter-project
> dependencies are generated - this is behaviour I'd expected.
> When I call mvn eclipse:eclipse in the "master" project, the eclipse files
> are generated, but interproject dependencies are inserted instead of jar
> dependencies.
> I've created an minimal example to reproduce this behaviour. The archive
> contains three projects:
> Master - the pom only project, driving the other two.
> Base - the first child project with no project dependencies. (Could be common
> server/client-side code.)
> Server_Base - the second child project with a dependency to Base.
> After extracting the archive you can reproduce the error by doing the
> following:
> 1) Try running mvn eclipse:eclipse in Master,
> 2) backup the eclipse files in Server_Base
> 3) run mvn eclipse:clean eclipse:eclipse in Server_Base.
> 4) Compare the new eclipse project files with the previous ones.
--
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
