Repackage ASM code within separate namespace

[hzpz]

See https://code.google.com/p/json-smart/issues/detail?id=52.
I am not sure about the OSGi side of things. Please review and verify that the change does not break the OSGi bundle.

[aborg0]

From OSGi point of view, this is probably fine, I doubt people use json-smart because of asm:asm transitive dependency and they can create their own bundle from it if they prefer. (Or just use the new asm version, which I suspect is the recommended option anyway.) When I suggested to embed it, I forget to make the packages private. With this change the net.minidev:asm bundle should bump its version number to 2.x though.

[hzpz]

Thanks for the review! As for the asm dependency (which is still there despite the maven-jarjar-plugin), it might be a better idea to use the maven-shade-plugin. See http://stackoverflow.com/a/5727793/3790806.

[UrielCh]

hello,

I understand anything about OSGI.

Could you suggest a patch out of net.minidev.asm json-smart?

should I add:

org.apache.felix
maven-bundle-plugin
2.3.7
true


${project.groupId}.${project.artifactId}
${project.artifactId}
${project.version}
net.minidev.asm,net.minidev.asm.ex

in my ASM pom ?

[UrielCh]

Can you check the last Git changes ?