| Summary: | bpm-service tests fails due to KIE using Maven | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Jiri Pechanec <jpechane> |
| Component: | Rules / jBPM integration | Assignee: | David Ward <dward> |
| Status: | ON_QA --- | QA Contact: | Matej Melko <mmelko> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | atangrin, ldimaggi, soa-p-jira |
| Target Milestone: | DR1 | ||
| Target Release: | 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
If you try to build the bpm-service quickstart, you will encounter an java.lang.ExceptionInInitializerError. To work around this, add the Red Hat JBoss Fuse Service Works Maven repository as a profile in your settings.xml file. This profile must contain the following setting:
<programlisting><![CDATA[
<activeByDefault>true</activeByDefault>
]]></programlisting>
For more information about this issue, please refer to the section entitled "About the Maven Setting File" in the Red Hat JBoss BRMS 6 Development Guide.
|
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: | |
| Bug Depends On: | |||
| Bug Blocks: | 1043497 | ||
|
Description
Jiri Pechanec
2013-12-20 11:42:04 UTC
David - this is actually an issue with the Maven environment during test and not at runtime, so the kie-ci module and Maven libs are not a factor. I believe this is due to the fact that Drools only picks up the user's environment from settings.xml and does not respect the current profile as passed in via -P. Let me explain a bit more. Here are the important lines that are obscured in the long stack trace: [FATAL] Non-resolvable parent POM for org.switchyard.quickstarts:switchyard-quickstart-parent:1.1.1-p2-redhat-2: Failure to find org.switchyard:switchyard-parent:pom:1.1.1-p2-redhat-2 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced ... I get the same error if I run the project build locally with an offline repo. The settings to point to this local repo are in a profile in my settings.xml, so I will build the project with "mvn -Pfsw clean package". *However*, if i make the 'fsw' profile activeByDefault in my settings.xml instead of passing the profile from the command-line, then everything works. There's nothing we can do about this from a SY POV. We need to evaluate if/when the Drools team will address the issue of respecting profile activation via command-line. Perhaps this is already fixed and simply requires a refresh of the Drools version we include in FSW. Without that, then we are looking at documenting this as a requirement for the user to have the FSW maven repo in a profile that's active by default. Proposed doc text: When building the bpm-service quickstart, the FSW Maven repository must be contained in a profile in the user's settings.xml and that profile must be marked as <activeByDefault>true</activeByDefault>. For more information please consult section 4.2.3.5 "Settings.xml and Remote Repository Setup" in the BRMS documentation [1]. http://docs.jboss.org/drools/release/6.0.1.Final/drools-docs/html/KIEChapter.html#KIEDeployingSection NOTE TO DOCS : the above link is for community documentation. I'm not sure where this section lives in the BRMS product documentation, but we may want to link to that instead of community. |