You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Igor Vaynberg <ig...@gmail.com> on 2008/04/11 18:19:56 UTC
default build profile
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
Re: default build profile
Posted by Martijn Dashorst <ma...@gmail.com>.
https://issues.apache.org/jira/browse/WICKET-1524
On 4/12/08, Martijn Dashorst <ma...@gmail.com> wrote:
> fixed
>
>
> On 4/11/08, Maurice Marrink <ma...@gmail.com> wrote:
> > fine by me.
> >
> >
> > Maurice
> >
> >
> > On Fri, Apr 11, 2008 at 7:51 PM, Igor Vaynberg <ig...@gmail.com> 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 <la...@gmail.com> 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 <ig...@gmail.com>
> > > > 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
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.2 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
Re: default build profile
Posted by Martijn Dashorst <ma...@gmail.com>.
Still uses the javadoc
Martijn
On 4/12/08, Johan Compagner <jc...@gmail.com> wrote:
> What does bambo build now?
>
>
> On 4/12/08, Martijn Dashorst <ma...@gmail.com> wrote:
>
> > fixed
> >
> > On 4/11/08, Maurice Marrink <ma...@gmail.com> wrote:
> > > fine by me.
> > >
> > >
> > > Maurice
> > >
> > >
> > > On Fri, Apr 11, 2008 at 7:51 PM, Igor Vaynberg <ig...@gmail.com>
> > 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 <la...@gmail.com>
> > 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
> > <ig...@gmail.com>
> > > > > 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
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> > Buy Wicket in Action: http://manning.com/dashorst
> > Apache Wicket 1.3.2 is released
> > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
> >
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
Re: default build profile
Posted by Johan Compagner <jc...@gmail.com>.
What does bambo build now?
On 4/12/08, Martijn Dashorst <ma...@gmail.com> wrote:
> fixed
>
> On 4/11/08, Maurice Marrink <ma...@gmail.com> wrote:
> > fine by me.
> >
> >
> > Maurice
> >
> >
> > On Fri, Apr 11, 2008 at 7:51 PM, Igor Vaynberg <ig...@gmail.com>
> 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 <la...@gmail.com>
> 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
> <ig...@gmail.com>
> > > > 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
> > > > >
> > > >
> > >
> >
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.2 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
>
Re: default build profile
Posted by Martijn Dashorst <ma...@gmail.com>.
fixed
On 4/11/08, Maurice Marrink <ma...@gmail.com> wrote:
> fine by me.
>
>
> Maurice
>
>
> On Fri, Apr 11, 2008 at 7:51 PM, Igor Vaynberg <ig...@gmail.com> 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 <la...@gmail.com> 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 <ig...@gmail.com>
> > > 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
> > > >
> > >
> >
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
Re: default build profile
Posted by Maurice Marrink <ma...@gmail.com>.
fine by me.
Maurice
On Fri, Apr 11, 2008 at 7:51 PM, Igor Vaynberg <ig...@gmail.com> 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 <la...@gmail.com> 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 <ig...@gmail.com>
> > 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
> > >
> >
>
Re: default build profile
Posted by Igor Vaynberg <ig...@gmail.com>.
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 <la...@gmail.com> 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 <ig...@gmail.com>
> 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
> >
>
Re: default build profile
Posted by lars vonk <la...@gmail.com>.
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 <ig...@gmail.com>
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
>