Niclas Hedhman wrote:
This is just one more of those Maven things...
Before releasing Qi4j 1.0, I put in place the Maven Enforcer Plugin,
which makes sure that every version of every plugin used is specified.
So, now you are using an unversioned (LATEST) plugin.
That's what I suspected, but I wasn't sure.
Quick work around for you is to add the eclipse plugin and version in
the <pluginsManagement> section of the poms.
As a workaround for me alone I'd prefer the -Denforcer.skip=true I'm
currently using, but if you meant that I should add
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.7</version>
</plugin>
to all the relevant poms and push it, I can do that(except for core of
course).
Cheers,
Georg
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
