Yann,
This is to be expected. When running maven in your B project, maven has no
knowledge of project A as a module to be built and referenced, only as a
dependency that needs to be retrieved from a repository and added to the
classpath.
In addition, finalName only effects the name of the artifact generated in
the target directory. If you install/deploy the same artifact it will
(should) have the standard naming of ${artifactId}-${version}. This is A
Good Thing, as it prevents ambiguity in the repository.
HTH,
Doug
On 10/12/06, Yann Albou <[EMAIL PROTECTED]> wrote:
Hi,
I try to use the finalName in my parent pom as following:
<finalName>${artifactId}</finalName> (without the version number)
If I run maven from the parent pom everything works fine: all my
artifacts are generated without the version number. and also the
classpath entry of the manifest.mf file is correctly set.
For instance I get :
parent
--- A module
--- B module (with a dependency on A)
So it generates B.jar with a Manifest containning "ClassPath: A.Jar"
Now If I run maven from B module it generates a B.jar but with a
manifest containing "ClassPath: A-1.2.1.Jar" for instance.
I get exactly the same behaviour with an EAR module that generate the
application.xml => module are not generated with the correct name...
If I run maven from the parent pom then the application.xml is generated
correctly
Did I miss something ?
Yann.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
