maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-120) Force inter-project dependencies
Date Sat, 07 Oct 2006 13:48:27 GMT
    [ http://jira.codehaus.org/browse/MECLIPSE-120?page=comments#action_76908 ] 
            
Kenney Westerhof commented on MECLIPSE-120:
-------------------------------------------

Hi Joerg,

Your first problem is another issue (MECLIPSE-152), that I'd like to see solved there. Forcing
snapshot versions only fixes
that problem in certain situations. 

But you actually mean -forceProjectReference here, right?

Second issue: I see that as a good thing - you'll find out soon enough which artifacts are
affected by a change since you can't change them
because they reference jar files, not projects. 

Also, when you do a lot of refactoring etc, I get the impression you don't have multiple release
cycles, but just 1, for the entire project tree.
If that's the case, you could use a dependencyManagement section in the root pom, specifying
${version} for all modules. That way they're always
referring to reactor/workspace projects. This should fix your issue, no?

Third issue: this is fixing it afterwards, and hoping that the developer will indeed update
the poms. As I mentioned above, if you still have
jar references and not project references, you're forced to update the pom at that time, or
decide not to since it's an unwanted change.
Isn't that safer? Developers are confronted with making a good decision on what to upgrade
and what for.

What I meant with my third comment is that you see stuff working in eclipse, but it won't
compile on the commandline. That gives the developer
another responsibility - mvn install before a commit, and update the poms. It's an iterative
process and requires more time on big projects. Just
updating a pom and mvn eclipse:eclipse, then refresh in eclipse gives you much faster feedback
on wheter it still works.

On the EAR thing: shouldn't that be solved in the dependencyManagement section? That way it'll
work both for eclipse and on the commandline.

Let me know what you think. I feel this change will probably make things worse because it
requires a lot of extra attention from developers,
and makes it much easier for them to commit breaking builds.

> 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

        

Mime
View raw message