On Apr 25, 2007, at 5:03 PM, Paul Smith wrote:
Thanks for fixing the site.xml stuff, site generation seems to be working now locally. I'm taking that the approach you're aiming at is such that at some point a 'mvn deploy' style command will build the distribution and site and auto-upload everything to the repository automatically?
Won't ever be quite that automatic since we need to hold a vote on the bits for releases.
Hopefully pushing the site content can be done with a maven deploy. I'm guessing Maven has some way that you can stage the content to a test site, but I've currently hard-coded my public_html path. Basically, it tarballs up the local content, uploads the tarball and extracts on the deployment site. Had to put an entry in my settings.xml to provide my user id on people.apache.org since it is not the same as my local user id.
I'm thinking that each product would have a base URL within http:// logging.apache.org and that there would be a web content only Maven project that would handle the general logging services content, the log4j companions content and any other
The Building Better Builds With Maven book (free as in beer at least) has a chapter on reproducible builds with Maven that I'll have to work through. You have to capture all the version numbers on the Maven plugins or you'll build may differ based on a change in the downloaded plugins.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
