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 PM, stephenconnolly [via Maven] < ml-node+s40175n5858236...@n5.nabble.com> wrote: > 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 <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=5858236&i=0>> > wrote: > > > 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 setClassPathScanning() > is > > called with String parameter but boolean is expected. > > > > protected ContainerConfiguration setupContainerConfiguration() > > { > > ClassWorld classWorld = new ClassWorld( "plexus.core", > > Thread.currentThread().getContextClassLoader() ); > > > > ContainerConfiguration cc = new DefaultContainerConfiguration() > > .setClassWorld( classWorld ) > > .setClassPathScanning( PlexusConstants.SCANNING_INDEX ) > > .setAutoWiring( true ) > > .setName( "maven" ); > > > > return cc; > > } > > > > The versions are chaotic now because > > maven-plugin-testing-harness:3.0.0 > > is dependent on > > maven-core:3.1.1 > > with sisu-inject-plexus other than 1.4.2. > > > > But maven-core:3.0.0 needs to have sisu-inject-plexus:1.4.2 > > > > How should I solve this? > > I tried to upgrade to maven-core:3.1.0 but got another problem. > > > > Should we use Takari IT framework? It will cost me more time to rework > all > > tests. > > > > -- > > Cheers > > Tibor > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://maven.40175.n5.nabble.com/NoSuchMethodError-maven-plugin-testing-harness-3-0-0-tp5858225p5858236.html > To start a new topic under Maven Developers, email > ml-node+s40175n142166...@n5.nabble.com > To unsubscribe from Maven Developers, click here > <http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=142166&code=dGlib3JkaWdhbmFAYXBhY2hlLm9yZ3wxNDIxNjZ8LTI4OTQ5MjEwMg==> > . > NAML > <http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://maven.40175.n5.nabble.com/NoSuchMethodError-maven-plugin-testing-harness-3-0-0-tp5858225p5858238.html Sent from the Maven Developers mailing list archive at Nabble.com.
