On Mon, Jun 8, 2015 at 11:16 AM, Jochen Theodorou wrote:
>
> Without looking to the source code, I'm pretty sure it could be replaced by
>> the right flags of the maven-javadoc-plugin...
>>
>
> can it be used outside maven? Becuase we are talking about a gradle build.
>
Ah, right, it's a Gradle-b
It can easily be replaced with a Gradle plugin.
2015-06-08 9:07 GMT+02:00 Sergio Fernández :
> 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 repl
Am 08.06.2015 09:07, schrieb Sergio Fernández:
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...
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 welcome
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 redistribu
