Shouldn't there be a "release candidate" profile in your pom.xml file that turns on the javadocs? I agree that the javadocs shouldn't be generated by merely typing mvn install, but it should be part of your release candidates (and releases of course). That can be turned on by doing mvn -Prc install.
On Mon, Apr 21, 2008 at 1:50 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > it should be in the changelog: > > https://issues.apache.org/jira/browse/WICKET-1524 > > -igor > > > > > On Mon, Apr 21, 2008 at 10:38 AM, C. Bergström <[EMAIL PROTECTED]> wrote: > > > > On Mon, 2008-04-21 at 10:36 -0700, Igor Vaynberg wrote: > > > mvn install wont generate javadoc by default anymore because it is a > > > lengthy task. javadoc will still be available from m2 repo, eg > > > > > > > http://people.apache.org/~frankbille/releases/apache-wicket-1.4-m1/m2-repo/org/apache/wicket/wicket/1.4-m1/ > > > > If it's not in the release notes/changelog. we should make an additional > > note of this.. > > > > >
