Hm, I think we are running into on of the NOTICE in the root of the bundle
svn issues again.

Both, Bridge and Jetty do not get their NOTICE copied into their binary jar
causing the somewhat awkward situation that the source artifacts have a
NOTICE claiming they contain code from the OSGi Alliance and from Mortbay
but they really don't - while the binary artifacts have a NOTICE that
doesn't mention neither but they actually do contain classes from both.

IIRC, the solution is to use the append-resources for the NOTICE and than
it should work correctly. As with other cases, I personally think that is a
-1 as I don't like shipping binaries which violate licenses but I can live
with being overruled by the majority provided we fix this in trunk.

regards,

Karl


On Fri, Sep 30, 2016 at 3:26 PM, Carsten Ziegeler <cziege...@apache.org>
wrote:
>
> I would like to call a vote on the following subproject releases:
>
> Http Base 3.0.14 (2 issues)
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12338092
>
> Http Bridge 3.0.14 (2 issues)
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12338093
>
> Http Jetty 3.3.0 (3 issues)
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12338094
>
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1140/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1140 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org




--
Karl Pauls
karlpa...@gmail.com

Reply via email to