Wendy Smoak-3 wrote:
>
> On 12/29/06, mraible <[EMAIL PROTECTED]> wrote:
>
>> I'm assuming you use the assembly plugin to create sources and javadocs?
>
> No... that would be done with the source and javadoc plugins. It
> should be happening when the "pre-assembly" profile is enabled, but I
> don't actually see that defined anywhere in the Struts 2 build.
>
> It looks like this (from the Struts 1 core module):
> http://svn.apache.org/repos/asf/struts/struts1/trunk/core/pom.xml
>
> (That profile is mis-named. Originally we were just including the
> -sources and -javadoc jars in the assembly rather than the entire
> website and full source code with build files.)
>
> Unless I'm missing something, the Struts 2 build doesn't produce
> -sources and -javadoc jars right now.
>
>> 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?
>
> Did you see the notes at the bottom of the wiki page? Ted will have
> to comment if you have more questions, as far as I know there's the
> autoexport plugin, then a cron job that zips up the exported site.
> (Or else he just runs it manually to pick up last minute changes.)
> That's the "docs.zip" that the wiki page says to download and include
> in the distribution.
>
> All in all, I'm not so sure the Struts 2 build is a good example. :)
>
Do you know know of a better example that uses Confluence for its
documentation?
Thanks,
Matt
--
View this message in context:
http://www.nabble.com/Is-there-a-documented-release-process-for-Struts-2--tf2897387.html#a8095524
Sent from the Struts - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
