[
https://issues.apache.org/jira/browse/AVRO-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983911#action_12983911
]
Scott Carey commented on AVRO-737:
----------------------------------
Ah, yes AvroRemoteException.
I was afraid to move it because doing so changed the generated method
signatures. If we're already going to change that, then I'll move it to
o.a.a.util or o.a.a. If so, we should fix AVRO-732 for 1.5.0 as well.
Several classes implement Tool that are not in the Tools package. I assume
that we will have use cases in the future for Tool classes that don't reside in
avro-tools. I did not investigate whether the ones already defined in other
projects can be moved easily.
> Java: Improve correlation between packages and modules
> ------------------------------------------------------
>
> Key: AVRO-737
> URL: https://issues.apache.org/jira/browse/AVRO-737
> Project: Avro
> Issue Type: Sub-task
> Components: java
> Reporter: Scott Carey
> Assignee: Scott Carey
> Fix For: 1.5.0
>
> Attachments: AVRO-737.v1.patch
>
>
> Several packages have classes from multiple modules in the new layout.
> In general, we should avoid this. Ideally, o.a.a.ipc would only exist in the
> avro-ipc.jar for example.
> For 1.5.0, I'd like to move the easy stuff around to better correlate
> packages with modules.
> This will cause API changes we need to document. Unfortunately, moving
> classes around is not something you can do gradually. Ideally these are
> isolated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
