I'm assuming you use the assembly plugin to create sources and javadocs? What about documentation? It looks like you're using the AutoExport Plugin for Confluence. How are you handling the "export documentation" process when it comes to releases?
Thanks, Matt Wendy Smoak-3 wrote: > > On 12/29/06, mraible <[EMAIL PROTECTED]> wrote: > >> Is there a documented release process for Struts 2? >> >> How do you create the JARs, sources, javadocs and upload them to a Maven >> repo? >> >> We're using Maven 2 in AppFuse, so I figured we could probably follow a >> pre-existing solution rather than coming up with our own. > > It's a work in progress... > http://cwiki.apache.org/WW/creating-and-signing-a-distribution.html > > The 'mvn deploy' step puts everything in a staging repository. After > the vote, we copy it over to another repo (internal to Apache) that > gets automatically synced to the central Maven repository. > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Is-there-a-documented-release-process-for-Struts-2--tf2897387.html#a8095387 Sent from the Struts - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
