I am sorry Charles but I still don’t get your point.
When I start Karaf and install commons-lang3 (bundle:install
mvn:org.apache.commons/commons-lang3/3.1) I can see that it exports these
headers:
Export-Package =
org.apache.commons.lang3.event;version=3.1,
org.apache.commons.lang3.mutable;version=3.1,
…
But the import in the OpenEJB core module needs this package:
org.apache.commons.lang;version="[3.1,4)“,
And this package doesn’t exist because the Commons-Lang guys changed the
package name.
Cheers,
Ronny
Am 04.02.2014 um 16:37 schrieb Charles Moulliard-2 [via OpenEJB]
<[email protected]>:
> MANIFEST file of commons lang 3 is correct so it can be deployed on karaf
> without option wrap:mvn but just mvn:
>
>
> On Mon, Feb 3, 2014 at 3:26 PM, rbraeunlich <[hidden email]> wrote:
>
> > Hi Charles,
> >
> > I tried with version 4.0.0 and 4.6.0.
> > Commons-Lang 3.* already has proper headers in its Manifest that why I
> > think
> > it's unnecessary to wrap it.
> > And I am not sure how the transformation works, but nevertheless it
> > shouldn't change the package names in the jar.
> >
> >
> >
> > --
> > View this message in context:
> > http://openejb.979440.n4.nabble.com/MANIFEST-generated-commons-lang-import-tp4667417p4667465.html
> > Sent from the OpenEJB User mailing list archive at Nabble.com.
> >
>
>
>
> --
> Charles Moulliard
> Apache Committer / Architect @RedHat
> Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
>
>
> If you reply to this email, your message will be added to the discussion
> below:
> http://openejb.979440.n4.nabble.com/MANIFEST-generated-commons-lang-import-tp4667417p4667484.html
> To unsubscribe from MANIFEST generated commons-lang import, click here.
> NAML
--
View this message in context:
http://openejb.979440.n4.nabble.com/MANIFEST-generated-commons-lang-import-tp4667417p4667487.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
