There is no bug here. I was mistaken. I inadvertently neglected to
convert one of the MQ jars to system scope and so it still appeared in
the manifest. System scope jars are NOT included in the manifest which
is the correct behavior.
Sorry for the confusion.
On 07/28/2014 09:43 AM, Steve Cohen wrote:
Sadly, my hopes were not completely fulfilled.
In spite of specifying the MQ jars as system dependencies with their own
paths, the maven manifest generator ignored these paths. This means
that I must no longer run my application with java -jar, relying on the
classpath manifest, but must specify the classpath on the command line.
Doable, but annoying.
This is arguably a bug. If system dependencies are required to list
their path, should not the manifest classpath generator respect these?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
