Yep, I agree with Odi. #2 seems like the way to go. Mike
On 4/9/06, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > Folks, > > I spent a good half of yesterday struggling with the Maven2 release > plug-in. After having spent several hours I am still unable to make > Maven2 do what I want. > > The trouble is that the current layout of HttpComponents repository does > not seem to conform to Maven SVN layout guidelines. Presently > HttpComponent modules do not have separate trunk/tag/branch folders. > They share a common trunk and therefore must share common tags and > branches folders as well. The SVN layout looks something like that > > /repos/asf/jakarta/httpcomponents > trunk > http-core > http-async > http-client > ... > tags > http-core-4.0-alpha1 > http-core-4.0-alpha2 > http-client-4.0-alpha1 > ... > > That doesn't seem to be compatible with the way Maven2 release plug-in > functions. It appears Maven can only work with the following SVN layout > > /repos/asf/jakarta/httpcomponents > http-core > trunk > tags > 4.0-alpha1 > 4.0-alpha2 > ... > http-client > trunk > tags > 4.0-alpha1 > ... > > Essentially, we have two options here > (1) keep things as they are at the moment thus probably having to manage > the release process manually > (2) restructure the repository in order to make Maven2 happy. Since we > have not had a single official release to this point now would be the > least disruptive moment to go ahead with such restructuring > > Opinions? > > Oleg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
