Typically remote tags are created automatically (or will once I'm finished) doing mvn release:prepare release:perform (well, they'll be pushed asap they're created locally). This behavior though has one big disadvantage. Assume that you've missed anything in the release process (e.g. your uploaded artifacts are rejected by oss.sonatype.org, or anything else). If your tags/branches are directly pushed to your remote repo you need to start over again with a completely new release and tag (since you don't want to change the history upstream). BUT if you created the tags and commits only locally you can first complete the release and IFF everything went fine you push the commits and tags; otherwise simply throw them away and start anew.
Hope this makes it clear now. BTW, yes I'll update the Release page too. On Tue, May 15, 2012 at 5:35 PM, Harald Wellmann <hwellmann...@googlemail.com> wrote: > +1 > ...but don't forget to update > http://team.ops4j.org/wiki/display/ops4j/Releasing :-) > > > > Am 15.05.2012 15:18, schrieb Andreas Pieber: > >> >> mvn release:prepare release:perform (add this for local tags >> -DconnectionUrl=scm:git:file://`pwd`) >> > > Can you explain? I'd say you always want remote tags and not just local > ones. I remember ending up with local tags only when doing a release, but > I'm not sure why, and I'm not friends with Git anyway... > > Regards, > Harald > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
