| Summary: | Cannot load rules from maven repository | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | David Murphy <dmurphy> |
| Component: | Rules / jBPM integration | Assignee: | David Ward <dward> |
| Status: | MODIFIED --- | QA Contact: | Matej Melko <mmelko> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | aileenc, atangrin, rcernich, soa-p-jira |
| Target Milestone: | --- | ||
| Target Release: | 6.1.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
If the user attempts to import the rules-interview-container quick start and removes local DRL resources, they cannot load rules from the Maven repository. The users will instead encounter a NoClassDefFoundError.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
David Murphy
2013-12-12 14:45:29 UTC
David Ward, fyi: I ran into the same stack trace when building a part of the kie/drools/jbpm project. The solution for me, was to use maven 3.0.5 instead of maven 3.1.1. This is because of a custom plugin that we use in our build process and the fact that we use aether 1.0.x. It looks like this exception is caused because there's something depending on version later than aether 1.0.x, while the drools/jbpm (and ip-bom?) stuff uses the aether 1.0.x artifacts. I re-tested this on EAP 6.3 + SwitchYard 2.0, and it works there, as the proper maven/aether dependencies are there now. (Specifically, I changed the rules-interview-container QS to load a kjar containing the DRL from the local maven repository, vs. using what is in the QS itself.) So, the issue reported here with the EAP stack trace had been fixed. However, as noted above, trying to run the quickstart locally (JUnit test loading from local maven repository) does not work, because of the maven/aether build clashes in the local build environment. I think that's lower priority, but if it's deemed necessary to fix, a new BZ/Jira should be opened, IMO. This has worked for me as well. |