Hi,
I have a module "module1" defined with version "1.2-SNAPSHOT" and
module3 has a dependency to module1.
<dependency>
<groupId>org.cd.test</groupId>
<artifactId>module1</artifactId>
<version>1.2-SNAPSHOT</version>
</dependency>
Module one inherits from a module "parent" which also has the version
"1.2-SNAPSHOT".
I deployed parent and module1 with mvn deploy and then deleted them
from my local repository
When I build module3, module1 will be downloaded, the file names (jar
and pom) will be renamed to include "1.2-SNAPSHOT", but the version in
the header of the pom will remain the timestamp. Now, if I had
dependencies in module1 with version defined as ${version} (with that
I would expect the version of module1 - 1.2-SNAPSHOT), they will not
be found (since version is a timestamp).
Is this the expected behaviour? What's the best way to define
dependencies to snapshot modules? Cause I defined them using the
"dependencyManagement" section as ${version} and then I ran into this
problem.
Thanks,
Ciprian
Off topic: Is there any document that describes the way maven handles
snapshots and the meta files/information?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
