Doug,
thanks for your reply.
Yes that's true, Maven has no knowledge of projet A. But it knows that A
is a dependency. So it should include A as a reference in module B using
the finalName: is it completly non sens?
Moreover I found dangerous that the behavior is not the same when
building
In the last couple of months, this same discussion has come up once or
twice. I believe someone even suggested adding another node to
dependency to allow you to change the name of the artifact when it
was brought into your project/jar/war. There might even be a JIRA
already posted as an
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
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
