On 10/2/07, Alin Dreghiciu <[EMAIL PROTECTED]> wrote: > > > On 10/2/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > > You can use the java api for that: java.util.jar. As long as you > > have an input stream, it should work. > > Well, not "how" is my "problem", just the fact that I must read that jar and > get the manifest. As long as the artifact is in the local repo there is no > performace penalty. But if is on a remote repo x number of bundles it could > be problematic in terms of performance.
Well, the jar will be downloaded anyway, right ? So better download it and inspect it locally... > > I guess it would be nice to have a third option to allow specifying > > the wrapping explicitely, but the maven artifact object (or xml) is > > not extensible and both classifiers and types modify the url, so I'm > > not sure if there is a way. I'd rather use the first solution too. > > > > I'm also thinking that having a pax:run goal in a maven plugin could > > be useful too for maven users that do not have pax runner installed. > > You mean beside the pax:provision ? I must have missed this one ;-) > > > Alin > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
