Thx but that does not work ... continuum does not expand the '.' in some
valid path.
I also try -Droot.dir=`pwd` but it does not work too :(
And I try a strange var named '${curr-scm-root}' who does not work ...
Some other ideas ? :)
Emmanuel Venisse a écrit :
You can try -Droot.dir=.
continuum start maven in the working directory so '.' is correct
Emmanuel
B. De Mezzo a écrit :
During the test phase, I need some property files located in
'svn-checkouted-dir/conf' (for example). This 'svn-checkouted-dir' is
managed by continuum and is on the form :
'continuum-install-path/apps/continuum/workingdir/1/' or something
like that. So I need a solution to say to maven and to my test that
the root project dir is
'continuum-install-path/apps/continuum/workingdir/1/'. For example
with a '-Droot.dir=${the.fucking.var.I.look.for}' when I define in
continuum a 'build definition' to run maven.
Obviously, I rather prefere to use a property or an env var than to
fix directly in my pom.xml the current path used by continuum ...
Thx !
BDM.
Emmanuel Venisse a écrit :
What do you try to do exactly?
Do you want the working directory or the path of the target directory?
Emmanuel
B. De Mezzo a écrit :
B. De Mezzo a écrit :
hello,
I am looking for a property to pass througth maven to get the
absolute path location of the current build working directory.
Does it exist ? If not, have you got an idea to get this piece of
information ?
Thx,
BDM.
update:
- ${basedir} is not a good solution because it changes for each
project in multi-module project.
- And when I use a piece of ant code within maven (in some
<configuration><task>...</task></configuration>), the modification,
I have done onto an ant-style property, is not visible back in maven.
- Using profiles to set a property according to an existing file or
an existing property (to do distinction between root project and
module project levels) does not work too ...
I am becoming disappointed ...
HHEEELLLPPP :)
Thx,
BDM.
