Upgrading to KIE 6.2.0.Final gives an Error in pom.xml

[Webster Homer]

We have a drools project with lots of .drl files. This project builds fine under drools 6.1.0.Final. However when I changed the version to 6.2.0.Final

Maven complains about the kjar packaging

and 

project build error: Unresolveable build extension: Plugin org.kie:kie-maven-plugin:6.2.0.Final or one of its dependencies could not be resolved: Failed to collect dependencies for org.kie:kie-maven-plugin:jar:6.2.0.Final ()

What gives?

I tried just reverting the plugin to 6.1.0 which allows the project to build, but it crashes when called. Seems to me either 6.2.0 is unstable or poorly documented and is not backwardly compatible with 6.1.0

In either case we cannot upgrade to it.

This message and any files transmitted with it are the property of Sigma-Aldrich Corporation, are confidential, and are intended solely for the use of the person or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please contact the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited.

[Petr Široký]

Hello,

I am not aware of any changes that could cause this issue. The plugin should work the same as for 6.1.0.Final. Are you by any chance behind firewall? It seems Maven is not able to download/find the plugin, but the 6.2.0.Final is available in Central (http://search.maven.org/#search%7Cga%7C1%7Ckie-maven-plugin)

Could you share your pom.xml, or at least the relevant parts like pluginManagement? Also full maven log with debug enabled (-X) would be great.

Just for a reference, this is an example of the plugin configuration that works: https://github.com/droolsjbpm/droolsjbpm-integration/blob/6.2.0.Final/kie-examples-api/kie-maven-example/pom.xml

Thanks,

Petr

[Webster Homer]

I am behind a firewall. The pom.xml had no issues with 6.1.0.

When I run a mvn install from the command line I don't see an error. I only see it in Eclipse. Which is good. I think I can figure that out. I have not updated my Eclipse to use 6.2.0.Final

My second issue is not so simple however.

When I actually deploy my code to Wildfly and try to execute it, I get an exception:

java.lang.NoClassDefFoundError: Could not initialize class org.eclipse.sisu.wire.ParameterKeys

This appears to be happening in a call to logger.error. We use log4j2 ver 2.0.2

I was only smoke testing the 6.2.0 release. 

I have to say I find KIE often has dependency conflicts with other projects. Especially, Arquillian since both KIE and Arquillian embed maven. I'm guessing that 6.2 has added a new conflict that was not there before. So we will not be moving to it any time soon. Tracking down dependency issues is a pain. 

Thanks,

Web

[Petr Široký]

Hello,

the 6.1.0.Final plugin might have been cached somewhere (your local maven repo, your internal nexus, etc), so that's why I was asking if you are behind firewall. But if you say it works from command line, then it seems the Eclipse config/setup might be the case.

As for the dependency clashes: Yes, this is unfortunately a very big pain overall in Java world. The fact that kie-ci and ARQ (more precisely shrinkwrap-maven-resolver) both depend on different versions of Maven makes them hard to use together. Looking at the maven version in shrinkwrap resolver, you could try to upgrade the shrinkwrap to 2.1.1 (uses maven 3.1.1) or the latest 2.2 development releases. I don't know if that will work though.

Thanks,

Petr

[ouzha...@gmail.com]

Could you tell me how to solve it?

在 2015年3月27日星期五 UTC+8下午6:27:42，Petr Široký写道：