On 3/12/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Is this going to result in a copy of all the artifacts with added
bundled metadata?
Will the structure will be same? Just wondering if the bundles should
just be included in the main repository with a classifier.
this is going to be a "beta"
It processes all jar artifacts contained in a repo.
So if the repo it points to contains the whole maven repo, it will do
the whole thing.
Carlos Sanchez wrote:
there's already a bundleall goal in the felix bundle plugin that will
generate osgi bundles for each dependency in the tree
https:/
there's already a bundleall goal in the felix bundle plugin that will
generate osgi bundles for each dependency in the tree
https://issues.apache.org/jira/browse/FELIX-199
are you processing the whole repo or just a tree of dependencies
On 3/13/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
Hi Carloz
Hi Carloz,
Just in case you need a mojo to process the repository,
I'm almost done with this RPM Factory mojo.
I'm going to use it to RPM the maven repository, but
with a little modification, it could be used to create and add
manifests to all the jars in the maven repository as well.
I'll prob
Is this going to result in a copy of all the artifacts with added
bundled metadata?
Will the structure will be same? Just wondering if the bundles should
just be included in the main repository with a classifier.
- Brett
On 12/03/2007, at 4:46 PM, Carlos Sanchez wrote:
There are some ini
There are some initiatives like Apache Felix about repackaging
libraries from the maven repository until projects themselves include
the OSGi manifest.
It makes sense in the meantime to have a Maven repo with same
structure but with OSGi bundles. This repo would be temporal and
things could chang