[
https://issues.apache.org/jira/browse/MSHARED-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Murashenkov updated MSHARED-659:
---------------------------------------
Description:
I'd like to reopen the issue MSHARED-396.
So the case is extremely simple:
1. Maven module creates executable jar adding classpath to manifest.
2. Then assembly plugin packs executable jar and it's dependencies into archive.
3. Then we unpack app and launch it with java -jar myexecutable.jar. All
dependencies are placed in same folder and referenced by manifest classpath.
Now suppose we had one library of version 1.0 in runtime scope and 1.5 in test
scope. Current behavior is that manifest classpath will have version 1.5 set,
but assembly plugin will pack 1.0 cause we only take runtime dependencies. And
this may result in ClassNotFoundException in production.
Perhaps it has something to do with MSHARED-4?
was:
I'd like to reopen the issue MSHARED-396.
So the case is extremely simple:
1. Maven module creates executable jar adding classpath to manifest.
2. Then assembly plugin packs executable jar and it's dependencies into archive/
3. Then we unpack app and launch it with java -jar myexecutable.jar. All
dependencies are places in same folder and referenced by manifest classpath.
Now suppose we had one library of version 1.0 in runtime scope and 1.5 in test
scope. Current behavior is that manifest classpath will have version 1.5 set,
but assembly plugin will pack 1.0 cause we only take runtime dependencies. And
this may result in ClassNotFoundException in production.
Perhaps it has something to do with MSHARED-4?
> CLONE - Created manifest contains versions of test scope
> --------------------------------------------------------
>
> Key: MSHARED-659
> URL: https://issues.apache.org/jira/browse/MSHARED-659
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Reporter: Dmitry Murashenkov
> Attachments: dependency-bug.zip
>
>
> I'd like to reopen the issue MSHARED-396.
> So the case is extremely simple:
> 1. Maven module creates executable jar adding classpath to manifest.
> 2. Then assembly plugin packs executable jar and it's dependencies into
> archive.
> 3. Then we unpack app and launch it with java -jar myexecutable.jar. All
> dependencies are placed in same folder and referenced by manifest classpath.
> Now suppose we had one library of version 1.0 in runtime scope and 1.5 in
> test scope. Current behavior is that manifest classpath will have version 1.5
> set, but assembly plugin will pack 1.0 cause we only take runtime
> dependencies. And this may result in ClassNotFoundException in production.
> Perhaps it has something to do with MSHARED-4?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
