Hi,
Since I only needed to inject the Maven propject, and rather than use a
stub, I decided to inject the Maven project manually in my mojo.
final MavenProject mvnProject = new MavenProject() ;
mvnProject.setFile( baseDir ) ;
this.rule.setVariableValueToObject( mojo, project, mvnProject );
Hi,
Le 23/07/2014 20:29, Karl Heinz Marbaise a écrit :
my assumption is to use the maven-compat artifact in your project
Actually, I already had this artifact in my dependencies. ;)
Your answer gave me the idea to try without, but it was worst.
Le 23/07/2014 22:06, Martin Gainty a écrit :
Le jeudi 24 juillet 2014 12:05:37 Barrie Treloar a écrit :
On 24 July 2014 01:08, Vincent Zurczak vincent.zurc...@linagora.com wrote:
Hi,
I am not sure this is the right mailing-list.
Maybe I should have posted to the dev list. Anyway...
I have started working on new Maven plug-in
Hi,
I am not sure this is the right mailing-list.
Maybe I should have posted to the dev list. Anyway...
I have started working on new Maven plug-in last week and I have set up
unit tests using the testing-harness plugin.
I have problems with Maven injected fields, such as the Maven project.
Hi,
my assumption is to use the maven-compat artifact in your project apart
from that it would be interesting which kind of plugin do you develop
and which intention it has...
Kind regards
Karl-Heinz Marbaise
On 7/23/14 5:38 PM, Vincent Zurczak wrote:
Hi,
I am not sure this is the right
On 24 July 2014 01:08, Vincent Zurczak vincent.zurc...@linagora.com wrote:
Hi,
I am not sure this is the right mailing-list.
Maybe I should have posted to the dev list. Anyway...
I have started working on new Maven plug-in last week and I have set up
unit tests using the testing-harness
