fine by me. Maurice
On Fri, Apr 11, 2008 at 7:51 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > well, it is convinient to have the sources deployed every time i mvn > install wicket, because i have projects in my eclipse workspace that > depend on those snapshots. the javadoc gen is a nuisance because it > isnt useful and is slow to run. > > -igor > > > > > On Fri, Apr 11, 2008 at 10:31 AM, lars vonk <[EMAIL PROTECTED]> wrote: > > Not directly an answer to your question but a hint related to the topic: > > > > Maven's Super POM (http://maven.apache.org/pom.html#The_Super_POM) already > > has a default profile available that includes the javadoc and sources > > plugin. When you run "mvn clean install -DperformRelease=true" javadoc and > > sources are automatically generated. So there is actually no need to > > configure the javadoc and sources plugin in your own POM (unless you do > > something special of course). > > > > Cheers Lars > > > > > > > > According to the maven docs: http://maven.apache.org/pom.html javadoc and > > source generation is already in the Maven Parent Pom so there is actually > no > > need to include it to your own POM. You can just do mvn install -Prelease > > > > On Fri, Apr 11, 2008 at 6:19 PM, Igor Vaynberg <[EMAIL PROTECTED]> > > wrote: > > > > > > > > > can we disable the javadoc generation for the default build profile? i > > > do mvn install at least a few times a day and javadoc takes ages. can > > > we move that into a release profile or something similar. the sources > > > jar is ok because that just takes a second or two, but javadoc hangs > > > the build for a good while. > > > > > > thoughts? > > > > > > -igor > > > > > >
