Hi IMHO using the maven invoker plugin is a better way as you can easily test your plugin with different core versions. but it's only my POV :-)
On 23 August 2017 at 18:03, ahardy42 <[email protected]> wrote: > After a concentrated stint of experimentation, I have setup my tests using > the maven-plugin-testing-harness so that the tests run with a live remote > repository and have all the resources provided in the target/test-classes > directory. > > The solution is here: > https://stackoverflow.com/questions/45241317/hard-time- > mojo-testing-with-maven-plugin-testing-harness/45833419#answer-45833419 > > Sorry if the question title betrays my frustration. The limited feedback I > got here on this user list was also surprising. Obviously with no feedback > to speak of, I have no idea why no-one from the maven community wanted to > communicate on this subject. I would of course be grateful now to get some > feedback of any kind. I'm not asking for anyone to spend more than a minute > to write a reply - I have essentially finished my work with the testing > harness. > > Why was it so difficult? Are the inner workings all in the process of > re-development for maven 4? > > > > -- > View this message in context: http://maven.40175.n5.nabble. > com/maven-plugin-testing-harness-tp5911556p5912964.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
