You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "John E. Conlon" <jc...@verticon.com> on 2006/11/04 04:31:46 UTC
Felix Commons Initiative Status
What is the latest status of the commons?
I'm willing to help start doing the spade work if this will help move it
forward.
regards,
John
Re: Re[2]: Felix Commons Initiative Status
Posted by Felix Meschberger <Fe...@day.com>.
Many thanks.
Regards
Felix
On 11/5/06, Peter Kriens <Pe...@aqute.biz> wrote:
> Sorry, my server was doing strange :-(
>
> I have deployed the jar again. It now looks better.
>
> Kind regards,
>
> Peter Kriens
>
> FM> Hi Peter and Richard,
>
> FM> The new plugin and the bnd tool are great, I just tried them an hour ago ....
>
> FM> There are only two issues: The bnd build 0.0.97 does not seem to be
> FM> complete in the repository (around 67KB compared to 115KB for build
> FM> 0.0.96, and maven complains about a corrupt JAR file) and the bundle
> FM> plugin cannot currently cope with non-existing src directory (will
> FM> post a JIRA issue with proposed patches for this).
>
> FM> Anyway, the new plugin/bnd combination is a great plus compared to the
> FM> already useful osgi plugin.
>
> FM> Thanks and Regards
> FM> Felix
>
> FM> On 11/4/06, Peter Kriens <Pe...@aqute.biz> wrote:
> >> Maybe you could take a look at the bnd program. Converting JARs to
> >> bundle is quite easy with the wrap command. Additional changes to the
> >> manifest could be made by building the JAR with a specific bnd file
> >> that contains the specifics.
> >>
> >> Let me know if I can help ...
> >>
> >> Kind regards,
> >>
> >> Peter Kriens
> >>
> >>
> >> JEC> What is the latest status of the commons?
> >>
> >> JEC> I'm willing to help start doing the spade work if this will help move it
> >> JEC> forward.
> >>
> >> JEC> regards,
> >> JEC> John
> >>
> >>
> >> --
> >> Peter Kriens Tel +33467542167
> >> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens
> >> 34160 Beaulieu, France ICQ 255570717
> >> Skype pkriens Fax +1 8153772599
> >>
> >>
>
>
> --
> Peter Kriens Tel +33467542167
> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens
> 34160 Beaulieu, France ICQ 255570717
> Skype pkriens Fax +1 8153772599
>
>
Re[2]: Felix Commons Initiative Status
Posted by Peter Kriens <Pe...@aQute.biz>.
Sorry, my server was doing strange :-(
I have deployed the jar again. It now looks better.
Kind regards,
Peter Kriens
FM> Hi Peter and Richard,
FM> The new plugin and the bnd tool are great, I just tried them an hour ago ....
FM> There are only two issues: The bnd build 0.0.97 does not seem to be
FM> complete in the repository (around 67KB compared to 115KB for build
FM> 0.0.96, and maven complains about a corrupt JAR file) and the bundle
FM> plugin cannot currently cope with non-existing src directory (will
FM> post a JIRA issue with proposed patches for this).
FM> Anyway, the new plugin/bnd combination is a great plus compared to the
FM> already useful osgi plugin.
FM> Thanks and Regards
FM> Felix
FM> On 11/4/06, Peter Kriens <Pe...@aqute.biz> wrote:
>> Maybe you could take a look at the bnd program. Converting JARs to
>> bundle is quite easy with the wrap command. Additional changes to the
>> manifest could be made by building the JAR with a specific bnd file
>> that contains the specifics.
>>
>> Let me know if I can help ...
>>
>> Kind regards,
>>
>> Peter Kriens
>>
>>
>> JEC> What is the latest status of the commons?
>>
>> JEC> I'm willing to help start doing the spade work if this will help move it
>> JEC> forward.
>>
>> JEC> regards,
>> JEC> John
>>
>>
>> --
>> Peter Kriens Tel +33467542167
>> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens
>> 34160 Beaulieu, France ICQ 255570717
>> Skype pkriens Fax +1 8153772599
>>
>>
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
Re: Felix Commons Initiative Status
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Ivo,
It depends on whether you want to use it as a maven plugin or
directly...for a maven plugin, read this:
http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html
If you want to use it directly, read this:
http://www.aqute.biz/Code/Bnd
-> richard
Ivo K. Koga wrote:
> Hi Felix,
>
> Could you help me getting started using this bnd tool?
>
> Regards,
>
> Ivo Koga
>
> On 11/4/06, Felix Meschberger <Fe...@day.com> wrote:
>>
>> Hi Peter and Richard,
>>
>> The new plugin and the bnd tool are great, I just tried them an hour ago
>> ....
>>
>> There are only two issues: The bnd build 0.0.97 does not seem to be
>> complete in the repository (around 67KB compared to 115KB for build
>> 0.0.96, and maven complains about a corrupt JAR file) and the bundle
>> plugin cannot currently cope with non-existing src directory (will
>> post a JIRA issue with proposed patches for this).
>>
>> Anyway, the new plugin/bnd combination is a great plus compared to the
>> already useful osgi plugin.
>>
>> Thanks and Regards
>> Felix
>>
>> On 11/4/06, Peter Kriens <Pe...@aqute.biz> wrote:
>> > Maybe you could take a look at the bnd program. Converting JARs to
>> > bundle is quite easy with the wrap command. Additional changes to the
>> > manifest could be made by building the JAR with a specific bnd file
>> > that contains the specifics.
>> >
>> > Let me know if I can help ...
>> >
>> > Kind regards,
>> >
>> > Peter Kriens
>> >
>> >
>> > JEC> What is the latest status of the commons?
>> >
>> > JEC> I'm willing to help start doing the spade work if this will help
>> move it
>> > JEC> forward.
>> >
>> > JEC> regards,
>> > JEC> John
>> >
>> >
>> > --
>> > Peter Kriens Tel +33467542167
>> > 9C, Avenue St. Drézéry AOL,Yahoo: pkriens
>> > 34160 Beaulieu, France ICQ 255570717
>> > Skype pkriens Fax +1 8153772599
>> >
>> >
>>
>
Re: Felix Commons Initiative Status
Posted by "Ivo K. Koga" <iv...@gmail.com>.
Hi Felix,
Could you help me getting started using this bnd tool?
Regards,
Ivo Koga
On 11/4/06, Felix Meschberger <Fe...@day.com> wrote:
>
> Hi Peter and Richard,
>
> The new plugin and the bnd tool are great, I just tried them an hour ago
> ....
>
> There are only two issues: The bnd build 0.0.97 does not seem to be
> complete in the repository (around 67KB compared to 115KB for build
> 0.0.96, and maven complains about a corrupt JAR file) and the bundle
> plugin cannot currently cope with non-existing src directory (will
> post a JIRA issue with proposed patches for this).
>
> Anyway, the new plugin/bnd combination is a great plus compared to the
> already useful osgi plugin.
>
> Thanks and Regards
> Felix
>
> On 11/4/06, Peter Kriens <Pe...@aqute.biz> wrote:
> > Maybe you could take a look at the bnd program. Converting JARs to
> > bundle is quite easy with the wrap command. Additional changes to the
> > manifest could be made by building the JAR with a specific bnd file
> > that contains the specifics.
> >
> > Let me know if I can help ...
> >
> > Kind regards,
> >
> > Peter Kriens
> >
> >
> > JEC> What is the latest status of the commons?
> >
> > JEC> I'm willing to help start doing the spade work if this will help
> move it
> > JEC> forward.
> >
> > JEC> regards,
> > JEC> John
> >
> >
> > --
> > Peter Kriens Tel +33467542167
> > 9C, Avenue St. Drézéry AOL,Yahoo: pkriens
> > 34160 Beaulieu, France ICQ 255570717
> > Skype pkriens Fax +1 8153772599
> >
> >
>
Re: Felix Commons Initiative Status
Posted by Felix Meschberger <Fe...@day.com>.
Hi Peter and Richard,
The new plugin and the bnd tool are great, I just tried them an hour ago ....
There are only two issues: The bnd build 0.0.97 does not seem to be
complete in the repository (around 67KB compared to 115KB for build
0.0.96, and maven complains about a corrupt JAR file) and the bundle
plugin cannot currently cope with non-existing src directory (will
post a JIRA issue with proposed patches for this).
Anyway, the new plugin/bnd combination is a great plus compared to the
already useful osgi plugin.
Thanks and Regards
Felix
On 11/4/06, Peter Kriens <Pe...@aqute.biz> wrote:
> Maybe you could take a look at the bnd program. Converting JARs to
> bundle is quite easy with the wrap command. Additional changes to the
> manifest could be made by building the JAR with a specific bnd file
> that contains the specifics.
>
> Let me know if I can help ...
>
> Kind regards,
>
> Peter Kriens
>
>
> JEC> What is the latest status of the commons?
>
> JEC> I'm willing to help start doing the spade work if this will help move it
> JEC> forward.
>
> JEC> regards,
> JEC> John
>
>
> --
> Peter Kriens Tel +33467542167
> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens
> 34160 Beaulieu, France ICQ 255570717
> Skype pkriens Fax +1 8153772599
>
>
Re: Felix Commons Initiative Status
Posted by Peter Kriens <Pe...@aQute.biz>.
Maybe you could take a look at the bnd program. Converting JARs to
bundle is quite easy with the wrap command. Additional changes to the
manifest could be made by building the JAR with a specific bnd file
that contains the specifics.
Let me know if I can help ...
Kind regards,
Peter Kriens
JEC> What is the latest status of the commons?
JEC> I'm willing to help start doing the spade work if this will help move it
JEC> forward.
JEC> regards,
JEC> John
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
Re: Felix Commons Initiative Status
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Tim Moloney wrote:
> I'm willing to do commons-logging. I haven't used bnd yet but I will
> take a look at the docs and try to use it to generate the
> commons-logging pom. In the meantime, I posted a pom for
> commons-logging here [1] but I generated this one by hand.
>
> I have a few suggestions.
> - Add a link from the "Apache Felix" homepage [2] to the "Apache Felix
> Commons" page [3]
I will leave this to Marcel to figure out how he wants to handle it. :-)
> - In JIRA, create a "Felix Commons" component
I did this yesterday...it isn't visibly unless someone adds an issue to it.
> - Add a link from the "Apache Felix Commons" page [3] to the new
> "Felix Commons" component in JIRA
Yes, that makes sense...I will do that. Although I don't see an
meaningful way to link to the "Felix Commons" component, so I will just
link to Felix in JIRA.
> Short-term, I think these would make it easy to see what bundles
> exist, which bundles people want, and which of these are being
> worked. Long-term, I think these would improve the visibility of the
> Felix Commons initiative and increase contributions.
Agreed.
-> richard
>
> [1]
> http://www.mail-archive.com/felix-dev@incubator.apache.org/msg02706.html
> [2] http://cwiki.apache.org/FELIX/index.html
> [3] http://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+Commons
>
> Tim Moloney
>
>
> Richard S. Hall wrote:
>> Felix,
>>
>> I think it would be great if you could offer these...perhaps Enrique
>> can help us out with describing how he envisions this taking place.
>>
>> For the time being, I can list your potential contributions on the
>> wiki page.
>>
>> -> richard
>>
>> Felix Meschberger wrote:
>>> Hi,
>>>
>>>> If you have libraries you have turned into bundles, then you can offer
>>>> to contribute them.
>>>>
>>>> I was thinking lately that we could actually define a common
>>>> process/approach for bundling third-party libs and define a POM file
>>>> template for our new maven plugin for doing so. Then the whole process
>>>> potentially becomes really simple. Felix Commons could become a large
>>>> "project" of POMs where each simply has a dependency on the library it
>>>> wants to convert, which will then convert it automatically with the
>>>> plugin when built...then we just need to make the resulting JARs
>>>> publicly available (perhaps through OBR and Maven) and we are done.
>>>
>>> Great thing ! In fact, I could already share some of them: BeanUtils,
>>> Codec, Collections, Configuration, Digester, EL, FileUpload,
>>> HTTPClient, IO, Lang plus CGLib.
>>>
>>> They are currently based on the older OSGi plugin, but of course I
>>> would migrate them to the new plugin, which is on my plate anyway.
>>>
>>> Here is for example, what I did for Commons Lang (old plugin):
>>>
>
Re: Felix Commons Initiative Status
Posted by Tim Moloney <t....@verizon.net>.
Oops, I forget to mention that Include-Resource is a bnd configuration
tag in the maven-bundle-plugin.
Tim Moloney wrote:
> Peter Kriens wrote:
>> TM> I'll keep pushing forward but I wanted to share this in case
>> TM> a) I'm doing something wrong, or
>> TM> b) things need to get fixed.
>> You seem do be doing all right :-) I have just fixed the NPE, sorry.
>> Never crossed my mind there could be no manifest ... Should be online
>> tomorrow.
>>
>> [...]
>
> Thanks.
>
> I have a new question. Can I use Include-Resource to copy a file
> directly from the library jar to the bundle or is that not possible?
>
> Here's a specific example. I want to copy META-INF/LICENSE.txt,
> META-INF/mailcap.default, and META-INF/mimetypes.default from
> activation-1.1.jar into the generated bundle jar. Can I use
> Include-Resource to copy it directly or do I have to unzip
> activation-1.1.jar first? If I have to unzip first, how do I do that
> in Maven? (Sorry for the newbie Maven question.)
>
> Tim
>
>
Commons Initiative Status: more dynamic behaviour?
Posted by Toni Menzel <to...@gmx.de>.
I am somthing confused about the recent activity for converting bundles
for common libraries like apache-commons and (for example that one I
thought to contribute the bundle for) junit.
But typing "junit" into the OBR Search gets more bundles (with very
different version numbering)
than we might need. (is there any real difference between the
knoplerfish,equinox or felix bundles? It shouldn't if I understand osgi
R4 correcly)
The only difference is, we need a pom, to get that working with maven.
But is (as Peter Kriens noticed in this newsgroup recently) that really
what we want to do manually?
How about fetching the bundles and (more important) the manifest and
generate the pom on-demand if needed. (so we would have a third version
of the maven-bundle plugin;-)
Does the OBR have some kind of webservice API to access it?
Toni
Tim Moloney schrieb:
> Peter Kriens wrote:
>> TM> I'll keep pushing forward but I wanted to share this in case
>> TM> a) I'm doing something wrong, or
>> TM> b) things need to get fixed.
>> You seem do be doing all right :-) I have just fixed the NPE, sorry.
>> Never crossed my mind there could be no manifest ... Should be online
>> tomorrow.
>>
>> [...]
>
> Thanks.
>
> I have a new question. Can I use Include-Resource to copy a file
> directly from the library jar to the bundle or is that not possible?
>
> Here's a specific example. I want to copy META-INF/LICENSE.txt,
> META-INF/mailcap.default, and META-INF/mimetypes.default from
> activation-1.1.jar into the generated bundle jar. Can I use
> Include-Resource to copy it directly or do I have to unzip
> activation-1.1.jar first? If I have to unzip first, how do I do that
> in Maven? (Sorry for the newbie Maven question.)
>
> Tim
--
Toni Menzel
http://www.tonit.com
mailto:tonimenzel@gmx.de
Re: Felix Commons Initiative Status
Posted by Tim Moloney <t....@verizon.net>.
Peter Kriens wrote:
> TM> I'll keep pushing forward but I wanted to share this in case
> TM> a) I'm doing something wrong, or
> TM> b) things need to get fixed.
> You seem do be doing all right :-) I have just fixed the NPE, sorry.
> Never crossed my mind there could be no manifest ... Should be online
> tomorrow.
>
> [...]
Thanks.
I have a new question. Can I use Include-Resource to copy a file
directly from the library jar to the bundle or is that not possible?
Here's a specific example. I want to copy META-INF/LICENSE.txt,
META-INF/mailcap.default, and META-INF/mimetypes.default from
activation-1.1.jar into the generated bundle jar. Can I use
Include-Resource to copy it directly or do I have to unzip
activation-1.1.jar first? If I have to unzip first, how do I do that in
Maven? (Sorry for the newbie Maven question.)
Tim
Re[2]: Felix Commons Initiative Status
Posted by Peter Kriens <Pe...@aQute.biz>.
TM> I'll keep pushing forward but I wanted to share this in case
TM> a) I'm doing something wrong, or
TM> b) things need to get fixed.
You seem do be doing all right :-) I have just fixed the NPE, sorry.
Never crossed my mind there could be no manifest ... Should be online
tomorrow.
The second horrible stack trace is not much I can do about. I report
the error via the log but there is only one way to report failure from
the plugin and that is an execption. I think Maven should not print a
stack trace in this case.
The version was wrong because OSGi has the major.minor.micro.qualifier
format.
Kind regards,
Peter Kriens
TM> Tim Moloney wrote:
>> I'm willing to do commons-logging. I haven't used bnd yet but I will
>> take a look at the docs and try to use it to generate the
>> commons-logging pom. In the meantime, I posted a pom for
>> commons-logging here [1] but I generated this one by hand.
TM> I'm using bnd to bundle all the dependencies of commons-logging. I have
TM> worked my way to jta-1.0.1B.jar which caused problems.
TM> bnd gives a NPE as follows:
TM> java -jar bnd-0.0.jar print
TM> ~/.m2/repository/javax/transaction/jta/1.0.1B/jta-1.0.1B.jar
TM> Software error occurred java.lang.NullPointerException
TM> java.lang.NullPointerException
TM> at aQute.lib.osgi.Verifier.<init>(Verifier.java:68)
TM> at aQute.bnd.main.bnd.doPrint(bnd.java:456)
TM> at aQute.bnd.main.bnd.doPrint(bnd.java:442)
TM> at aQute.bnd.main.bnd.run(bnd.java:56)
TM> at aQute.bnd.main.bnd.main(bnd.java:30)
TM> While bnd shouldn't die like that, closer inspection of jta-1.0.1B.jar
TM> shows that it's not really a jar file. It's just a zip file, no
TM> MANIFEST.MF file. I created a jar file so bnd won't NPE but now I get
TM> mvn install
TM> [...]
TM> [ERROR] Invalid value for Bundle-Version, 1.0.1B does not match
TM> [0-9]+(\.[0-9]+(\.[0-9]+(\.[0-9A-Za-z_-]+)?)?)?
TM> org.apache.maven.plugin.MojoFailureException: Found errors, see log
TM> at
TM> org.apache.felix.tools.maven2.bundleplugin.BundlePlugin.execute(BundlePlugin.java:150)
TM> at
TM> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
TM> at
TM> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
TM> at
TM> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
TM> at
TM> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
TM> at
TM> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
TM> at
TM> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
TM> at
TM> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
TM> at
TM> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
TM> at
TM> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
TM> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
TM> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
TM> at
TM> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
TM> at
TM> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
TM> at java.lang.reflect.Method.invoke(Method.java:585)
TM> at
TM> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
TM> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
TM> at
TM> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
TM> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
TM> [...]
TM> So I changed the version number to "1.0.1.B" everywhere so it matched
TM> the RE. I can now create a jta bundle.
TM> I'll keep pushing forward but I wanted to share this in case
TM> a) I'm doing something wrong, or
TM> b) things need to get fixed.
TM> Tim Moloney
--
Peter Kriens Tel +33467542167
9C, Avenue St. Drézéry AOL,Yahoo: pkriens
34160 Beaulieu, France ICQ 255570717
Skype pkriens Fax +1 8153772599
Re: Felix Commons Initiative Status
Posted by Tim Moloney <t....@verizon.net>.
Tim Moloney wrote:
> I'm willing to do commons-logging. I haven't used bnd yet but I will
> take a look at the docs and try to use it to generate the
> commons-logging pom. In the meantime, I posted a pom for
> commons-logging here [1] but I generated this one by hand.
I'm using bnd to bundle all the dependencies of commons-logging. I have
worked my way to jta-1.0.1B.jar which caused problems.
bnd gives a NPE as follows:
java -jar bnd-0.0.jar print
~/.m2/repository/javax/transaction/jta/1.0.1B/jta-1.0.1B.jar
Software error occurred java.lang.NullPointerException
java.lang.NullPointerException
at aQute.lib.osgi.Verifier.<init>(Verifier.java:68)
at aQute.bnd.main.bnd.doPrint(bnd.java:456)
at aQute.bnd.main.bnd.doPrint(bnd.java:442)
at aQute.bnd.main.bnd.run(bnd.java:56)
at aQute.bnd.main.bnd.main(bnd.java:30)
While bnd shouldn't die like that, closer inspection of jta-1.0.1B.jar
shows that it's not really a jar file. It's just a zip file, no
MANIFEST.MF file. I created a jar file so bnd won't NPE but now I get
mvn install
[...]
[ERROR] Invalid value for Bundle-Version, 1.0.1B does not match
[0-9]+(\.[0-9]+(\.[0-9]+(\.[0-9A-Za-z_-]+)?)?)?
org.apache.maven.plugin.MojoFailureException: Found errors, see log
at
org.apache.felix.tools.maven2.bundleplugin.BundlePlugin.execute(BundlePlugin.java:150)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[...]
So I changed the version number to "1.0.1.B" everywhere so it matched
the RE. I can now create a jta bundle.
I'll keep pushing forward but I wanted to share this in case
a) I'm doing something wrong, or
b) things need to get fixed.
Tim Moloney
Re: Felix Commons Initiative Status
Posted by Tim Moloney <t....@verizon.net>.
I'm willing to do commons-logging. I haven't used bnd yet but I will
take a look at the docs and try to use it to generate the
commons-logging pom. In the meantime, I posted a pom for
commons-logging here [1] but I generated this one by hand.
I have a few suggestions.
- Add a link from the "Apache Felix" homepage [2] to the "Apache Felix
Commons" page [3]
- In JIRA, create a "Felix Commons" component
- Add a link from the "Apache Felix Commons" page [3] to the new "Felix
Commons" component in JIRA
Short-term, I think these would make it easy to see what bundles exist,
which bundles people want, and which of these are being worked.
Long-term, I think these would improve the visibility of the Felix
Commons initiative and increase contributions.
[1] http://www.mail-archive.com/felix-dev@incubator.apache.org/msg02706.html
[2] http://cwiki.apache.org/FELIX/index.html
[3] http://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+Commons
Tim Moloney
Richard S. Hall wrote:
> Felix,
>
> I think it would be great if you could offer these...perhaps Enrique
> can help us out with describing how he envisions this taking place.
>
> For the time being, I can list your potential contributions on the
> wiki page.
>
> -> richard
>
> Felix Meschberger wrote:
>> Hi,
>>
>>> If you have libraries you have turned into bundles, then you can offer
>>> to contribute them.
>>>
>>> I was thinking lately that we could actually define a common
>>> process/approach for bundling third-party libs and define a POM file
>>> template for our new maven plugin for doing so. Then the whole process
>>> potentially becomes really simple. Felix Commons could become a large
>>> "project" of POMs where each simply has a dependency on the library it
>>> wants to convert, which will then convert it automatically with the
>>> plugin when built...then we just need to make the resulting JARs
>>> publicly available (perhaps through OBR and Maven) and we are done.
>>
>> Great thing ! In fact, I could already share some of them: BeanUtils,
>> Codec, Collections, Configuration, Digester, EL, FileUpload,
>> HTTPClient, IO, Lang plus CGLib.
>>
>> They are currently based on the older OSGi plugin, but of course I
>> would migrate them to the new plugin, which is on my plate anyway.
>>
>> Here is for example, what I did for Commons Lang (old plugin):
>>
Re: Felix Commons Initiative Status
Posted by Felix Meschberger <Fe...@day.com>.
Hi Richard,
> I think it would be great if you could offer these...perhaps Enrique can
> help us out with describing how he envisions this taking place.
>
> For the time being, I can list your potential contributions on the wiki
> page.
Ok. So I will create JIRA issues and just attach the poms there...
Regards
Felix
Re: Felix Commons Initiative Status
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Felix,
I think it would be great if you could offer these...perhaps Enrique can
help us out with describing how he envisions this taking place.
For the time being, I can list your potential contributions on the wiki
page.
-> richard
Felix Meschberger wrote:
> Hi,
>
>> If you have libraries you have turned into bundles, then you can offer
>> to contribute them.
>>
>> I was thinking lately that we could actually define a common
>> process/approach for bundling third-party libs and define a POM file
>> template for our new maven plugin for doing so. Then the whole process
>> potentially becomes really simple. Felix Commons could become a large
>> "project" of POMs where each simply has a dependency on the library it
>> wants to convert, which will then convert it automatically with the
>> plugin when built...then we just need to make the resulting JARs
>> publicly available (perhaps through OBR and Maven) and we are done.
>
> Great thing ! In fact, I could already share some of them: BeanUtils,
> Codec, Collections, Configuration, Digester, EL, FileUpload,
> HTTPClient, IO, Lang plus CGLib.
>
> They are currently based on the older OSGi plugin, but of course I
> would migrate them to the new plugin, which is on my plate anyway.
>
> Here is for example, what I did for Commons Lang (old plugin):
>
> ------8<------
> <project>
> <modelVersion>4.0.0</modelVersion>
> <parent>
> <groupId>org.apache.felix.commons</groupId>
> <artifactId>felix-commons</artifactId>
> <version>1</version>
> </parent>
>
> <artifactId>commons-lang-osgi</artifactId>
> <version>2.0</version>
> <packaging>osgi-bundle</packaging>
>
> <name>Commons Lang packaged as an OSGi Bundle</name>
> <description>OSGi Bundle of Commons Lang</description>
>
> <dependencies>
> <dependency>
> <groupId>commons-lang</groupId>
> <artifactId>commons-lang</artifactId>
> <version>${version}</version>
> </dependency>
> </dependencies>
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.felix.plugins</groupId>
> <artifactId>maven-osgi-plugin</artifactId>
> <version>0.8.0-SNAPSHOT</version>
> <extensions>true</extensions>
> <configuration>
> <inlinedArtifacts>
> <inlinedArtifact>
> commons-lang
> </inlinedArtifact>
> </inlinedArtifacts>
> <osgiManifest>
> <bundleManifestVersion>2</bundleManifestVersion>
> <bundleName>${name}</bundleName>
> <bundleDescription>
> ${description}
> </bundleDescription>
> <bundleSymbolicName>
> ${groupId}.${artifactId}
> </bundleSymbolicName>
> <exportPackage>
> org.apache.commons.lang;
> org.apache.commons.lang.builder;
> org.apache.commons.lang.enum;
> org.apache.commons.lang.exception;
> org.apache.commons.lang.math;
> org.apache.commons.lang.time;
> version="${version}"
> </exportPackage>
> </osgiManifest>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
> ------8<------
>
> Regards
> Felix
Re: Felix Commons Initiative Status
Posted by Felix Meschberger <Fe...@day.com>.
Hi,
> If you have libraries you have turned into bundles, then you can offer
> to contribute them.
>
> I was thinking lately that we could actually define a common
> process/approach for bundling third-party libs and define a POM file
> template for our new maven plugin for doing so. Then the whole process
> potentially becomes really simple. Felix Commons could become a large
> "project" of POMs where each simply has a dependency on the library it
> wants to convert, which will then convert it automatically with the
> plugin when built...then we just need to make the resulting JARs
> publicly available (perhaps through OBR and Maven) and we are done.
Great thing ! In fact, I could already share some of them: BeanUtils,
Codec, Collections, Configuration, Digester, EL, FileUpload,
HTTPClient, IO, Lang plus CGLib.
They are currently based on the older OSGi plugin, but of course I
would migrate them to the new plugin, which is on my plate anyway.
Here is for example, what I did for Commons Lang (old plugin):
------8<------
<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.felix.commons</groupId>
<artifactId>felix-commons</artifactId>
<version>1</version>
</parent>
<artifactId>commons-lang-osgi</artifactId>
<version>2.0</version>
<packaging>osgi-bundle</packaging>
<name>Commons Lang packaged as an OSGi Bundle</name>
<description>OSGi Bundle of Commons Lang</description>
<dependencies>
<dependency>
<groupId>commons-lang</groupId>
<artifactId>commons-lang</artifactId>
<version>${version}</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.felix.plugins</groupId>
<artifactId>maven-osgi-plugin</artifactId>
<version>0.8.0-SNAPSHOT</version>
<extensions>true</extensions>
<configuration>
<inlinedArtifacts>
<inlinedArtifact>
commons-lang
</inlinedArtifact>
</inlinedArtifacts>
<osgiManifest>
<bundleManifestVersion>2</bundleManifestVersion>
<bundleName>${name}</bundleName>
<bundleDescription>
${description}
</bundleDescription>
<bundleSymbolicName>
${groupId}.${artifactId}
</bundleSymbolicName>
<exportPackage>
org.apache.commons.lang;
org.apache.commons.lang.builder;
org.apache.commons.lang.enum;
org.apache.commons.lang.exception;
org.apache.commons.lang.math;
org.apache.commons.lang.time;
version="${version}"
</exportPackage>
</osgiManifest>
</configuration>
</plugin>
</plugins>
</build>
</project>
------8<------
Regards
Felix
Re: Felix Commons Initiative Status
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Felix Meschberger wrote:
> To control the deployment of the bundles we use in-house, I hacked
> together a bundle which implements a very simple OBR server allowing
> to upload bundles and build the repository.xml file dynamically from
> the list of uploaded bundles.
>
> Here is the feature list:
> * Implemented with a Servlet frontend
> * Upload with POST
> * Generates repository.xml on-demand from the installed bundles
> * Automatic version-timestamp generation if the qualifier part of
> the bundle version contains the word "SNAPSHOT"
> * Simple GUI to see the list of available bundles as well as the
> details of them
>
> To enable the automatic upload to above repository, I hacked together
> a simple maven-plugin which just inspects the generated artifact to
> see whether it is a bundle and uploads to a configurable location.
>
> Could this help in any way ? - Or do such things already exist ?
Sounds very interesting to me. I don't have anything like this. Peter
Kriens offered a tool to generate the repository.xml file from a set of
bundle JAR files, but it sounds like your stuff goes further with
respect to uploading stuff to the repo server.
This sounds like you need a server entity running, right? If so, I am
not sure if we have the facilities for that at Apache or not.
For starters, it seems that we just need to generate a repository.xml
for all Commons bundles and then just copy the file and the bundle JAR
files to some web-accessible directory some place, then we are pretty
much done. This is essentially how Peter's tools works.
I am hoping that Enrique chimes in here soon on his thoughts... :-)
-> richard
Re: Felix Commons Initiative Status
Posted by Felix Meschberger <Fe...@day.com>.
Hi,
> Seems reasonable to me...although I am just winging
> it here. I am still not exactly sure how we are going to do this or
> where these generated bundles are going to live, etc. It would be nice
> if we could automatically publish them to an OBR repository some
> place...something to work on for the future, I guess. :-)
To control the deployment of the bundles we use in-house, I hacked
together a bundle which implements a very simple OBR server allowing
to upload bundles and build the repository.xml file dynamically from
the list of uploaded bundles.
Here is the feature list:
* Implemented with a Servlet frontend
* Upload with POST
* Generates repository.xml on-demand from the installed bundles
* Automatic version-timestamp generation if the qualifier part of
the bundle version contains the word "SNAPSHOT"
* Simple GUI to see the list of available bundles as well as the
details of them
To enable the automatic upload to above repository, I hacked together
a simple maven-plugin which just inspects the generated artifact to
see whether it is a bundle and uploads to a configurable location.
Could this help in any way ? - Or do such things already exist ?
Regards
Felix
Re: Felix Commons Initiative Status
Posted by "Richard S. Hall" <he...@ungoverned.org>.
John E. Conlon wrote:
> On Sat, 2006-11-04 at 07:28 -0500, Richard S. Hall wrote:
>
>> If you have some specific libraries you with to volunteer to bundle-
>> ize,
>> I can add your name and the libraries to the wiki page for now until
>> we
>> decide what our process will be.
>>
>
> Would like to bundleize the following three:
>
> <groupId>antlr</groupId>
> <artifactId>antlr</artifactId>
> <version>2.7.6</version>
>
> <groupId>commons-collections</groupId>
> <artifactId>commons-collections</artifactId>
> <version>3.1</version>
>
> <groupId>commons-lang</groupId>
> <artifactId>commons-lang</artifactId>
> <version>2.0</version>
>
I added these to the Felix Commons wiki page...there is some overlap
with what Felix said he would potentially provide, but we can work that
out...that is the whole point of this initiative. :-)
> Since bundleizing is just a pom.xml, how shall I furnish you with the
> pom.xml files? Maybe you could open Jira issues and I (or other
> contributors) can simply attach the pom.xmls for your or Enrique's
> review?
>
Good question. Slight variation, perhaps, I created a "Felix Commons"
JIRA component, so you can create an issue for any POM that you have and
attach it to that. Seems reasonable to me...although I am just winging
it here. I am still not exactly sure how we are going to do this or
where these generated bundles are going to live, etc. It would be nice
if we could automatically publish them to an OBR repository some
place...something to work on for the future, I guess. :-)
-> richard
>
>> I was thinking lately that we could actually define a common
>> process/approach for bundling third-party libs and define a POM file
>> template for our new maven plugin for doing so. Then the whole process
>> potentially becomes really simple. Felix Commons could become a large
>> "project" of POMs where each simply has a dependency on the library it
>> wants to convert, which will then convert it automatically with the
>> plugin when built...then we just need to make the resulting JARs
>> publicly available (perhaps through OBR and Maven) and we are done.
>>
> This is pretty much the approach I was thinking. Just a bunch of poms
> that are built and deploy their bundles to Maven.
>
>
> thanks,
> John
>
>
>
Re: Felix Commons Initiative Status
Posted by "John E. Conlon" <jc...@verticon.com>.
On Sat, 2006-11-04 at 07:28 -0500, Richard S. Hall wrote:
> If you have some specific libraries you with to volunteer to bundle-
> ize,
> I can add your name and the libraries to the wiki page for now until
> we
> decide what our process will be.
Would like to bundleize the following three:
<groupId>antlr</groupId>
<artifactId>antlr</artifactId>
<version>2.7.6</version>
<groupId>commons-collections</groupId>
<artifactId>commons-collections</artifactId>
<version>3.1</version>
<groupId>commons-lang</groupId>
<artifactId>commons-lang</artifactId>
<version>2.0</version>
Since bundleizing is just a pom.xml, how shall I furnish you with the
pom.xml files? Maybe you could open Jira issues and I (or other
contributors) can simply attach the pom.xmls for your or Enrique's
review?
> I was thinking lately that we could actually define a common
> process/approach for bundling third-party libs and define a POM file
> template for our new maven plugin for doing so. Then the whole process
> potentially becomes really simple. Felix Commons could become a large
> "project" of POMs where each simply has a dependency on the library it
> wants to convert, which will then convert it automatically with the
> plugin when built...then we just need to make the resulting JARs
> publicly available (perhaps through OBR and Maven) and we are done.
This is pretty much the approach I was thinking. Just a bunch of poms
that are built and deploy their bundles to Maven.
thanks,
John
Re: Felix Commons Initiative Status
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Ivo K. Koga wrote:
> Hi Richard,
>
> I don´t know If I understood, but is this an effort to put some of public
> knowledge open sources libraries in bundles to be accessable by people
> who
> wants to use it?
The basic idea is to create a community effort around taking third-party
open source libraries and making bundles out of them. In general, we all
end up creating bundles out of various common libraries, so rather than
us each duplicating the effort, we can do it as a community and share
these bundle-ized third-party libraries.
> If it´s the case, I don´t know exactly how I can contribute, but I
> think it
> will be a very interesting task. Hope I could be helpful in anything.
If you have libraries you have turned into bundles, then you can offer
to contribute them.
I was thinking lately that we could actually define a common
process/approach for bundling third-party libs and define a POM file
template for our new maven plugin for doing so. Then the whole process
potentially becomes really simple. Felix Commons could become a large
"project" of POMs where each simply has a dependency on the library it
wants to convert, which will then convert it automatically with the
plugin when built...then we just need to make the resulting JARs
publicly available (perhaps through OBR and Maven) and we are done.
Just a thought I was having...perhaps Enrique or other people have
thoughts on this.
Thanks for your interest.
-> richard
>
>
> Regards,
>
> Ivo K. Koga
>
> On 11/4/06, Richard S. Hall <he...@ungoverned.org> wrote:
>>
>> John E. Conlon wrote:
>> > What is the latest status of the commons?
>> >
>> > I'm willing to help start doing the spade work if this will help
>> move it
>> > forward.
>>
>> I recently talked with Enrique about this and it sounds like he is going
>> to get some time to start working on it...I think he will post more
>> thoughts on this soon.
>>
>> I just created a placeholder page on the subproject document sections of
>> the wiki:
>>
>>
>> http://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+Commons
>>
>> If you have some specific libraries you with to volunteer to bundle-ize,
>> I can add your name and the libraries to the wiki page for now until we
>> decide what our process will be.
>>
>> -> richard
>>
>
Re: Felix Commons Initiative Status
Posted by "Ivo K. Koga" <iv...@gmail.com>.
Hi Richard,
I don´t know If I understood, but is this an effort to put some of public
knowledge open sources libraries in bundles to be accessable by people who
wants to use it?
If it´s the case, I don´t know exactly how I can contribute, but I think it
will be a very interesting task. Hope I could be helpful in anything.
Regards,
Ivo K. Koga
On 11/4/06, Richard S. Hall <he...@ungoverned.org> wrote:
>
> John E. Conlon wrote:
> > What is the latest status of the commons?
> >
> > I'm willing to help start doing the spade work if this will help move it
> > forward.
>
> I recently talked with Enrique about this and it sounds like he is going
> to get some time to start working on it...I think he will post more
> thoughts on this soon.
>
> I just created a placeholder page on the subproject document sections of
> the wiki:
>
> http://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+Commons
>
> If you have some specific libraries you with to volunteer to bundle-ize,
> I can add your name and the libraries to the wiki page for now until we
> decide what our process will be.
>
> -> richard
>
Re: Felix Commons Initiative Status
Posted by "Richard S. Hall" <he...@ungoverned.org>.
John E. Conlon wrote:
> What is the latest status of the commons?
>
> I'm willing to help start doing the spade work if this will help move it
> forward.
I recently talked with Enrique about this and it sounds like he is going
to get some time to start working on it...I think he will post more
thoughts on this soon.
I just created a placeholder page on the subproject document sections of
the wiki:
http://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+Commons
If you have some specific libraries you with to volunteer to bundle-ize,
I can add your name and the libraries to the wiki page for now until we
decide what our process will be.
-> richard