On 20/09/15 21:15, Stian Soiland-Reyes wrote:
I had the same issue, and ignored it. It is the adapter it is looking for,
to know what (if any) needs updating on the Eclipse side.
It is probably best to let Eclipse add the ignore section to the jena super
pom then, as executing this plugin is not needed while editing code (e.g.
it is not generating source code from an XSD or similar).
Yes, this is a good idea. It reduces friction when importing Jena into
Eclipse.
JENA-1042
and just done in the jena parent POM so we can see what unexpected
effects it has.
Andy
The Eclipse maven plugin section that would be added is safe to add, it is
basically a no-op for non-Eclipse Maven users.
On 20 Sep 2015 14:38, "Andy Seaborne" <[email protected]> wrote:
On 20/09/15 11:14, Dave Reynolds wrote:
On 19/09/15 17:54, Claude Warren wrote:
The contract test maven plugin produces reports about the contract tests.
It does not run them and can be ignored. However, I am curious as to why
the system can't find the plugin. It is in the maven repository (
http://mvnrepository.com/artifact/org.xenei/contract-test-maven-plugin)
Not something I can answer. I had thought it might be because I was on
an older eclipse but I've tried a clean install of Mars and got the same
behaviour. The error message is complaining about not finding the plugin
in the Marketplace, I've no idea whether it is trying the maven repo or
not.
Being messed about by Maven is nothing new for me so I'm just happy
Eclipse offers to just hide the error!
Dave
I thought was Eclipse is looking for an adapter (in the Eclipse
Marketplace) to handle that maven goal.
Andy
