Build works on java8 with “mvn clean test install site.” On java7 and java11
“mvn clean test” works.
One curiousity, “mvn apache-rat:check” fails with 4 license violations, namely:
src/native/unix/native/.indent.pro
src/native/unix/configure
src/native/unix/support/config.guess
src/native/unix/support/config.sub
I think aside from these I would likely be a +1. The “.indent.pro” looks to be
excludable, the others, being GPL licensed, we may need to add to the
NOTICE.txt and then add the Apache 2.0 license header to them? IIRC, we should
be able to do something like that
Cheers,
-Rob
> On Jun 17, 2019, at 8:13 AM, Mark Thomas <[email protected]> wrote:
>
> It has been ~18 months since the last Commons Daemon release. After the
> recent flurry of activity, I think we are ready for a release.
>
> Notable changes include:
> - Improved JRE/JDK detection to support increased range of both JVM
> versions and vendors.
> - Procrun. Change the default service from LocalSystem to
> 'NT Authority\LocalService'
>
> The full set of changes is in the changelog
>
> 1.1.1 can be obtained from (r34537):
> https://dist.apache.org/repos/dist/dev/commons/daemon/
>
> The git tag is:
> https://github.com/apache/commons-daemon/commits/COMMONS_DAEMON_1_1_1
> 4319f482e1ff6ea7655e1377120750fd6ecc3810
>
> The Maven Staging repo is:
> https://repository.apache.org/content/repositories/orgapachecommons-1441/
>
> The Windows binaries have been signed by the Symantec code signing service.
>
>
>
> [ ] Approved - go ahead and release Commons Daemon 1.1.1
> [ ] Broken - do not release because...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
