[
https://issues.apache.org/jira/browse/AVRO-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Carey updated AVRO-737:
-----------------------------
Attachment: migrate_avro_packages.v5.sh
AVRO-737.v5.patch
I believe this is the last patch version. I have tested it several times.
There are minor differences from the last one:
* This includes the changes to CHANGES.txt
* The ipc.mapred.tether generated classes are now in mapred.tether inside of
the avro-mapred project.
I'll commit this after confirmation that this works. The CHANGES.txt message
for this change is:
{noformat}
AVRO-716. Java: Improve correlation between packages and modules.
Each module introduced by AVRO-647 now exclusively provides
different java packages. This required moving several classes
around into new packages and will therefore require users to
change their package imports when upgrading to Avro 1.5.0.
Summary of changes:
* AvroRemoteException has moved to org.apache.avro
* ByteBufferInputStream and ByteBufferInputStream have moved
to org.apache.avro.util
* InduceSchemaTool has moved to org.apache.avro.tools
* SpecificCompiler, SchemaTask, and ProtocolTask have moved
to org.apache.avro.compiler.specific
* The Idl compiler has moved to org.apache.avro.compiler.idl
* ReflectRequestor and ReflectResponder have moved to
org.apache.avro.ipc.reflect
* GenericRequestor and GenericResponder have moved to
org.apache.avro.ipc.generic
* SpecificRequestor and SpecificResponder have moved to
org.apache.avro.ipc.specific
(scottcarey)
{noformat}
> 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, AVRO-737.v2.patch, AVRO-737.v3.patch,
> AVRO-737.v4.patch, AVRO-737.v5.patch, migrate_avro_packages.sh,
> migrate_avro_packages.v4.sh, migrate_avro_packages.v5.sh
>
>
> 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.
