Re: Build failed in Jenkins: Log4j 2.x #2771

On Mon, May 8, 2017 at 6:40 PM, Matt Sicker wrote: > If OSGi is going to refuse to support multi-release jars, then I doubt > they're going to remain relevant over time as it's a rather important > feature for libraries. > Don't tell that to IBM... ;-) Gary > > On 8 May 2017 at 11:21, Ralph G

Re: Build failed in Jenkins: Log4j 2.x #2771

If OSGi is going to refuse to support multi-release jars, then I doubt they're going to remain relevant over time as it's a rather important feature for libraries. On 8 May 2017 at 11:21, Ralph Goers wrote: > BTW - it may, or may not, be possible to run the full build with Java 9 > once the bug

Re: Build failed in Jenkins: Log4j 2.x #2771

BTW - it may, or may not, be possible to run the full build with Java 9 once the bug Gary found gets fixed - which should be in the next EA release. See http://mail.openjdk.java.net/pipermail/jdk9-dev/2015-July/002414.html .

Re: Build failed in Jenkins: Log4j 2.x #2771

mvn site should work, but only when run by itself under Java 9. That is how you run it for a release build anyway - all by itself. Ralph > On May 8, 2017, at 8:33 AM, Matt Sicker wrote: > > How exactly are we supposed to make a release then if "mvn site" doesn't > work? > > On 8 May 2017 at 1

Re: Build failed in Jenkins: Log4j 2.x #2771

How exactly are we supposed to make a release then if "mvn site" doesn't work? On 8 May 2017 at 10:32, Ralph Goers wrote: > The issue is that Matt keeps changing the Jenkins job to do "mvn clean > install site” instead of “mvn clean install”. The job cannot run the site > plugin as that must be

Re: Build failed in Jenkins: Log4j 2.x #2771

The issue is that Matt keeps changing the Jenkins job to do "mvn clean install site” instead of “mvn clean install”. The job cannot run the site plugin as that must be run in java 9. Ralph > On May 8, 2017, at 7:57 AM, Matt Sicker wrote: > > But the issue in the stack trace is that the javado

Re: Build failed in Jenkins: Log4j 2.x #2771

But the issue in the stack trace is that the javadoc plugin is being run by java 7 in log4j-api when it needs to be run as java 9. On 8 May 2017 at 09:57, Matt Sicker wrote: > I only just recently fixed the email address configured in Jenkins, so > there were probably several other failure messa

Re: Build failed in Jenkins: Log4j 2.x #2771

I only just recently fixed the email address configured in Jenkins, so there were probably several other failure messages that bounced to log4j-dev@. On 8 May 2017 at 09:43, Mikael Ståldal wrote: > I don't understand why the Jenkins build suddenly starts failing. It cannot > possibly be due to m

Re: Build failed in Jenkins: Log4j 2.x #2771

I don't understand why the Jenkins build suddenly starts failing. It cannot possibly be due to my change to BUILDING.md, can it? On Mon, May 8, 2017 at 4:03 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See redirect?page

Build failed in Jenkins: Log4j 2.x #2771

See Changes: [mikael.staldal] Fix typo -- [...truncated 63.84 KB...] V extends Object declared in method forEach(BiConsumer) [WARNING]