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):
