Right now release process is: 1) Update version number in build.gradle 2) Commit to SVN, tag in SVN 3) gradle generateRelease 4) Visit Nexus site, close new release
You need some setup for setup 3 and, I believe, some access rights for step 4. On Thu, Sep 1, 2011 at 12:43 PM, Massimo Lusetti <[email protected]> wrote: > On Thu, Sep 1, 2011 at 6:44 PM, Howard Lewis Ship <[email protected]> wrote: > >> That's an open question; we may want a special Gradle task to handle >> this, based on creating a final release (that could then update and >> upload the changed archetype-catalog.xml). Or we could just leave it >> as a manual, once per year-ish task. > > Could you describe your release process, I think you're the only one > producing releases till now right? > > I think that this should be handled by the "release process" which as > a last action could upload the catalog to people.apache.org, right now > the whole archetype and archetype-catalog is built as you do the build > from the main project (root dir) but I think that the upload should > only take place when a full release is made with the publish to the > main maven repo. > > The failsafe option right now is to run it manually and later (maybe > for 5.4 or when my gradle skills are improoved) hook it when needed... > > Cheers > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
