Brent, I like the outcome that you are after and mentioned on the site-dev list that I had been toying with patching the maven site plugin to optionally do exactly what you are describing. Others - Hen, Brett - responded that while it is good to have versioned javadoc available on the site, having the site build pull and regenerate it each time is not the best approach, since it never changes. Hen suggested that we might be better off establishing an apache javadoc repo where we can publish these things *once* and then link to them definitively. Hen, Brett pls chime in if I have misrepresented anything.
Can we agree on a definitive location on minotaur/www where we can place versioned javadoc? How about jakarta.apache.org/commons/javadoc/<component>/<release>? I am personally OK with committing your changes if you have this working (including the SCM plugin dependency, as long as it works on both Windoz and linux) and changing to use the repo once we have that sorted. Phil On 5/31/05, Brent Worden <[EMAIL PROTECTED]> wrote: > I've been working on automating the the generation of javadoc for prior > releases for inclusion on the website. The change involves adding a post > goal to the javadoc report goal. The post goal performs a checkout from the > repository for a tagged version of the project. Javadoc is then executed on > the checked out source, placing the generated HTML in a directory at the same > level as the default javadoc. > > One downside to this change is that it requires using version 1.5-beta-3 of > the Maven SCM Plugin. This is needed because prior versions do not support > Subversion. > > If there are no objections, I will commit these changes. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
