avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-124) avro release artifact includes ivy jar file but no license
Date Fri, 25 Sep 2009 19:51:15 GMT

    [ https://issues.apache.org/jira/browse/AVRO-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759719#action_12759719
] 

Patrick Hunt commented on AVRO-124:
-----------------------------------

Makes sense.  However I was thinking, why is ivy necessary to the end user (vs contributor)?
You have avro/zk jar, + the dependent jars, ivy jar is really only necessary if you want to
build yourself, and/or test, etc... (am I missing something?) For testing you need to pull
down jars anyway, so really not having ivy would only limit you to not recompiling (if you
are offline). Therefore my assumption that you didn't really intend to include. But, like
I said, what you are saying sounds fine to me as well.

> 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.


Mime
View raw message