[
https://issues.apache.org/jira/browse/AVRO-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986313#action_12986313
]
Holger Hoffstätte commented on AVRO-737:
----------------------------------------
The remaining problem is that the avro:test-jar is not yet found for assembling
tools:
[ERROR] Failed to execute goal on project avro-tools: Could not resolve
dependencies for project org.apache.avro:avro-tools:jar:1.5.0-SNAPSHOT: Failure
to find org.apache.avro:avro:jar:tests:1.5.0-SNAPSHOT in
http://tux:8080/nexus/content/groups/public was cached in the local repository,
resolution will not be reattempted until the update interval of nexus has
elapsed or updates are forced -> [Help 1]
There is no avro:avro-tests.jar created yet. Doing so manually will create the
jar, but it will then not be seen or installed during the install phase since
it is not declared anywhere.
> 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.
