You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jean-Pierre Froud (JIRA)" <ji...@codehaus.org> on 2012/06/22 10:01:22 UTC
[jira] (MECLIPSE-726) Limit project references to modules only
Jean-Pierre Froud created MECLIPSE-726:
------------------------------------------
Summary: Limit project references to modules only
Key: MECLIPSE-726
URL: https://jira.codehaus.org/browse/MECLIPSE-726
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: Core : Dependencies resolution and build path (.classpath), Core : Multi-projects
Affects Versions: 2.8
Environment: Win. XP sp3
Reporter: Jean-Pierre Froud
Attachments: ScreenShot278.jpg
In my workspace, I have a multi-module project A with A1, A2 modules.
I also have another multi-module project B with B1, B2 modules.
A1 has a dependency on B1 and I'm using 'useProjectReferences' (true) and A2 depends on A1.
!ScreenShot278.jpg!
When I'm doing "mvn eclipse:eclipse" on A, the result I want:
A2 references workspace project A1
A1 uses repository artifact B1 (not the workspace project)
Is there a way to limit 'useProjectReferences' only to modules? Or listing the projects to reference?
The reason I want that is because I had weird behaviour on versions:
A1 depends on C version 2.0
B1 depends on C version 1.5
and the version of C taken during runtime of A1 is the one from B1 (1.5) instead of 2.0 version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-726) Limit project references to modules only
Posted by "Jean-Pierre Froud (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MECLIPSE-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301888#comment-301888 ]
Jean-Pierre Froud commented on MECLIPSE-726:
--------------------------------------------
I found a way to do this:
{code:xml}
<useProjectReferences>true</useProjectReferences>
<workspace>..</workspace>
{code}
This seems to be working fine.
But I'm still not getting the purpose of {{limitProjectReferencesToWorkspace}}
If I do this:
{code:xml}
<useProjectReferences>true</useProjectReferences>
<workspace>..</workspace>
<limitProjectReferencesToWorkspace>true</limitProjectReferencesToWorkspace>
{code}
There's no project references, all dependencies come from the repo.
> Limit project references to modules only
> ----------------------------------------
>
> Key: MECLIPSE-726
> URL: https://jira.codehaus.org/browse/MECLIPSE-726
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: Core : Dependencies resolution and build path (.classpath), Core : Multi-projects
> Affects Versions: 2.8
> Environment: Win. XP sp3
> Reporter: Jean-Pierre Froud
> Attachments: ScreenShot278.jpg
>
>
> In my workspace, I have a multi-module project A with A1, A2 modules.
> I also have another multi-module project B with B1, B2 modules.
> A1 has a dependency on B1 and I'm using 'useProjectReferences' (true) and A2 depends on A1.
> !ScreenShot278.jpg!
> When I'm doing "mvn eclipse:eclipse" on A, the result I want:
> A2 references workspace project A1
> A1 uses repository artifact B1 (not the workspace project)
> Is there a way to limit 'useProjectReferences' only to modules? Or listing the projects to reference?
> The reason I want that is because I had weird behaviour on versions:
> A1 depends on C version 2.0
> B1 depends on C version 1.5
> and the version of C taken during runtime of A1 is the one from B1 (1.5) instead of 2.0 version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira