Good day to you, cl29,
I am not sure if I understand your situation perfectly ( your post seems to
be wrapped into one long line ). But you may want to try adding
<project>
...
<properties>
<basedir><!-- your path --></basedir>
</properties>
</project>
See [1] for more info.
Cheers,
Franz
[1] http://maven.apache.org/ref/2.0.4/maven-model/maven.html
cl29 wrote:
>
> we are going to change our cvs, splitting our project into modules and for
> this reason project.xml, build.properties and project.properties are moved
> to a directory. We are still using Maven 1.Old structure:project |_
> build.properties |_ project.properties |_ project.xml |_ src |_ tools |_
> ....New structure: |_ conf |_build.properties
> |_project.properties |_project.xml |_ src |_ tools |_ ...So files
> - usually corresponding to ${basedir} - are no longer in the top level
> directory and goals like scm:update for example working recursive start in
> directory conf and miss all modifications done in src and tools.My
> question is, where do I set ${basedir}, so that I can use all files from
> conf dir, but let basedir="./project"
>
--
View this message in context:
http://www.nabble.com/maven-basedir-tf2963988s177.html#a8313003
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
