We require jars that are built to conform to maven standards. But they do not need to be built with maven. That means they do need a pom.properties in there. If gradle does not add that automatically, you should be able to automate that yourself.

The pom.properties is a very simple file, that requires 3 key value pairs:

#Generated by Maven
#Wed Nov 18 14:44:09 PST 2009
version=2.2
groupId=javax.el
artifactId=el-api

This is necessary for discovery of jars, and versioning of jars within the same JVM. Maven provides a standard for this, so it seemed redundant us creating yet another way to declare this meta data.

Mark

On 28 Jan 2014, at 22:03, Andrew Berman <rexxe98@gmail.com> wrote:

Hello,

I keep running into an issue where Drools is looking for a pom.properties file and I get an error since I'm using Gradle.  Does Drools depend on Maven?  I noticed there is a lot of code looking for Maven and pom.xml and pom.properties, why is that?

Thanks!

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users

_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users