Could be I'm going to run the build with each ActiveMQ release since what
we have and see what happens. I'll nuke the latest one I have just in case
it's junked.
Gary
On Fri, Apr 7, 2017 at 1:49 PM, Matt Sicker wrote:
> Corrupted downloads perhaps? That's very odd!
>
> On 7
Corrupted downloads perhaps? That's very odd!
On 7 April 2017 at 15:48, Gary Gregory wrote:
> Hm,
>
> I had changed active mq testing from 5.14.1 to 5.14.4 and that yields:
>
> [ERROR] error: error reading C:\Users\ggregory\.m2\repository\org\apache\
>
Hm,
I had changed active mq testing from 5.14.1 to 5.14.4 and that yields:
[ERROR] error: error reading
C:\Users\ggregory\.m2\repository\org\apache\activemq\activemq-broker\5.14.4\activemq-broker-5.14.4.jar;
invalid LOC header (bad signature)
[ERROR] error: error reading
It's already in the pom:
https://github.com/apache/logging-log4j2/blob/master/log4j-1.2-api/pom.xml#L74
I don't think it's scope=test, but type=test-jar.
On 7 April 2017 at 15:41, Gary Gregory wrote:
> I added to log4j-1.2-api:
>
>
> org.apache.logging.log4j
I added to log4j-1.2-api:
org.apache.logging.log4j
log4j-core
test
test
but that blows up Maven 3.3.9:
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
must be
Maybe it's because it's a new snapshot version and you need to run "mvn
install" at least once?
On 7 April 2017 at 15:40, Matt Sicker wrote:
> This is the first I've ever seen that error, and it's not popping up in
> Jenkins or anything. I don't think the code has changed
This is the first I've ever seen that error, and it's not popping up in
Jenkins or anything. I don't think the code has changed since 2.8.2, so I
don't know why it would break.
On 7 April 2017 at 15:34, Gary Gregory wrote:
> This is with Maven 3.3.9 though.
>
> Gary
>
>
This is with Maven 3.3.9 though.
Gary
On Fri, Apr 7, 2017 at 1:11 PM, Matt Sicker wrote:
> Does it have a dependency on log4j-core:test? It should. Could be a bug in
> your beta version of Maven ;)
>
> On 7 April 2017 at 14:46, Gary Gregory wrote:
>
Does it have a dependency on log4j-core:test? It should. Could be a bug in
your beta version of Maven ;)
On 7 April 2017 at 14:46, Gary Gregory wrote:
> Hi All:
>
> I'm seeing this in master:
>
> [INFO] --- maven-bundle-plugin:3.2.0:manifest (default) @ log4j-1.2-api
>