You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Barry Kaplan (JIRA)" <ji...@codehaus.org> on 2005/11/18 18:36:06 UTC
[jira] Created: (MNG-1623) Generation of eclipse projects requires that reactor projects have installed jars
Generation of eclipse projects requires that reactor projects have installed jars
---------------------------------------------------------------------------------
Key: MNG-1623
URL: http://jira.codehaus.org/browse/MNG-1623
Project: Maven 2
Type: Bug
Components: maven-eclipse-plugin
Versions: 2.0
Reporter: Barry Kaplan
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.)
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MECLIPSE-3) Generation of eclipse projects
requires that reactor projects have installed jars
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-3?page=all ]
fabrizio giustina updated MECLIPSE-3:
-------------------------------------
Version: 2.0
> Generation of eclipse projects requires that reactor projects have installed jars
> ---------------------------------------------------------------------------------
>
> Key: MECLIPSE-3
> URL: http://jira.codehaus.org/browse/MECLIPSE-3
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Barry Kaplan
>
>
> 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.)
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-3) Generation of eclipse projects
requires that reactor projects have installed jars
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-3?page=comments#action_59217 ]
Olivier Lamy commented on MECLIPSE-3:
-------------------------------------
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
> Generation of eclipse projects requires that reactor projects have installed jars
> ---------------------------------------------------------------------------------
>
> Key: MECLIPSE-3
> URL: http://jira.codehaus.org/browse/MECLIPSE-3
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Barry Kaplan
>
>
> 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.)
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-3) Generation of eclipse projects
requires that reactor projects have installed jars
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-3?page=comments#action_58230 ]
Olivier Lamy commented on MECLIPSE-3:
-------------------------------------
The title should be :
eclipse:eclipse requires target/classes directories present for project references.
see relative http://jira.codehaus.org/browse/MECLIPSE-67.
Olivier
> Generation of eclipse projects requires that reactor projects have installed jars
> ---------------------------------------------------------------------------------
>
> Key: MECLIPSE-3
> URL: http://jira.codehaus.org/browse/MECLIPSE-3
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Barry Kaplan
>
>
> 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.)
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MECLIPSE-3) Generation of eclipse projects
requires that reactor projects have installed jars
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-3?page=comments#action_58232 ]
Olivier Lamy commented on MECLIPSE-3:
-------------------------------------
workaround :
mvn -Dmaven.test.skip=true clean compile eclipse:clean eclipse:eclipse
> Generation of eclipse projects requires that reactor projects have installed jars
> ---------------------------------------------------------------------------------
>
> Key: MECLIPSE-3
> URL: http://jira.codehaus.org/browse/MECLIPSE-3
> Project: Maven 2.x Eclipse Plugin
> Type: Bug
> Versions: 2.0
> Reporter: Barry Kaplan
>
>
> 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.)
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org