Re: Is the Maven 3 lifecycle extensions documentation page up to date?

So the only one that worked as the -D arg to the maven invocation. I checked the 10K jar into source control to avoid the bootstrap problem, and Circle CI does exactly what I'd hope for. Proof being the intended result - https://buildradiator.org/r#b7n63m6hcb9sm2ttdn/Build_Radiator_DotOrg_Master

Re: Is the Maven 3 lifecycle extensions documentation page up to date?

OK, thanks. I'll kill the /build/extensions element of the pom, and try .mvn/extensions.xml - Paul On Thu, Jun 1, 2017 at 7:26 AM, Igor Fedorenko wrote: > Build extensions are loaded too late to contribute event spies, see how > EventSpyDispatcher makes a copy of spies

Re: Is the Maven 3 lifecycle extensions documentation page up to date?

Build extensions are loaded too late to contribute event spies, see how EventSpyDispatcher makes a copy of spies when it's created. And even if EventSpyDispatcher didn't make the copy, I think build extensions are not in scope to capture all events, i.e. things that happen before/after individual

Is the Maven 3 lifecycle extensions documentation page up to date?

This page: https://maven.apache.org/examples/maven-3-lifecycle-extensions.html My problem: I have an extension that works just fine in ${maven.home}/lib/ext/ isn't activated when I do the all the things mentioned in the page. So my extension was copied from one the Takari EventSpy plugins

[GitHub] maven-surefire issue #152: [SUREFIRE-1378] Nice to have systemPropertiesFile...

Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/152 @michaldo Version 3.0 will have configurable via Java interface in pom.xml. This way you can turn the behavior to file system. Please check Jira [1] with version 3.0. Maybe we