Tim Ellison wrote:
On 06/10/16 05:02, Josh Elser wrote:
Things to look into for next release:
* apache-pirk-0.2.0-incubating.jar appears to have way too many LICENSE
entries (the MIT/BSD licensed stuff doesn't appear to be included).
Seems like they were meant for the -exe.jar. Probably just
maven-jar-plugin being a little over-aggressive :)
Yeah, the license entries in the built apache-pirk-0.2.0-incubating.jar
come from
apache-pirk-0.2.0-incubating/src/main/resources/META-INF/bin-license-notice/
in the release.
The licenses were placed there to avoid confusion in the source release.
There are plans for how to address the licenses in the binaries (see
below).
If the refactoring doesn't make it into 0.2.0, it might be good to move
those files to something that isn't put into the source-jar. Don't need
to create more confusion over licensing. Either way, not a huge deal
until graduation is a topic of discussion. I'm sure it will be worked
out in the end :)
Assorted other thoughts:
For 0.1.0, I remember that there were some JARs also staged, but it
doesn't look like these ever made it to Maven Central. Are there any
plans to do this? Not having these JARs in Central may become an
impediment to adoption.
You will recall that there were a number of problems in getting the
licenses and notice files correct for these binary releases; and the
work to fix it would be "wasted" as the code gets restructured into
Maven modules which handle the l&n files better.
So for the moment, we agreed to only release the source zip, and delay
distributing convenience binaries until after the restructuring. DarinJ
has put forward a proposed rework that is looking good.
Yup, I do recall that there was an original attempt at publishing JARs.
Mostly a prod at helping to ease adoption (help get more people
involved) in the future :). I did forget that there was some refactoring
work in the pipeline.
Thanks!
