Issue Details (XML | Word | Printable)

Key: MECLIPSE-3
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: fabrizio giustina
Reporter: Barry Kaplan
Votes: 3
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Maven 2.x Eclipse Plugin

Generation of eclipse projects requires that reactor projects have installed jars

Created: 18/Nov/05 11:33 AM   Updated: 02/Apr/06 01:17 AM
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.2

Time Tracking:
Not Specified


 Description  « Hide
Most reactor actions work without requiring projects in the hierachy to have installed jars. eg, You can compile and test the hierarchy using only the project target directories. However, when generating eclipse projects, the plugin will fail if a dependent project in the hierarchy does not have its jar installed. (Note, that if the jar /is/ installed, a direct project reference /will/ be defined in the .classpath – ie, the project installed jar is never actually used.)

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Olivier Lamy added a comment - 09/Feb/06 05:26 AM
The title should be :
eclipse:eclipse requires target/classes directories present for project references.
see relative http://jira.codehaus.org/browse/MECLIPSE-67.
Olivier

Olivier Lamy added a comment - 09/Feb/06 05:36 AM
workaround :
mvn -Dmaven.test.skip=true clean compile eclipse:clean eclipse:eclipse

Olivier Lamy added a comment - 22/Feb/06 06:57 AM
I have a probably related trouble.
My root pom contains modules :
  • accommons-tools (version 2.4-SNAPSHOT)
  • accommons-prefs (version 1.6-SNAPSHOT)
  • accommons-cache (version 2.5-SNAPSHOT)
  • split-tars (1.6-SNAPSHOT)

accommons-cache depends on : accommons-tools-2.3 and accommons-prefs-1.5
split-tars depends on accommons-tools-2.3, accommons-prefs-1.5 and accommons-cache-2.5-SNAPSHOT
In the root folder, I run : mvn compile eclipse:clean eclipse:eclipse
In accommons-cache, my .classpath contains :
<classpathentry kind="var" path="M2_REPO/C:/projets/accommons-libs/accommons-prefs/target/classes"/>
<classpathentry kind="var" path="M2_REPO/C:/projets/accommons-libs/accommons-tools/target/classes"/>

In split-tars folder, my .classpath contains :
<classpathentry kind="var" path="M2_REPO/C:/projets/accommons-libs/accommons-prefs/target/classes"/>
<classpathentry kind="var" path="M2_REPO/C:/projets/accommons-libs/accommons-tools/target/classes"/>

and a good :
<classpathentry kind="src" path="/accommons-cache"/>

I don't know if it's relative to this issue
Olivier


fabrizio giustina added a comment - 02/Apr/06 01:17 AM
fix in svn for 2.2.
The plugin now does a manual artifact resolution and doesn't require reactor projects to be installed anymore.

A snapshot with this change can be found at:
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-eclipse-plugin/2.2-SNAPSHOT/maven-eclipse-plugin-2.2-20060402.070500-1.jar