maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Elliot Metsger <>
Subject Re: Status of MRELEASE-835?
Date Thu, 06 Mar 2014 03:11:55 GMT
I've been using a version of the patch locally, and it's been helpful.

We have a relatively large project, with multiple modules that can be
versioned independently of each other.  Ultimately, these modules get
packaged into a war at release time.  In order to insure that these modules
use the same version of dependencies, they inherit from a parent pom that
contains a huge <dependencyManagement> element; every <dependency> is
defined there (~90 managed SNAPSHOT deps).

So when we perform a release, we need to resolve the SNAPSHOT versions in
the parent pom, and that is where the patch attached to MRELEASE-835 is
quite useful.  We can release the parent pom, and resolve the managed

Things get a little trickier when releasing the descendant modules, because
the check-dependency-snapshots phase will ask you to re-resolve the managed
dependencies from the parent.  So for each sub-module of the parent, you're
potentially answering a lot of versioning prompts - you're re-resolving the
same set of managed dependencies over and over.  Because our sub-modules
can be independently versioned, we have problems using batch mode and
setting the dependencies from system properties.

Maybe we have a not-ideal project structure, or we're missing some best
practices that we could be applying that could make our release process
easier.  But my immediate thought is that it would be nice for the version
maps for managed dependencies to somehow be made available across Project
releases, maybe in the release descriptor, so that you aren't re-prompted
each time.  It would be really nice if we could define the version maps a
priori, using an easier (?) serialization than a Properties file.  I have a
lot of local hacks that I'd be willing to share, if they'd be considered


On Wed, Mar 5, 2014 at 4:06 PM, Robert Scholte <> wrote:

> Hi,
> I'll look into that.
> For the last couple of releases I've picked up a specific part of the
> plugin and tried to gather all related issues.
> The number of open issues is still huge (and some very old) so it takes
> some time to analyze every issue.
> However, this kind of reminders can help.
> Robert
> Op Wed, 05 Mar 2014 15:29:45 +0100 schreef Thorsten Heit <
>  Hi,
>> last year in april I added an enhancement request for the release plugin
>> that allows a user to automatically resolve snapshot dependencies in
>> release:prepare, i.e. there's no interaction necessary; see MRELEASE-835.
>> I also added a patch I made using the source code of version 2.4.1 that is
>> still applicable even the recently released version 2.5.
>> Since the issue was added, there has been no activity on it; it also isn't
>> assigned to someone, and as far as I have seen there have been at least
>> two similar requests:
>> * MRELEASE-463 from 2009 (also with a patch provided)
>> * MRELEASE-854 from last november, marked as duplicate of MRELEASE-463
>> I just wanted to know what the actual status is? Is there no need for such
>> a IMHO usable and CI- and/or build-server friendly feature? Is there
>> anything missing in the issue/patch/description/...?
>> At least a comment such as "I'll look into that" would be nice :-)
>> Regards
>> Thorsten
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message