The problem is this:

1) At the moment you need to put enum helper classes in /lib (we simply haven't changed the way this worked from 5.5)

2) If the same JAR contains classes you need for rule authoring you need it uploaded to the M2 Repository and added as a dependency to your project.
3) If your JAR classes were compiled against classes not in the JAR (or other project dependency) you'll the classes not found messages.

Item (1) is arguably acceptable as the database helper class is a (rule authoring) design time requirement and not a (KJAR) runtime requirement.

Sent on the move

On 21 Feb 2014 16:38, "SrjTx" <clickthex@yahoo.com> wrote:
I am not 100% clear on the relationship between these two.

I want to have an enumeration that is populated from a DB.
It makes sense to me that I have to put the jar with the DB access class in
the repository.  I know that I have to also put it in the /lib dir, but I
don't understand the relationship and why I have to do it.

Also, once I add the db access class, there are my.com.tenancy classes and
org.hibernate classes that get flagged as class not found.

I can add them to the repo, but since I don't access them directly, I
guessed that I wouldn't have to put them there and only in the ./lib

Can anyone elaborate on this or share a good link?

Thanks!





--
View this message in context: http://drools.46999.n3.nabble.com/6-0-1-F-Artifact-Repository-vs-container-lib-dir-tp4028240.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users