[
https://issues.apache.org/jira/browse/AVRO-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759708#action_12759708
]
Doug Cutting commented on AVRO-124:
-----------------------------------
I'd currently intended to include all of the dependent jar files in the
release, so that the release can be used standalone & offline, without folks
having to locate dependencies, with Ivy or otherwise. Given that, the lack of
an Ivy license file is an oversight. It's under the AL2, so the top-level
license covers us legally, but, by convention, we're including the license
files for other AL2 stuff in lib and should be consistent. Does that make
sense?
Ideally we should probably configure Ivy so that it looks in the lib/ directory
for dependencies so that offline builds work when a release is first unpacked.
I just tried to configure that but failed to find a simple way to do it yet...
> avro release artifact includes ivy jar file but no license
> ----------------------------------------------------------
>
> Key: AVRO-124
> URL: https://issues.apache.org/jira/browse/AVRO-124
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.1.0
> Reporter: Patrick Hunt
> Priority: Blocker
>
> The release artifact includes the ivy jar, but no license file, notice, etc...
> I believe that you don't intend to ship this, but it snuck into the release
> based on it being in the lib directory? (esp since the build.xml will d/l the
> jar if it's missing)
> You probably just need to explicitly exclude it when building the release
> package (see ZooKeeper build.xml, I found the same issue there when moving to
> ivy)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
