[
https://issues.apache.org/jira/browse/AVRO-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986755#action_12986755
]
Scott Carey commented on AVRO-737:
----------------------------------
Holger,
I can reproduce your problem by deleting org/apache/avro from my local repo and
doing 'clean compile'. 'clean test' or 'clean install' works. Changing the
dependency from <classifier>tests</classifier> to <type>test-jar</type> does
not seem to help.
Even though the test scope dependency is not needed for 'compile' it is
searching for it and fails when it is not found.
A possible solution is to re-map the test-compile portion in the avro project
to occur in the compile phase. That should attatch the test stuff to the
reactor eariler.
> 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.
