You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Charles Moulliard <ch...@gmail.com> on 2014/02/03 09:12:56 UTC
Re: MANIFEST generated commons-lang import
Hi Ronny,
Which version of open-ejb would you like to deploy ? You can tranform a non
OSGI jar file into a OSGI Bundle using the wrap instruction
install -s wrap:org.apache.commons/commons-lang3/3.1
Regards,
On Fri, Jan 31, 2014 at 8:58 PM, Ronny Bräunlich <r....@gmail.com>wrote:
> Hello everyone,
>
> I wanted to drop the openejb-core module into Karaf 3.
> When trying to start the bundle OSGi couldn't resolve the import
> org.apache.commons.lang;version="[3.1,4.0)".
> As far as I know there is no version >3 of that package because the name
> changed to org.apache.commons.lang3.
> Am I wrong or should someone correct the "openejb.osgi.import.pkg"
> property in the POM?
>
> Cheers,
> Ronny
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
Re: MANIFEST generated commons-lang import
Posted by Charles Moulliard <ch...@gmail.com>.
Mailing list is defind here : http://openejb.apache.org/mailing-lists.html
On Tue, Feb 4, 2014 at 8:13 PM, rbraeunlich <r....@gmail.com> wrote:
> Do the TomEE guys have a separate mailing list?
> I created a PR: https://github.com/apache/tomee/pull/3
> But I am not sure if they'll get it because it's a mirror.
>
>
> Am 04.02.2014 um 18:06 schrieb Charles Moulliard-2 [via OpenEJB] <
> ml-node+s979440n4667488h8@n4.nabble.com>:
>
> > I think that we should contact Apache TomEE project to report this issue
> > and provide a PR to change the import package of commons (
> >
> https://github.com/apache/tomee/blob/trunk/container/openejb-core/pom.xml)
> >
> >
> > On Tue, Feb 4, 2014 at 5:19 PM, rbraeunlich <[hidden email]> wrote:
> >
> > > 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] <
> > > [hidden email]>:
> > >
> > > > 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.
> > >
> >
> >
> >
> > --
> > 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-tp4667417p4667488.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-tp4667417p4667489.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
Re: MANIFEST generated commons-lang import
Posted by rbraeunlich <r....@gmail.com>.
Do the TomEE guys have a separate mailing list?
I created a PR: https://github.com/apache/tomee/pull/3
But I am not sure if they’ll get it because it’s a mirror.
Am 04.02.2014 um 18:06 schrieb Charles Moulliard-2 [via OpenEJB] <ml...@n4.nabble.com>:
> I think that we should contact Apache TomEE project to report this issue
> and provide a PR to change the import package of commons (
> https://github.com/apache/tomee/blob/trunk/container/openejb-core/pom.xml)
>
>
> On Tue, Feb 4, 2014 at 5:19 PM, rbraeunlich <[hidden email]> wrote:
>
> > 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] <
> > [hidden email]>:
> >
> > > 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.
> >
>
>
>
> --
> 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-tp4667417p4667488.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-tp4667417p4667489.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
Re: MANIFEST generated commons-lang import
Posted by Charles Moulliard <ch...@gmail.com>.
I think that we should contact Apache TomEE project to report this issue
and provide a PR to change the import package of commons (
https://github.com/apache/tomee/blob/trunk/container/openejb-core/pom.xml)
On Tue, Feb 4, 2014 at 5:19 PM, rbraeunlich <r....@gmail.com> wrote:
> 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] <
> ml-node+s979440n4667484h84@n4.nabble.com>:
>
> > 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.
>
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
Re: MANIFEST generated commons-lang import
Posted by rbraeunlich <r....@gmail.com>.
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] <ml...@n4.nabble.com>:
> 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.
Re: MANIFEST generated commons-lang import
Posted by Charles Moulliard <ch...@gmail.com>.
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 <r....@gmail.com> 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
Re: MANIFEST generated commons-lang import
Posted by rbraeunlich <r....@gmail.com>.
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.