incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Fernández <wik...@apache.org>
Subject Re: Groovy release and LEGAL-171
Date Mon, 08 Jun 2015 07:07:17 GMT
Hi,

my two cents without knowing in detail the issue:

Could I make a clean build from a source release without that file?

Without looking to the source code, I'm pretty sure it could be replaced by
the right flags of the maven-javadoc-plugin...

Other opinions better formed than mine are welcomed to the discussion.

Cheers,


On Mon, Jun 8, 2015 at 8:57 AM, Roman Shaposhnik <rvs@apache.org> wrote:

> Hi!
>
> Groovy is currently voting a release where exactly
> the same issue as LEGAL-171 got raised. Their
> tarball currently contains the file in question:
>     buildSrc/src/main/java/JavadocFixTool.java
> with the LICENSE described in LEGAL-171.
>
> My understanding is that this file should NOT
> be redistributed by releases of software under
> ALv2 even though Groovy only uses it during
> the build and doesn't create a shipable binary.
>
> Thoughts?
>
> Thanks,
> Roman.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernandez@redlink.co
w: http://redlink.co

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message