Re: maven basedir
cl29 wrote:
>
> Good day to you, Franz!
> Good day to Arnaud!
> Thanks for your fast reply and sorry for my late reply.
> I have tested this with Maven2 now, and basedir properties in conf/pom.xml
> as you mentioned below, but scm:update announces as workingdir
> project/conf and by this does not update all files and directories;
> updates: all files/subdirs from conf
> missing: src, tools, ...directories and subdirectories.
>
> Any idea to solve the problem?
> I tried with relative path ans absolute paths in pom.xml
>
> project
> conf/pom.xml
> src/
> tools/
> /
>
> calling mvn from conf-dir
> # mvn scm:update
>
> Cheers,
> Claudia
>
>
> franz see wrote:
>>
>> Good day to you, Arnaud,
>>
>> Pardon, I failed to read that part about the maven version :-)
>>
>> Thanks for the correction.
>>
>> - Franz
>>
>>
>> Arnaud HERITIER wrote:
>>>
>>> These settings are working only with maven 2.X.
>>> Not m1.x
>>>
>>> Arnaud
>>>
>>> On 1/13/07, franz see <[EMAIL PROTECTED]> wrote:
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
...
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]
>>>
>>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/maven-basedir-tf2963988s177.html#a8434825
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven basedir
Good day to you, Arnaud,
Pardon, I failed to read that part about the maven version :-)
Thanks for the correction.
- Franz
Arnaud HERITIER wrote:
>
> These settings are working only with maven 2.X.
> Not m1.x
>
> Arnaud
>
> On 1/13/07, franz see <[EMAIL PROTECTED]> wrote:
>>
>>
>> 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
>>
>>
>> ...
>>
>>
>>
>>
>>
>> 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]
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/maven-basedir-tf2963988s177.html#a8348696
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven basedir
These settings are working only with maven 2.X.
Not m1.x
Arnaud
On 1/13/07, franz see <[EMAIL PROTECTED]> wrote:
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
...
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]
Re: maven basedir
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
...
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]
