This is the branch 3.0-rc1 in surefire project
https://github.com/apache/maven-surefire/tree/3.0-rc1
The problematic project is maven-surefire-report-plugin.
https://github.com/apache/maven-surefire/blob/3.0-rc1/maven-surefire-report-plugin/pom.xml
As we can see maven-surefire-report-plugin/pom.x
You should really try Takari plugin testing harness. It's good, works
for all 3.x maven versions too.
--
Regards,
Igor
On Thu, Jan 7, 2016, at 08:04 AM, Stephen Connolly wrote:
> Ha! I'm knee deep in trying to switch maven-release over to Maven 3 and
> fighting the AbstractReleaseTestCase is pr
FWIW, Sisu tries to maintain compatibility across different versions where
possible - if you find that you can’t use a newer release in place of an older
one then you can always report this (http://www.eclipse.org/sisu/support/) with
the details and any test projects/logs. Also note that sisu-in
JBoss has nice solutions with BOM file.
In Maven 4.0 migration we should not forget to provide several
dependencyManagements POM with version 4.0.0 of individual dependencies.
There I can see that e.g. IT testing has recommended set of artifacts with
certain versions.
On Thu, Jan 7, 2016 at 2:05 P
Ha! I'm knee deep in trying to switch maven-release over to Maven 3 and
fighting the AbstractReleaseTestCase is proving too much for my allocated
morning of project time... to say this whole thing is a mess would be an
understatement ;-)
On 7 January 2016 at 12:40, Tibor Digana
wrote:
> I am mig
I am migrating plugin to 3.0.0 and I have a problem with a test
because it fails due to maven-plugin-testing-harness:3.0.0 cannot call a
method:
setClassPathScanning(Ljava/lang/String;)Lorg/codehaus/plexus/ContainerConfiguration;
In maven-plugin-testing-harness' code the method setClassPathScannin
