Hi,
I have a problem using the maven-bundle-plugin with how the names of
SNAPSHOT dependencies are resolved.
For example, I have the following dependency in my pom:
<dependency>
<groupId>com.company</groupId>
<artifactId>my-lib</artifactId>
<version>1.0.0-SNAPSHOT</version>
</dependency>
Note that my com.company:my-lib is located in my internal (not my local)
maven repo.
When the maven-bundle-plugin runs it generates the manifest for the bundle
with the following class path entry:
Bundle-ClassPath: .,my-lib-1.0.0-20140523.082755-2.jar
I'm expecting to see
Bundle-ClassPath: .,my-lib-1.0.0-SNAPSHOT.jar
I guess this wouldn't ordinarily be a problem but I'm later using the
proguard-mave-plugin and the maven-assembly-plugin to optimise and assemble
my jar and these are using the SNAPSHOT name and not the timestamp name.
If I manually install the dependency into my local repo 'SNAPSHOT' is used
as expected. - it's only when the dependency is downloaded by maven from
the internal repo that the issue occurs.
An interesting side note is that when I open my project in Eclipse and get
m2e to build the project, the dependency version is changed to 'SNAPSHOT',
so it seems that Eclipse behaves as expected - it's only building on the
command line that causes the problem.
I'm tearing my hair out on this one so any tips would be greatly
appreciated.
Thanks,
Ben
