Re: Configure 'finalName' pattern for all child modules

2011-10-16 Thread Stanimir Stamenkov

Wed, 12 Oct 2011 17:42:59 -0700, /Manfred Moser/:

11-10-12 05:30 PM, Yuen-Chi Lian wrote:


 parent
 groupIdy/groupId
 artifactIdx/artifactId
 versionv/version
 relativePath../parent/relativePath


  Dont use relative path  ...


Why it is not good?  I ask because the m2e plugin for Eclipse 
automatically generates:


  parent
...
relativePath../relativePath
  /parent

for new child modules.  As far as I understand the above is the 
default - is there a difference if it is specified explicitly?


--
Stanimir

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Configure 'finalName' pattern for all child modules

2011-10-12 Thread Stanimir Stamenkov
I want to configure the 'finalName' for a parent module and all its 
child modules as:


build
finalName${artifactId}/fileName
/build

Is there a way to configure this as a default pattern in the parent 
and avoid repeating it in the 'build' section for all child modules?


--
Stanimir

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Configure 'finalName' pattern for all child modules

2011-10-12 Thread Yuen-Chi Lian
Yes. Have you tried?

$ cat parent/pom.xml | grep finalName

finalName${project.artifactId}-${project.version}-b${buildNumber}/finalName

In the child:

parent
groupIdy/groupId
artifactIdx/artifactId
versionv/version
relativePath../parent/relativePath

Yuen-Chi Lian | www.yclian.com
I do not seek; I find. - Pablo Picasso



2011/10/13 Stanimir Stamenkov s7a...@netscape.net

 I want to configure the 'finalName' for a parent module and all its child
 modules as:

build
finalName${artifactId}/**fileName
/build

 Is there a way to configure this as a default pattern in the parent and
 avoid repeating it in the 'build' section for all child modules?

 --
 Stanimir

 --**--**-
 To unsubscribe, e-mail: 
 users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




Re: Configure 'finalName' pattern for all child modules

2011-10-12 Thread Manfred Moser

 Dont use relative path  ...

11-10-12 05:30 PM, Yuen-Chi Lian wrote:

Yes. Have you tried?

$ cat parent/pom.xml | grep finalName

finalName${project.artifactId}-${project.version}-b${buildNumber}/finalName

In the child:

 parent
 groupIdy/groupId
 artifactIdx/artifactId
 versionv/version
 relativePath../parent/relativePath

Yuen-Chi Lian | www.yclian.com
I do not seek; I find. - Pablo Picasso



2011/10/13 Stanimir Stamenkovs7a...@netscape.net


I want to configure the 'finalName' for a parent module and all its child
modules as:

build
finalName${artifactId}/**fileName
/build

Is there a way to configure this as a default pattern in the parent and
avoid repeating it in the 'build' section for all child modules?

--
Stanimir

--**--**-
To unsubscribe, e-mail: 
users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Configure 'finalName' pattern for all child modules

2011-10-12 Thread Stanimir Stamenkov

Thu, 13 Oct 2011 08:30:49 +0800, /Yuen-Chi Lian/:


Yes. Have you tried?

$ cat parent/pom.xml | grep finalName

finalName${project.artifactId}-${project.version}-b${buildNumber}/finalName


Ah, yes - thank you.  I've already tried it before but for some 
reason I had determined it doesn't work, but seems I've been wrong.


--
Stanimir

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org