You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vlad Skarzhevskyy (JIRA)" <ji...@codehaus.org> on 2007/02/14 05:12:21 UTC
[jira] Created: (MECLIPSE-229) multiproject with classifier
dependency on another module
multiproject with classifier dependency on another module
---------------------------------------------------------
Key: MECLIPSE-229
URL: http://jira.codehaus.org/browse/MECLIPSE-229
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: multiproject
Affects Versions: 2.3, 2.2
Environment: windows, java5, multiproject
Reporter: Vlad Skarzhevskyy
I have module "microemu-injected" with artifact <classifier>inject</classifier>
<dependency>
<groupId>org.microemu</groupId>
<artifactId>microemu-injected</artifactId>
<version>${version}</version>
<classifier>inject</classifier>
</dependency>
When I generate eclipse project I got dependency on complete project not just to its artifact.
<classpathentry kind="src" path="/microemu-injected"/>
When generating project for each module separately
<classpathentry kind="var" path="M2_REPO/org/microemu/microemu-injected/2.0.1-SNAPSHOT/microemu-injected-2.0.1-SNAPSHOT-inject.jar"/>
And this is what I need.
But I have other project dependancy so I can't use useProjectReferences:false
Project https://microemulator.svn.sourceforge.net/svnroot/microemulator/trunk/microemulator
Is it posible to add filter to configuration of maven-eclipse-plugin
to trigger different behaviour for this situation.
like this:
<dependencySets>
<dependencySet>
<useProjectReferences>false</useProjectReferences>
<includes>
<include>microemu-injected</include>
</includes>
</dependencySet>
</dependencySets>
or
Simple :
<useProjectReferencesWithclassifier>false<useProjectReferencesWithclassifier>
--
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] Commented: (MECLIPSE-229) multiproject with classifier
dependency on another module
Posted by "Vincenzo Vitale (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196390#action_196390 ]
Vincenzo Vitale commented on MECLIPSE-229:
------------------------------------------
Any update on this?
I have exactly the same problem using the GWT eclipse plugin with two different project both with GWT code. To have the plugin working fine I had to add:
<dependency>
<groupId>com.tomtom.web</groupId>
<artifactId>common</artifactId>
<version>${version}</version>
</dependency>
<dependency>
<groupId>com.tomtom.web</groupId>
<artifactId>common</artifactId>
<version>${version}</version>
<classifier>sources</classifier>
<scope>compile</scope>
</dependency>
in the upper project but in this way a only project dependency will be added in ecllipse and I do need this only for the first dep and a normal jar dep for the second dep (related to the source code).
Thanks,
V.
> multiproject with classifier dependency on another module
> ---------------------------------------------------------
>
> Key: MECLIPSE-229
> URL: http://jira.codehaus.org/browse/MECLIPSE-229
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Multi-projects
> Affects Versions: 2.2, 2.3
> Environment: windows, java5, multiproject
> Reporter: Vlad Skarzhevskyy
> Attachments: noProjectReferences.patch
>
>
> I have module "microemu-injected" with artifact <classifier>inject</classifier>
> <dependency>
> <groupId>org.microemu</groupId>
> <artifactId>microemu-injected</artifactId>
> <version>${version}</version>
> <classifier>inject</classifier>
> </dependency>
> When I generate eclipse project I got dependency on complete project not just to its artifact.
> <classpathentry kind="src" path="/microemu-injected"/>
> When generating project for each module separately
> <classpathentry kind="var" path="M2_REPO/org/microemu/microemu-injected/2.0.1-SNAPSHOT/microemu-injected-2.0.1-SNAPSHOT-inject.jar"/>
> And this is what I need.
> But I have other project dependancy so I can't use useProjectReferences:false
> Project https://microemulator.svn.sourceforge.net/svnroot/microemulator/trunk/microemulator
> Is it posible to add filter to configuration of maven-eclipse-plugin
> to trigger different behaviour for this situation.
> like this:
> <dependencySets>
> <dependencySet>
> <useProjectReferences>false</useProjectReferences>
> <includes>
> <include>microemu-injected</include>
> </includes>
> </dependencySet>
> </dependencySets>
> or
> Simple :
> <useProjectReferencesWithclassifier>false<useProjectReferencesWithclassifier>
>
--
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-229) multiproject with classifier
dependency on another module
Posted by "Vlad Skarzhevskyy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vlad Skarzhevskyy updated MECLIPSE-229:
---------------------------------------
Attachment: noProjectReferences.patch
suggested solution for problem
<noProjectReferences>
<noProjectReference>special-module1<noProjectReference>
<noProjectReference>special-module2<noProjectReference>
<noProjectReferences>
patch made on trunk from February 13 SVN revision 494359
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin
> multiproject with classifier dependency on another module
> ---------------------------------------------------------
>
> Key: MECLIPSE-229
> URL: http://jira.codehaus.org/browse/MECLIPSE-229
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: multiproject
> Affects Versions: 2.2, 2.3
> Environment: windows, java5, multiproject
> Reporter: Vlad Skarzhevskyy
> Attachments: noProjectReferences.patch
>
>
> I have module "microemu-injected" with artifact <classifier>inject</classifier>
> <dependency>
> <groupId>org.microemu</groupId>
> <artifactId>microemu-injected</artifactId>
> <version>${version}</version>
> <classifier>inject</classifier>
> </dependency>
> When I generate eclipse project I got dependency on complete project not just to its artifact.
> <classpathentry kind="src" path="/microemu-injected"/>
> When generating project for each module separately
> <classpathentry kind="var" path="M2_REPO/org/microemu/microemu-injected/2.0.1-SNAPSHOT/microemu-injected-2.0.1-SNAPSHOT-inject.jar"/>
> And this is what I need.
> But I have other project dependancy so I can't use useProjectReferences:false
> Project https://microemulator.svn.sourceforge.net/svnroot/microemulator/trunk/microemulator
> Is it posible to add filter to configuration of maven-eclipse-plugin
> to trigger different behaviour for this situation.
> like this:
> <dependencySets>
> <dependencySet>
> <useProjectReferences>false</useProjectReferences>
> <includes>
> <include>microemu-injected</include>
> </includes>
> </dependencySet>
> </dependencySets>
> or
> Simple :
> <useProjectReferencesWithclassifier>false<useProjectReferencesWithclassifier>
>
--
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