[
https://issues.apache.org/jira/browse/AVRO-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Zeyliger updated AVRO-282:
---------------------------------
Attachment: AVRO-282.patch.txt
Here's what's going on. The "avroj" target packs up in the jar whatever
happens to match in build/lib/*.jar. If you've run "avro test-java"
beforehand, that will include slf4j-simple, and everything will be fine. If
not, it won't work.
I'm by no means an Ivy expert. The patch I'm attaching introduces two new ivy
configurations: "build" (for build dependencies, like javacc) and "avroj" (for
avroj's runtime dependencies). The ivy-retrieve-avroj target will ask ivy to
download avroj's dependencies in a separate directory, which gets packaged up
during the avroj target. (So, no longer will avroj include random stuff from
build/lib. Specifically, it won't include javacc.) Similarly, folks who
depend on Avro, shouldn't need to get javacc either.
I suspect there are still too many dependencies: paranamer pulls in all of ant,
which isn't strictly necessary.
> avroj build broken depending on build order
> -------------------------------------------
>
> Key: AVRO-282
> URL: https://issues.apache.org/jira/browse/AVRO-282
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Philip Zeyliger
> Assignee: Philip Zeyliger
> Priority: Minor
> Attachments: AVRO-282.patch.txt
>
>
> If you build avroj without having built the tests, there's no logging
> framework implementation, and you get
> bq. "Exception in thread "main" java.lang.NoClassDefFoundError:
> org/slf4j/impl/StaticLoggerBinder"
> when running
> bq. java -jar build/avroj-1.2.0-dev.jar rpcsend
> '{"protocol":"sleepy","namespace":null,"types":[],"messages":{"sleep":{"request":[{"name":"millis","type":"long"}],"response":"null"}}}'
> sleep localhost 7002 '{"millis": 203}'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.