[
https://issues.apache.org/jira/browse/AXIS2-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884927#action_12884927
]
Dennis Sosnoski commented on AXIS2-3642:
----------------------------------------
Yes, this is being resolved for the JiBX 1.2.3 release by removing the
Class-Path entries from the jars distributed through Maven. I'll update both
Axis2 trunk and 1.5 branch to use 1.2.3 as soon as it's released (which should
be within the next 10 days).
> jibx libs coming in Axis2 distrib are renamed while still reffering in their
> manifests to old names
> ---------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3642
> URL: https://issues.apache.org/jira/browse/AXIS2-3642
> Project: Axis2
> Issue Type: Bug
> Components: databinding
> Affects Versions: 1.3
> Reporter: Michael B
> Assignee: Dennis Sosnoski
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Funny thing I found: i can not use jibx-bind-1.1.5.jar coming in full Axis2
> distrib to postprocess my compiled databinding DTOs.
> The cause is that jibx-bind-1.1.5.jar needs some classes from jibx-run.jar
> which is named in Axis2 distrib as jibx-run-1.1.5.jar. But unfortunately
> ibx-bind-1.1.5.jar still has its META-INF/MANIFEST.MF containing the line:
> Class-Path: bcel.jar jibx-run.jar xpp3.jar stax-api.jar wstx-asl.jar
> That is - reffering to jibx-run.jar, not jibx-run-1.1.5.jar which is present
> in the Axsis2 disctrib.
> Of cause this is not a major issue, but i think that it would be better to
> fix it either by renaming jars back (i.e. stripping version) or modifying
> their manifest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
