maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <>
Subject [jira] Closed: (MECLIPSE-120) Force inter-project dependencies
Date Sat, 07 Oct 2006 01:08:27 GMT
     [ ]

Kenney Westerhof closed MECLIPSE-120.

    Resolution: Won't Fix

Sorry but we can't do this. This would present the user with a different set of dependency
relations in eclipse
than is really defined. You should just update the dependencies to the working copy versions
if you want to refactor stuff.

It would work in eclipse, but when you run a build with maven, it would fail. This gives developers
an unrealistic
idea about the consistency of their code.

> Force inter-project dependencies
> --------------------------------
>                 Key: MECLIPSE-120
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: multiproject
>    Affects Versions: 2.2
>            Reporter: Joerg Schaible
> 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:
For more information on JIRA, see:


View raw message