[
http://jira.codehaus.org/browse/MECLIPSE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122345
]
Arnaud Heritier commented on MECLIPSE-120:
------------------------------------------
Do we reopen the issue ?
> 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
