[
https://issues.apache.org/jira/browse/AVRO-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867722#comment-13867722
]
Ioannis Canellos commented on AVRO-987:
---------------------------------------
Since avro-tools is just a set of utilities and commands, which is something
that is NOT meant to be shared across bundles, then even keeping it as a plain
jar (not an osgi bundle) could make sense. In fact, even in normal OSGi bundles
often of people prefer to keep their utilities in private packages.
Personally, I don't have a strong preference on this, so I'd say that if
renaming is not an option for a 1.7.x release, let's keep avro-tools a plain
jar and make it an OSGi bundle in 1.8.x.
> 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-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)
