On Sun, 2007-06-10 at 12:33 +0200, Daniel Mueller wrote: > Hi Oleg, > > Which one of the stated variants could be implemented? I have not the > slightest clue about how you actually do releases, so it's a bit difficult > to help.
Hi Daniel, I still need to document the release process in more details [1] which I intend to do in the course of the coming ALPHA5 release. Currently I build release assemblies in a semi-manual fashion. I usually deploy the release artifacts to the Maven repository first, then I run javadoc and clover reports and finally build the release assemblies to be made available for download. I leave the decision as to which approach to take up to you. See what makes more sense. I guess the simpler the better. I also do not expect it to be fully hands-free. I think it is reasonable to expect some degree of intelligence from the release manager, so some manual interactions during the release process are fine by me. Cheers, Oleg [1] https://issues.apache.org/jira/browse/HTTPCORE-62 > Are they done by hand and then provided to the maven team? Or are > they somehow done automatically. I think at least for the continuous > integration stuff (built by gump, I asume) you'd have to change the invoked > command. > > Cheers, > Daniel > > On 6/9/07, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote: > > > > Hi Daniel, > > > > We are basically using Ant scripts for those development tasks where > > speed really matters (compile / run test cycle) and Maven2 for more > > complex tasks such as cutting and deploying releases. Two build systems > > can coexist in parallel as long as both are maintained. > > > > > I have only checked httpcomponents-core, but I assume this applies to > > the > > > other httpcomponent projects as well. If you change a pom I propose to > > > change the org.apache.httpcomponents:project pom, because then every > > > subcomponent inherits the changes. The changes to the build process > > should > > > be also for every project. > > > > > > This post is pretty extensive, but I saw on the mailinglist that at > > least > > > Roland didn't like Maven too much a year ago [5]. I don't know if this > > has > > > changed, or if I can help with any outstanding issues. I don't consider > > > myself to be authorative on maven, but I switched recently all projects > > at > > > our workplace from ant builds to maven. The projects were large'ish and > > > included a big hierarchical project with ~50 subcomponents, each built > > by > > > its own ant build script. In the end we had practically built our own > > maven > > > with ant, which was the point to reconsider. The transition went without > > > major problems beside the usual 'Doh, how am I gonna solve this one'... > > I'm > > > not saying maven solved everything nicely but in the end it was a > > net-gain. > > > > > > > I was a long time Maven skeptic and only recently started warming up to > > it. To me Maven really shines at reducing costs of splitting complex > > libraries into multiple single purpose modules, which in its turn helps > > reduce the number of requisite external dependencies for the upstream > > users. It was also my experience that maintaining a large number of > > sub-modules using Ant tended to be significantly more laborious and > > error-prone. > > > > So, please do feel free to go ahead and submit patches for proposed > > changes. I hope Roland will not veto it. > > > > Cheers > > > > Oleg > > > > > > > > > > Thanks and keep up the good work > > > Dan > > > > > > [1] http://maven.apache.org/plugins/maven-source-plugin/ > > > [2] > > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > > > [3] > > http://maven.apache.org/guides/introduction/introduction-to-the-pom.html > > > [4] > > > > > http://maven.apache.org/guides/introduction/introduction-to-profiles.html > > > [5] > > > > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg04234.html > > > > > > --------------------------------------------------------------------- > > 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]
