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.
On Thu, Sep 1, 2011 at 12:33 AM, Massimo Lusetti <[email protected]> wrote: > Hi all, > To close TAP5-1609 I simply need to hook the publishing of the newly > generate archetype-catalog.xml to tapestry.apache.org site. > > I managed to get the job done with the relative ant task but I would > like to ask where do you want this hooked in the build lifecycle... > > I mean there's a doc on how to produce a release? Is the "release" > task the right place where put the hook to scp-ing the catlog? > > 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]
