You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2012/11/08 18:12:12 UTC
[jira] [Commented] (AVRO-1197) Avro Java mapreduce pom depends on
IPC test jar which is not exposed
[ https://issues.apache.org/jira/browse/AVRO-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493307#comment-13493307 ]
Doug Cutting commented on AVRO-1197:
------------------------------------
Mike, I wonder why this works for me? I'm using Maven 3.03 and 'mvn clean test' succeeds without this patch, as it does under Jenkins:
https://builds.apache.org/job/AvroJava/
What's different in your environment?
That said, the patch looks correct. If one module uses another's test code then it makes sense that the latter might have to explicitly publish those, however I'm not enough of a Mavenista to know the rules or conventions here. If we can avoid publishing tests in releases that'd be nice, since I'd rather not have to maintain back-compatibility for test APIs.
> Avro Java mapreduce pom depends on IPC test jar which is not exposed
> --------------------------------------------------------------------
>
> Key: AVRO-1197
> URL: https://issues.apache.org/jira/browse/AVRO-1197
> Project: Avro
> Issue Type: Bug
> Components: build, java
> Reporter: Mike Percy
> Assignee: Mike Percy
> Fix For: 1.7.3
>
> Attachments: AVRO-1197.patch
>
>
> I am getting a build issue on trunk:
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Avro Toplevel .............................. SUCCESS [1.202s]
> [INFO] Apache Avro Java .................................. SUCCESS [0.755s]
> [INFO] Apache Avro ....................................... SUCCESS [7.015s]
> [INFO] Apache Avro Compiler .............................. SUCCESS [1.554s]
> [INFO] Apache Avro Maven Plugin .......................... SUCCESS [1.279s]
> [INFO] Apache Avro IPC ................................... SUCCESS [2.914s]
> [INFO] Trevni Java ....................................... SUCCESS [0.195s]
> [INFO] Trevni Java Core .................................. SUCCESS [0.690s]
> [INFO] Apache Avro Mapred API ............................ FAILURE [0.427s]
> [INFO] Trevni Java Avro .................................. SKIPPED
> [INFO] Trevni Specification .............................. SKIPPED
> [INFO] Apache Avro Tools ................................. SKIPPED
> [INFO] Apache Avro Protobuf Compatibility ................ SKIPPED
> [INFO] Apache Avro Thrift Compatibility .................. SKIPPED
> [INFO] Apache Avro Maven Archetypes ...................... SKIPPED
> [INFO] Apache Avro Maven Service Archetype ............... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 17.124s
> [INFO] Finished at: Wed Nov 07 16:30:55 PST 2012
> [INFO] Final Memory: 27M/81M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project avro-mapred: Could not resolve dependencies for project org.apache.avro:avro-mapred:jar:1.7.3-SNAPSHOT: Could not find artifact org.apache.avro:avro-ipc:jar:tests:1.7.3-SNAPSHOT in apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :avro-mapred
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira