maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <mgai...@hotmail.com>
Subject RE: AW: AW: AW: mvn release:prepare does not update parent version
Date Sat, 09 Nov 2013 23:41:16 GMT

  


> Date: Sat, 9 Nov 2013 08:31:21 -0500
> Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version
> From: gordon.cody@zafin.com
> To: users@maven.apache.org
> 
> You may want to upgrade maven itself once more. It is not just maven itself
> but the combination of plugins that are used and your environment matters.
> Ensure that each maven goal you plan on using in your environment actually
> works in your environment before you need it for real. Maven has to work
> with your vcs,
MG>dev .. svn but in prod.. git was used 
 
 your artifact mgmt (nexus/artifactory/other),
MG>ours was nexus but I can see configuration deltas biting the release manager

 your network security policies,
MG>we could download point releases 
MG>mega updates from http sites located outside the firewall were and are a no-no
MG>and could get you in hot water real quick in a 'secure' environment (such as a bank)
 
etc. all at the same time.
> 
> When we began upgrading existing projects from mvn-2.0.9 we had to also
> upgrade numerous plugins. It took some effort to find the combination of
> plugins/configuration that allowed us to do 'mvn deploy' successfully with
> mvn-3.0.4. But 'mvn release' did not work in our environment until
> mvn-3.0.5 was released!!
MG>Another big delta
MG>What are the implications for this delta to your dependency object graph?

MG>for child <module>s What are the implications for this delta to your object graph?
 
. Underlying plugin(s) had changed.

MG>Exactly..What are the implications for your plugins object graph?
MG>look at this dependency from maven-release-plugin
    <dependency>
      <groupId>org.apache.maven.release</groupId>
      <artifactId>maven-release-manager</artifactId>
      <version>${project.version}</version>
    </dependency>
MG>notice maven-release-plugin and maven-release-manager are inextricably linked on same
version
MG>the release-manager plugin prompts the user for version specific questions
MG>maven-release-plugin is the plugin that does the work from the questions asked by release-manager
MG>follow up question: why the separation?

> Regards, Gord
MG>Well put Gordon!!! 
> 
> On Sat, Nov 9, 2013 at 4:55 AM, Markus Karg <karg@quipsy.de> wrote:
> 
> > Robert,
> >
> > no need to teach me about completeness of reports -- I am in the reverse
> > situation day by day as you can imagine. The problem was that I had the
> > problem since I migrated to Maven 3 from day one with even the smallest
> > possible POM (it looked 'obvious' to me) and did not have the idea there
> > might be a fix already already which is not contained in Maven 3 so far. In
> > fact this is why I would love to have the ability to use version ranges in
> > plugin dependencies! ;-)
> >
> > Anyways, as all is fixed now, thanks for the kind help! :-)
> > -Markus
> >
> > -----Original Message-----
> > From: Robert Scholte [mailto:rfscholte@apache.org]
> > Sent: Freitag, 8. November 2013 18:52
> > To: Maven Users List
> > Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version
> >
> > Op Fri, 08 Nov 2013 16:30:30 +0100 schreef Markus Karg <karg@quipsy.de>:
> >
> > > I wonder why someone fixed it but didn't close
> > > https://jira.codehaus.org/browse/MRELEASE-837...!
> >
> > Well, is was probably already fixed for a long time. Since you only had a
> > description it will take some time to fix it, since it must first be
> > reproducible. That's why attaching a sample project helps, and a patch with
> > a possible fix even more.
> >
> > In this case it was the log-file which triggered me: first update the
> > version of the plugin and see if it has been already been fixed.
> >
> > It is all about being as complete as possible :)
> >
> > Robert
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> 
> 
> -- 
> Best Regards, Gord Cody
> 
> Release Manager Zafin Labs Americas Inc.
> 179 Colonnade Road-Suite 100, Ottawa ON, Canada
> Phone: +1 (613) 216-2504 Fax: +1 (613) 688-1374 Mobile: +1 613-601-2734
> Web: http://zafin.com Email: gordon.cody@zafin.com
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message