I don't think that's a good solution. What you have done is to bundle those
classes inside your jar again.
On Jan 16, 2015 11:14 PM, Sithumini Senevirathne sithumi...@wso2.com
wrote:
Hi,
This was solved using embedding dependencies Embed-Dependency. Below is
the code snippet,
Hi,
I am currently developing a G-Reg feature[1] and for that I use a 3rd party
library called membrane-soa-model. This library uses Groovy 2.0 which needs
ASM 4. I created an osgi bundle for the membrane. If we run the Registry
server ASM 3 bundle also get Active as product-AS uses it. When
I think what you should do is to depend on the correct version. Can you
attach full pom.xml.
On Jan 16, 2015 5:39 PM, Sithumini Senevirathne sithumi...@wso2.com
wrote:
Hi,
I am currently developing a G-Reg feature[1] and for that I use a 3rd
party library called membrane-soa-model. This
Hi,
This was solved using embedding dependencies Embed-Dependency. Below is
the code snippet,
instructions
Bundle-Name${project.artifactId}/Bundle-Name
Bundle-SymbolicName${project.groupId}.${project.artifactId}/Bundle-SymbolicName