[
https://issues.apache.org/jira/browse/AVRO-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986618#action_12986618
]
Holger Hoffstätte commented on AVRO-737:
----------------------------------------
Scott, I use 3.0.2 and my own personal nexus instance, but that had nothing to
do with the problem as everything was local. As I said, tools tries to use the
avro-tests.jar but as far as I can tell this is not yet declared anywhere. I
did full clean installs and always skip tests by default etc. (not a mvn newbie
:)
I don't have access to the machine right now but will take another look
tomorrow. If this works for everyone else just commit & I'll continue to
track/report against svn trunk.
> 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.