Jason brings up a valid point -- however, we have been using
maven.build.dir=${basedir}/build
and haven't had any plug-in blow up, yet -- at least not because of it :)
As Nick points out, this is a good way to find out if "target" has been hard-coded in
any plug-in!
The docs you are referring to are talking about the case when (and if) you build Maven
itself from source. If you happen to do that simply follow the instructions verbatim
and all will be well.
Sri
> -----Original Message-----
> From: Rauf, Saleem [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 06, 2003 1:12 PM
> To: Maven Users List; [EMAIL PROTECTED]
> Subject: RE: Maven Intergration Question
>
> Hi
>
> I agree with you, but in over company we are using ant to build the
> whole application, we just want to maven to build documentation, Do you
> have any bright ideas?
>
> Also I was looking into changing maven.build.dir value, but it's warning
> me about bootstrap of Maven from source code, as it expects the jar
> created to be in ${basedir}/target/. Can you please give more guidence
> on this.
>
> Below is from Maven docs:
>
> CAUTION: Changing default maven.build.dir value in your
> ${user.home}/build.properties might allow one some control of individual
> project directory layouts. However this practice will interfere with the
> bootstrap of Maven from source code, as it expects the jar created to be
> in ${basedir}/target/
> ${basedir
>
>
> Thanks,
> S-
>
> -----Original Message-----
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 06, 2003 12:07 PM
> To: Maven Users List
> Subject: Re: Maven Intergration Question
>
> On Thu, 2003-11-06 at 12:59, Rauf, Saleem wrote:
> > Is there is a way to customize target folder maven looks at. I wanted
> to
> > looked at build folder instead.
>
> Why do you really want to do this? Most people don't muck with the
> target/ default. If it's simply a personal preference I would recommend
> just sticking with target/ as I'm sure there are some places where
> target/ has been hard-coded by mistake in some plugins because that has
> been the standard for so long.
>
> >
> > Thanks,
> > -S
> >
> > -----Original Message-----
> > From: Vincent Massol [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, November 06, 2003 11:51 AM
> > To: 'Maven Users List'
> > Subject: RE: cactus plugin and overring war:war
> >
> >
> >
> > > -----Original Message-----
> > > From: Brett Porter [mailto:[EMAIL PROTECTED]
> > > Sent: 06 November 2003 07:18
> > > To: 'Maven Users List'
> > > Subject: RE: cactus plugin and overring war:war
> > >
> >
> > [snip]
> >
> > >
> > > Also, plugin:download'ing the latest cactus plugin as per the cactus
> > maven
> > > integration page doesn't work as the dependencies on the cactus jars
> > > themselves are incorrect :)
> >
> > Thanks. I've just put a symlink from 1.6dev to 1.5-rc1 for now.
> >
> > -Vincent
> >
> >
> > ---------------------------------------------------------------------
> > 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]
> --
> jvz.
>
> Jason van Zyl
> [EMAIL PROTECTED]
> http://tambora.zenplex.org
>
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
>
> -- Jacques Ellul, The Technological Society
>
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
