You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marius Grama (JIRA)" <ji...@codehaus.org> on 2008/10/29 07:54:51 UTC
[jira] Created: (MECLIPSE-498) eclipse:eclipse generates inaccurate
.project file for ejb-client dependency
eclipse:eclipse generates inaccurate .project file for ejb-client dependency
----------------------------------------------------------------------------
Key: MECLIPSE-498
URL: http://jira.codehaus.org/browse/MECLIPSE-498
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Reporter: Marius Grama
I have a pom.xml in which i specify among the dependencies and ejb library and its ejb-client generated library dependencies :
.....
<dependency>
<groupId>myproject</groupId>
<artifactId>my-artifact-ejb</artifactId>
<version>0.0.1-SNAPSHOT</version>
<type>ejb-client</type>
</dependency>
<dependency>
<groupId>myproject</groupId>
<artifactId>my-artifact-ejb</artifactId>
<version>0.0.1-SNAPSHOT</version>
<type>ejb</type>
</dependency>
.....
When I run maven having this program arguments :
-e clean eclipse:clean eclipse:eclipse package install -Dmaven.test.skip=true -Declipse.useProjectReferences=false -Declipse.useProjectReferences=false
everything runs smoothly and I have all the libraries added in the classpath.
When I drop
-Declipse.useProjectReferences=false
program argument my .project generated file looks a bit like this :
<projectDescription>
<name>uniqa-testservice-service-testserviceimpl-iiop-client</name>
<comment>uniqa-testservice-service-testserviceimpl-iiop-client</comment>
<projects>
<project>xxx</project>
<project>my-artifact-ejb</project>
<project>my-artifact-ejb</project>
<project>yyyy</project>
</projects>
........
</projectDescription>
and in the .classpath file :
....
<classpathentry kind="src" path="/my-artifact-ejb"/>
<classpathentry kind="src" path="/my-artifact-ejb"/>
.....
my-artifact-ejb is a project which exists in the same workspace as my project.
I am rather new to Maven, but it seems to me that this is a bug for eclipse:eclipse. Please correct me if I am wrong.
--
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
[jira] Updated: (MECLIPSE-498) eclipse:eclipse generates inaccurate
.project file for ejb-client dependency
Posted by "Marius Grama (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marius Grama updated MECLIPSE-498:
----------------------------------
Attachment: EclipsePlugin.patch
This is a patch which corrects this bug.
Basically in EclipsePlugin.isAravailableAsAWorkspaceProject(Artifact) method needs to be added an extra test among with groupId, artifactId and version tests, where it should be verified if the workspace artifact's type is the same as the passed artifact's type.
> eclipse:eclipse generates inaccurate .project file for ejb-client dependency
> ----------------------------------------------------------------------------
>
> Key: MECLIPSE-498
> URL: http://jira.codehaus.org/browse/MECLIPSE-498
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Reporter: Marius Grama
> Attachments: EclipsePlugin.patch
>
>
> I have a pom.xml in which i specify among the dependencies and ejb library and its ejb-client generated library dependencies :
> .....
> <dependency>
> <groupId>myproject</groupId>
> <artifactId>my-artifact-ejb</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <type>ejb-client</type>
> </dependency>
> <dependency>
> <groupId>myproject</groupId>
> <artifactId>my-artifact-ejb</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <type>ejb</type>
> </dependency>
> .....
> When I run maven having this program arguments :
> -e clean eclipse:clean eclipse:eclipse package install -Dmaven.test.skip=true -Declipse.useProjectReferences=false -Declipse.useProjectReferences=false
> everything runs smoothly and I have all the libraries added in the classpath.
> When I drop
> -Declipse.useProjectReferences=false
> program argument my .project generated file looks a bit like this :
> <projectDescription>
> <name>uniqa-testservice-service-testserviceimpl-iiop-client</name>
> <comment>uniqa-testservice-service-testserviceimpl-iiop-client</comment>
> <projects>
> <project>xxx</project>
> <project>my-artifact-ejb</project>
> <project>my-artifact-ejb</project>
> <project>yyyy</project>
> </projects>
> ........
> </projectDescription>
> and in the .classpath file :
> ....
> <classpathentry kind="src" path="/my-artifact-ejb"/>
> <classpathentry kind="src" path="/my-artifact-ejb"/>
> .....
> my-artifact-ejb is a project which exists in the same workspace as my project.
> I am rather new to Maven, but it seems to me that this is a bug for eclipse:eclipse. Please correct me if I am wrong.
--
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