You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Stéphane Philippart <st...@prima-solutions.com> on 2003/12/11 10:41:29 UTC
How set maven.build.dest in project.xml ?
Hello,
I want to set the maven.build.dest to the 'build' value, when i do that
in a project.properties of each sun projects with :
maven.build.dest=${basedir}/build/ everything is find !
But i don't want to do that for all my sub-projects so i want to put
this property in the project.xml of my projects main project and
inherite it in my sub projects.
I put the lines :
<properties>
<maven.build.dest>build</maven.build.dest>
</properties>
in the root projetc.xml.
The other parameters (like dependencies, build for example) are well
inherited the properties seems not inherited. In the archive thread i
read it will be having problems for inheritance of properties in the
project.xml.
Does it work ? If yes what i have did wrong ?
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: How set maven.build.dest in project.xml ?
Posted by "J. Matthew Pryor" <jm...@yahoo.com>.
+1
I have had to integrate maven into projcet where for varous reasons, it was
easier to have maven build into a different directory
I think flexibility is the key, and also not being to rigind about such
things. I can see the need to justify the requirements, but as I say I have
used maven in 2 situations where is was *easier* at the time ot change the
name of the "target" folder. Not that it couldn't have been done another way
that didn't require that, but at the time it was (or would have been) easier
i.e. if I start work on an existing project with many members and the
project is not currently mavenized & I can't simply change it wholesale. I
want to gradually introduce maven but not disrupt the way people are
currently doing thaings
In fact by that argument, this feature will arguably enhance the adoption of
maven by making it easier to introduce maven into existing projects. That
was cerainly my case.
Matthew
> -----Original Message-----
> From: W. Sean Hennessy [mailto:shennessy@goldenhourdata.com]
> Sent: Friday, December 12, 2003 8:32 AM
> To: 'Maven Users List'
> Subject: RE: How set maven.build.dest in project.xml ?
>
>
>
> The advantage being Maven would be able to service the
> requirement for one group's choice of "target" and another
> group's use of "build" for the name of the result tree without
> the need to instrument a directory rename or dir copy
> goal.
>
> Do I really care that much if all classes are output to "target/"?
> Personally it does not matter which to me.
> Would like to be able to accommodate a different name be it
> "build", "target", "diskimage", "bin", "cible" or "Ziel".
>
> My interest is in the flexibility to accomodate such changes.
> Given the bandwith and any level of confidence in my jelly
> skillset I would volunteer to contribute.
>
>
> -----Original Message-----
> From: Jason van Zyl [mailto:jvanzyl@maven.org]
> Sent: Thursday, December 11, 2003 11:47 AM
> To: Maven Users List
> Subject: RE: How set maven.build.dest in project.xml ?
>
>
> On Thu, 2003-12-11 at 12:06, W. Sean Hennessy wrote:
> > Jason,
> >
> > Please, I beseech you to reconsider the "make target/ your only
> > choice" limitation. We acknowledge that a standard directory structure
> > facilitates maintenance. However, please, consider that the specific
> > folder naming could be defined as configurable items. We still
> > benefit from the existing directory the structure and the jelly
> > scripts behavior is preserved.
> >
> > "target/" becomes "${target-dir-nm}/" in build.xml and jelly.
> >
> > with
> > # ------------------
> > # build.properties
> > # ------------------
> > bin-dir-nm=bin
> > target-dir-nm=target
> > conf-dir-nm=conf
> > dist-dir-nm=dist
> > lib-dir-nm=lib
> > sql-dir-nm=sql
> > src-dir-nm=src
> > tst-dir-nm=test
> > web-dir-nm=web
> > xdoc-dir-nm=xdoc
> >
> > Thanks for your consideration.
> >
>
> Ok, in your opinion what would be the advantage of making these
> things above configurable? Do you really care that much
> if all classes are output to target/ ?
>
> --
> jvz.
>
> Jason van Zyl
> jason@zenplex.com
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: How set maven.build.dest in project.xml ?
Posted by "W. Sean Hennessy" <sh...@goldenhourdata.com>.
The advantage being Maven would be able to service the requirement for one group's choice of "target" and another
group's use of "build" for the name of the result tree without the need to instrument a directory rename or dir copy
goal.
Do I really care that much if all classes are output to "target/"?
Personally it does not matter which to me.
Would like to be able to accommodate a different name be it "build", "target", "diskimage", "bin", "cible" or "Ziel".
My interest is in the flexibility to accomodate such changes.
Given the bandwith and any level of confidence in my jelly skillset I would volunteer to contribute.
-----Original Message-----
From: Jason van Zyl [mailto:jvanzyl@maven.org]
Sent: Thursday, December 11, 2003 11:47 AM
To: Maven Users List
Subject: RE: How set maven.build.dest in project.xml ?
On Thu, 2003-12-11 at 12:06, W. Sean Hennessy wrote:
> Jason,
>
> Please, I beseech you to reconsider the "make target/ your only
> choice" limitation. We acknowledge that a standard directory structure
> facilitates maintenance. However, please, consider that the specific
> folder naming could be defined as configurable items. We still
> benefit from the existing directory the structure and the jelly
> scripts behavior is preserved.
>
> "target/" becomes "${target-dir-nm}/" in build.xml and jelly.
>
> with
> # ------------------
> # build.properties
> # ------------------
> bin-dir-nm=bin
> target-dir-nm=target
> conf-dir-nm=conf
> dist-dir-nm=dist
> lib-dir-nm=lib
> sql-dir-nm=sql
> src-dir-nm=src
> tst-dir-nm=test
> web-dir-nm=web
> xdoc-dir-nm=xdoc
>
> Thanks for your consideration.
>
Ok, in your opinion what would be the advantage of making these things above configurable? Do you really care that much
if all classes are output to target/ ?
--
jvz.
Jason van Zyl
jason@zenplex.com
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: How set maven.build.dest in project.xml ?
Posted by Jason van Zyl <jv...@maven.org>.
On Thu, 2003-12-11 at 12:06, W. Sean Hennessy wrote:
> Jason,
>
> Please, I beseech you to reconsider the "make target/ your only choice" limitation.
> We acknowledge that a standard directory structure facilitates maintenance.
> However, please, consider that the specific folder naming could be defined as configurable items. We still benefit from
> the existing directory the structure and the jelly scripts behavior is preserved.
>
> "target/" becomes "${target-dir-nm}/" in build.xml and jelly.
>
> with
> # ------------------
> # build.properties
> # ------------------
> bin-dir-nm=bin
> target-dir-nm=target
> conf-dir-nm=conf
> dist-dir-nm=dist
> lib-dir-nm=lib
> sql-dir-nm=sql
> src-dir-nm=src
> tst-dir-nm=test
> web-dir-nm=web
> xdoc-dir-nm=xdoc
>
> Thanks for your consideration.
>
Ok, in your opinion what would be the advantage of making these things
above configurable? Do you really care that much if all classes are
output to target/ ?
--
jvz.
Jason van Zyl
jason@zenplex.com
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: How set maven.build.dest in project.xml ?
Posted by "W. Sean Hennessy" <sh...@goldenhourdata.com>.
Jason,
Please, I beseech you to reconsider the "make target/ your only choice" limitation.
We acknowledge that a standard directory structure facilitates maintenance.
However, please, consider that the specific folder naming could be defined as configurable items. We still benefit from
the existing directory the structure and the jelly scripts behavior is preserved.
"target/" becomes "${target-dir-nm}/" in build.xml and jelly.
with
# ------------------
# build.properties
# ------------------
bin-dir-nm=bin
target-dir-nm=target
conf-dir-nm=conf
dist-dir-nm=dist
lib-dir-nm=lib
sql-dir-nm=sql
src-dir-nm=src
tst-dir-nm=test
web-dir-nm=web
xdoc-dir-nm=xdoc
Thanks for your consideration.
Sean
-----Original Message-----
From: Jason van Zyl [mailto:jvanzyl@maven.org]
Sent: Thursday, December 11, 2003 5:35 AM
To: Maven Users List
Subject: Re: How set maven.build.dest in project.xml ?
On Thu, 2003-12-11 at 04:41, Stéphane Philippart wrote:
> Hello,
>
> I want to set the maven.build.dest to the 'build' value, when i do
> that in a project.properties of each sun projects with :
> maven.build.dest=${basedir}/build/ everything is find !
I'll ask why you really want to do this and second that in coming versions I would like to make target/ your only
choice.
> But i don't want to do that for all my sub-projects so i want to put
> this property in the project.xml of my projects main project and
> inherite it in my sub projects.
>
> I put the lines :
> <properties>
> <maven.build.dest>build</maven.build.dest>
> </properties>
> in the root projetc.xml.
>
> The other parameters (like dependencies, build for example) are well
> inherited the properties seems not inherited. In the archive thread i
> read it will be having problems for inheritance of properties in the
> project.xml.
>
> Does it work ? If yes what i have did wrong ?
Why do you even want to do this?
> Thanks
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>
> For additional commands, e-mail: users-help@maven.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: How set maven.build.dest in project.xml ?
Posted by Jason van Zyl <jv...@maven.org>.
On Thu, 2003-12-11 at 04:41, Stéphane Philippart wrote:
> Hello,
>
> I want to set the maven.build.dest to the 'build' value, when i do that
> in a project.properties of each sun projects with :
> maven.build.dest=${basedir}/build/ everything is find !
I'll ask why you really want to do this and second that in coming
versions I would like to make target/ your only choice.
> But i don't want to do that for all my sub-projects so i want to put
> this property in the project.xml of my projects main project and
> inherite it in my sub projects.
>
> I put the lines :
> <properties>
> <maven.build.dest>build</maven.build.dest>
> </properties>
> in the root projetc.xml.
>
> The other parameters (like dependencies, build for example) are well
> inherited the properties seems not inherited. In the archive thread i
> read it will be having problems for inheritance of properties in the
> project.xml.
>
> Does it work ? If yes what i have did wrong ?
Why do you even want to do this?
> Thanks
> ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>
> For additional commands, e-mail: users-help@maven.apache.org
--
jvz.
Jason van Zyl
jason@zenplex.com
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org