[
https://issues.apache.org/jira/browse/AVRO-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-987:
------------------------------
Attachment: AVRO-987-exe.patch
Here's a patch that fixes this. It's not 100% compatible, since the nodeps
tools jar will now be called avro-tools-nodeps-X.Y.Z.jar instead of
avro-tools-X.Y.Z-nodeps.jar, which means that users of that jar will need to
update their poms when they upgrade.
Does this seem reasonable to folks? The other alternative is to not package
avro-tools as an osgi bundle, but I'd rather keep things consistent across
modules.
> Make Avro OSGi ready
> --------------------
>
> Key: AVRO-987
> URL: https://issues.apache.org/jira/browse/AVRO-987
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Ioannis Canellos
> Assignee: Ioannis Canellos
> Fix For: 1.7.6
>
> Attachments: AVRO-987-1_6_3-patch.txt, AVRO-987-exe.patch,
> AVRO-987-patch-updated.txt, AVRO-987-patch.txt, AVRO-987.patch
>
>
> It would be really nice to be able to use Avro inside OSGi. To achieve this
> two things are required:
> i) Provide proper MANIFEST.MF.
> ii) Deal with potential class loading issues. Avro uses Class.forName a lot
> and that is not very OSGi friendly.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
