Hi Olivier,
I tried the same thing in the root pom. But at the sub module level it was
taking ${my.build.directory} as {basedir}/${my.build.directory}, so the
error that was coming was like could not create *
D:\myProjects\project1\C:\builds\my-artifact-1.0.jar*
Is the any work around to this?
Regards,
Amit
On Mon, Apr 28, 2008 at 5:35 PM, Olivier Dehon <[EMAIL PROTECTED]> wrote:
> Avoid redefining variables that are (or might be) defined by maven
> itself.
>
> Use something like:
>
> <properties>
> <my.build.directory>C:/builds</my.build.directory>
> </properties>
>
> instead.
>
> HTH, -Olivier
>
> On Mon, 2008-04-28 at 16:13 +0530, amit kumar wrote:
> > Hi,
> > I want to create a variable that can take a value of directory path on
> the
> > system and that variable can be read by children projects of the
> project. I
> > tried with
> > <properties>
> > <build.directory>C:\builds</build.directory>
> > </properties>
> >
> > but problem with this is that ${build.directory} seems to be taken as
> > ${basedir}/${build.directory} which ultimately throws an error since the
> > C:\builds is not in the ${basedir}. Any clues?
> >
> > The reason for having having the value in the variable is because I am
> > trying to put all the builds of a project in a dynamic folder named with
> > that particular day's date.
> >
> >
> > Regards,
> > Amit
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
