maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Max Bowsher (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-120) Force inter-project dependencies
Date Fri, 01 Feb 2008 12:23:58 GMT

    [ http://jira.codehaus.org/browse/MECLIPSE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122014
] 

Max Bowsher commented on MECLIPSE-120:
--------------------------------------

I'm not sure that MECLIPSE-344 really addresses this use-case - if I'm reading it right, the
MECLIPSE-344 changes allow connecting project dependencies to projects already in the workspace.

This use-case, though, is about constructing set of project files that refer to each other
as dependencies, before they are imported into the workspace.

IIUC, the MECLIPSE-344 feature would allow this to be approximated by (1) doing normal eclipse:eclipse
(2) importing the projects (3) redoing eclipse:eclipse in MECLIPSE-344 mode. A bit inelegant.
Also, ideally it should be possible to use this feature without having to specify the path
to your eclipse workspace on the command line.

Therefore I think it is inaccurate to resolve this issue as a duplicate of MECLIPSE-344 -
it's just loosely related. I think there is value in implementing this feature as described
above alongside the MECLIPSE-344 feature.

> Force inter-project dependencies
> --------------------------------
>
>                 Key: MECLIPSE-120
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-120
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Multi-projects
>    Affects Versions: 2.2
>            Reporter: Joerg Schaible
>            Assignee: Arnaud Heritier
>             Fix For: 2.5
>
>
> In a multi-module setup, the dependencies between the projects are only created, if the
project's version match the one of the referenced artfiact. After a release this is normally
no longer the case if you have modules with independent release cycles. Therefore it would
be good, if the plugin could be forced with an option (e.g. -forceSnapshot) to use a dependency
to a module's project with a snapshot version instead of a dependency to the released artifact
in the local repository. The plugin detects this situation already, but logs just a warning.
Without this feature, refactorings are getting really tedious.

-- 
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

        

Mime
View raw message