sebb wrote: > On 14/11/2009, Christian Grobmeier <grobme...@gmail.com> wrote: >> > >> > > I'm sure glad there is help; there are a few project that are just going >> > / >> > > went through that process (commons-exec for instance) . Is there anyone >> > > involved willing to share their successful publishing process ? >> > >> > We definitely need to do that and it is on my todo list to document >> > the "manual" process that I follow. Basically, we have two ways to >> > do releases now - using the maven release plugin (more or less >> > documented on the Wiki) and "manually" doing the tagging and file >> > movement via the command line. Personally, I prefer the command line >> > approach. >> >> >> >> I have used the M2 approach for compress. It worked, but I sometime felt >> that the process had control bout me and not otherwise. I also run into >> several problems, from which most were based on my own enviroment. However, >> it was no fun at all. Currently I try to build up the release plugin for >> Log4php project, but this is pretty hard too. At the moment, I am tending to >> a proper command line plan. There are too much problems I don't understand >> with M2. >> >> @Henri: I don't know what why the error here happened, but I know that you >> need a clean checkout to make release plugin work proberly. Its not working >> if you have some kind of files from your IDE in your project. > > Seems to me one should _always_ work from a clean check-out, > regardless of the build process. Otherwise the process may not be > repeatable by others, and it's far too easy to accidentally include > spurious files.
+1. This is another reason I like the "manual" approach outlined by Niall above. You know what you are tagging, the tags are immutable and you build the artifacts from a fresh checkout of the tag. Phil > >> Cheers >> >> Christian >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
