Re: Build failed in Jenkins: Log4jScala #1

Makes sense to me. On 16 January 2017 at 18:54, Apache wrote: > I would expect it to be org.apache.logging:logging-parent. > > Ralph > > On Jan 16, 2017, at 1:23 PM, Matt Sicker wrote: > > I created for this. > I'm not sure about naming, so I

Re: Build failed in Jenkins: Log4jScala #1

I would expect it to be org.apache.logging:logging-parent. Ralph > On Jan 16, 2017, at 1:23 PM, Matt Sicker wrote: > > I created > for this. I'm not sure > about naming, so I opened that up

Re: Build failed in Jenkins: Log4jScala #1

I created for this. I'm not sure about naming, so I opened that up for questions. Naturally, this parent pom shouldn't need to get updated all that often (similar to the ASF parent pom or commons parent pom). We could also look at the commons par

Re: Build failed in Jenkins: Log4jScala #1

I'd imagine it'd be pretty minimal, just inheriting from the latest ASF pom and specifying some plugin baseline configurations where useful. On 16 January 2017 at 14:16, Apache wrote: > That would be fine depending on what is in it. > > Ralph > > On Jan 16, 2017, at 1:15 PM, Matt Sicker wrote:

Re: Build failed in Jenkins: Log4jScala #1

That would be fine depending on what is in it. Ralph > On Jan 16, 2017, at 1:15 PM, Matt Sicker wrote: > > So it seems as though using the log4j parent pom as the parent pom for this > repository won't work that well. I'm thinking we should make a common parent > pom for all log4j projects th

Re: Build failed in Jenkins: Log4jScala #1

So it seems as though using the log4j parent pom as the parent pom for this repository won't work that well. I'm thinking we should make a common parent pom for all log4j projects that can be used by log4j2, log4j-bom, log4j-scala, and log4j-boot (and any others down the line). On 16 January 2017

Build failed in Jenkins: Log4jScala #1

See -- Started by user Matt Sicker [EnvInject] - Loading node environment variables. Building remotely on H10 (ubuntu) in workspace Cloning the remote Git repositor