[
https://issues.apache.org/activemq/browse/AMQ-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43847#action_43847
]
Hans Bausewein commented on AMQ-1828:
-------------------------------------
Add to "environment:" java version "1.5.0_14" ( build 1.5.0_14-b03 )
The problem is in the jaxb-impl-2.0.3.jar downloaded from the Maven
repository, so strictly speaking, it's not an ActiveMQ issue.
But it causes the "activemq-rar-5.1.0.rar" deployment to fail, when the
"jaxb-api-2.1.jar" is not available on the CLASSPATH in Java 1.5, so better
keep the issue for easy reference.
> Classpath in "jaxb-impl" META-INF/MANIFEST.MF does not match included library
> -----------------------------------------------------------------------------
>
> Key: AMQ-1828
> URL: https://issues.apache.org/activemq/browse/AMQ-1828
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0
> Environment: JBoss 4.0.5 GA
> Reporter: Hans Bausewein
> Attachments: jaxb-impl-MANIFEST.diff
>
>
> When I first deployed and used the resource adapter, it could not find it's
> "jaxb-api-2.1.jar".
> See the attached "jaxb-impl-MANIFEST.diff".
> The META-INF/MANIFEST.MF of jaxb-impl-2.0.3.jar lists the classpath as:
> Class-Path: jaxb-api.jar activation.jar jsr173_1.0_api.jar jaxb1-impl.
> jar
> ... but the file names is "jaxb-api-2.1.jar"
> Applying the patch to the META-INF/MANIFEST.MF in "jaxb-api-2.1.jar" and
> updating that jar in "activemq-rar-5.1.0.rar" resolves the problem.
> I could reproduce the failing jar with the 5.1.0 source, but I couldn't find
> out where in the build process it fails.
> Maybe it's the "jaxb-impl" pom in the maven repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
