[
https://issues.apache.org/jira/browse/AVRO-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986302#action_12986302
]
Holger Hoffstätte commented on AVRO-737:
----------------------------------------
Got v3 to run & apply on Windows; no changes necessary except for renaming the
script to .bat. Regular commandline GNU patch wouldn't eat the patch file, but
TortoiseSVN liked it and everything worked/built. Nice! The changes are pretty
much exactly what I had in mind, thanks a lot. This will be very helpful going
forwards.
One addition to the first block of instructions in the script:
svn mv lang/java/avro/src/main/java/org/apache/avro/ipc/package.html
lang/java/ipc/src/main/java/org/apache/avro/ipc/
to move the lonely package.html file across projects.
I did get a build/install error with the tools project but couldn't really find
what was wrong. Might try again later.
> 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,
> migrate_avro_packages.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.
