Bug 1100187
| Summary: | business-central fails to build a project which depends on org.springframework:spring-jdbc and com.sun.xml.bind:jaxb-xjc | ||
|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Toshiya Kobayashi <tkobayas> |
| Component: | Business Central | Assignee: | Mario Fusco <mfusco> |
| Status: | CLOSED EOL | QA Contact: | Ivo Bek <ibek> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.1 | CC: | alazarot, ibek, kverlaen, mfusco, mwinkler, rzhang |
| Target Milestone: | ER1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-27 20:11:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1115479, 1115481 | ||
|
Description
Toshiya Kobayashi
2014-05-22 08:13:53 UTC
Cherry-picked to 6.0.x branch with https://github.com/droolsjbpm/guvnor/commit/a791d57af Verification failed in BPMS 6.0.3.ER1 When I use just the spring-jdbc dependency I will get the following exception as WARN: 14:38:58,894 WARN [org.guvnor.common.services.builder.Builder] (EJB default - 4) Verification of class org.apache.derby.client.am.Connection failed and will not be available for authoring. Please check the necessary external dependencies for this project are configured correctly.: java.lang.SecurityException: sealing violation: package org.apache.derby.jdbc is sealed However, the build fails. From the description of the BZ that should not happen. The build also fails when I try to build a project containing spring-jdbc and jaxb-xjc dependencies. The project only with the jaxb-xjc dependency is built successfully. Thanks Mario. I have one idea what it could cause it, hence I will try it today. Verified in BPMS 6.0.3.ER1. |