[ http://jira.codehaus.org/browse/MECLIPSE-120?page=all ]
Joerg Schaible reopened MECLIPSE-120:
-------------------------------------
"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."
Gosh, this happens anyway. When I create eclipse projects for all our ~100
modules at once, a lot of them cannot even compile although a build from
command line runs fine for the same multi-module level. The only possibility to
"fix" those projects is to create in those POMs a dependencyManagement section,
add the correct (transitive) dependency there (without adding it to the
dependency section).
Additionally I did not say, that this is the default, but an option. If it is
selected the developer knows, what he does. We were now bitten more than once
at *release* time, when the build of an artifact was broken by an updated
transitive dependency.
"You should just update the dependencies to the working copy versions if you
want to refactor stuff."
With such a lot of artifacts you sometimes have no idea, which artifacts might
be affected by a change. And it kills one of Eclipse best features.
"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."
Now, the current mode gives an unrealistic idea about the consistency of the
code. If all projects are linked, the developer knows after a refactoring,
which artifacts have been hit and can adjust the necessary POMs.
Note, we're not developing Maven, but enterprise apps. Maven and its plugins
are a "standalone" apps with isolated classloaders. With a lot of EJBs in an
EAR you have to synchronize versions in the end, since the EAR plugin will
collect from every dependency exactly one version and does not care if
different EJBs refer the same artifact in different versions in their
manifests.
> 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: 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
