On 9/20/10 3:17 PM, Claus Ibsen wrote:
On Mon, Sep 20, 2010 at 9:11 AM, Willem Jiang<willem.ji...@gmail.com> wrote:
On 9/20/10 10:50 AM, Johan Edstrom wrote:
I really don't think the validator should respect that.
No matter how much those classes are wrapped, I think possibly a
workaround would be okay but since the validator
would fail on wrapped imported classes that require more imports I think
that sucks.
A big banner that says "This is how you shade / this is how you get your
bundle into a smx repo" would be better.
just my 0.2
/je
I dig the karaf feature validate plugin for a while and found it is designed
for OSGi bundle. I had to admit that we need to the create wrap bundles into
the smx repo, or help the project to create a OSGi bundle.
Now I'm heading to create wrap bundle for sip and shiro-core.
I think Chris is working with the lead from Apache Shiro to make it
osgi compliant.
So touch base with him.
Yeah, shiro-core 1.1.0-incubating-SNAPSHOT looks good, I just run the
feature validating with that bundle.
On the other hand making wrap bundles for every single camel component
is tedious.
Because when the project release new version we gotta redo a osgi
bundle release and so on. It's an endless job.
Wrap bundle is a workaround method, and it doesn't support install
multiple version jars at the same time.
The best way to resolve this kind of issue is to help the project to
build the bundle itself :)
For some simple jars that dont need to be a bundle, then the wrap is a
good alternative, as we can use the project .jar directly.
Willem
