You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by jcaddel <jc...@yahoo.com> on 2010/02/22 01:56:29 UTC

Releasing parent poms

Could someone from the dev team possibly post the sequence of commands used
to release parent poms such as:

http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml


I've read the  http://maven.apache.org/plugins/maven-release-plugin/faq.html
faq  that talks about using -N 
mvn -N -Darguments=-N release:prepare
mvn -N -Darguments=-N release:perform

What wins between -Darguments=-N vs the plugin config from the main 
http://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml pom :

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-release-plugin</artifactId>
  <version>2.0-beta-9</version>
  <configuration>
    <useReleaseProfile>false</useReleaseProfile>
    <goals>deploy</goals>
    <arguments>-Papache-release</arguments>
  </configuration>
</plugin>

Wouldn't -Darguments=-N trample the -Papache-release setting?



-- 
View this message in context: http://old.nabble.com/Releasing-parent-poms-tp27681587p27681587.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Releasing parent poms

Posted by jcaddel <jc...@yahoo.com>.
<snip>
There's a much simpler solution. Don't aggregate through your parent.
Don't put modules in it. Put it in  directory by itself, and then the
release process is completely straightforward.
<snip>

That would make the releasing of a standalone parent pom easier, but isn't
what I am looking for.

My pom needs to retain its parent and also have modules, exactly like the
parent pom I linked to.

There must be an easy way, to version, tag, and release 
http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml this  pom.  They
have done it 18 times now. :)


-- 
View this message in context: http://old.nabble.com/Releasing-parent-poms-tp27681587p27682411.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Releasing parent poms

Posted by Benson Margulies <bi...@gmail.com>.
There's a much simpler solution. Don't aggregate through your parent.
Don't put modules in it. Put it in  directory by itself, and then the
release process is completely straightforward.

On Sun, Feb 21, 2010 at 7:56 PM, jcaddel <jc...@yahoo.com> wrote:
>
> Could someone from the dev team possibly post the sequence of commands used
> to release parent poms such as:
>
> http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml
>
>
> I've read the  http://maven.apache.org/plugins/maven-release-plugin/faq.html
> faq  that talks about using -N
> mvn -N -Darguments=-N release:prepare
> mvn -N -Darguments=-N release:perform
>
> What wins between -Darguments=-N vs the plugin config from the main
> http://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml pom :
>
> <plugin>
>  <groupId>org.apache.maven.plugins</groupId>
>  <artifactId>maven-release-plugin</artifactId>
>  <version>2.0-beta-9</version>
>  <configuration>
>    <useReleaseProfile>false</useReleaseProfile>
>    <goals>deploy</goals>
>    <arguments>-Papache-release</arguments>
>  </configuration>
> </plugin>
>
> Wouldn't -Darguments=-N trample the -Papache-release setting?
>
>
>
> --
> View this message in context: http://old.nabble.com/Releasing-parent-poms-tp27681587p27681587.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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