Yes, DUCC bundles activemq runtime used only by the broker. The
ducc_runtime/lib/activemq is for DUCC.
Seems redundant. Perhaps we can change our python scripts to point to
activemq/lib instead if ducc_runtime/lib/activemq.
As an option we can create JIRA and fix this in a future release of DUCC.
This doesnt not effect the user. Its just a packaging
bug.
Yes, there are some jars with a missing versions. Bug in the assembly
script. For some reason I added
<outputFileNameMapping>${artifact.artifactId}.jar</..>
This should be removed on a few dependencies in the assembly.
On Fri, Nov 22, 2013 at 10:43 AM, Marshall Schor <[email protected]> wrote:
> Some Jars from dependencies are packaged in the binary distribution
> multiple
> times. Some examples:
>
> The ducc_runtime has subdirectories:
> activemq/lib
> lib
> ...
>
> And the activemq/lib has versions of jars that also appear in the lib.
>
> An example:
>
> activemq/lib/xstream-1.3.1.jar
> lib/xstream.jar
>
> activemq/lib/spring-xxx (various)
> lib/springramework/spring-xxx (various)
>
> activemq/lib/aopalliance-1.0.jar
> lib/springframework/aopalliance-1.0.jar
>
> etc.
>
> Note, too, that sometimes the xxx-[version].jar convention is used, and
> sometimes, not
>
> -Marshall
>
