[
https://issues.apache.org/jira/browse/AVRO-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986799#action_12986799
]
Scott Carey commented on AVRO-737:
----------------------------------
It appears that this is a bug in Maven. The test-jar test dependency is
resolved mistakenly during the compile phase rather than the test-compile
phase. It isn't possible to move the test compilation up in the lifecycle
without a lot of work because the phases between compile and test-compile do
things like configure the classpath and filter files.
The workaround is to use 'test-compile' instead of 'compile' when the test
artifact has not been installed to the local repo.
If there are suggestions for a better work-around I'd love to hear it. We
could go back to copying those test classes across projects but I'd rather not.
> 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.
