| Summary: | jbpm-test.jar should not be distributed | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Tomas Schlosser <tschloss> |
| Component: | Build Process | Assignee: | Ryan Zhang <rzhang> |
| Status: | CLOSED NOTABUG | QA Contact: | Tomas Schlosser <tschloss> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | BRMS 5.3.0.GA | CC: | brms-jira, kverlaen, lpetrovi, rzhang |
| Target Milestone: | --- | Flags: | kverlaen:
needinfo+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-05-02 09:56:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Tomas Schlosser
2012-02-22 12:18:17 UTC
This is not a test jar, this is a jar that provides utility classes to test jBPM processes. The jBPM plugin generates examples that are using this API, so excluding it from the distribution would cause issues here. Would it be possible to mark these classes as experimental, so that users know this API might still change in future versions etc.? This need to be discussed in PM meetings. This should be resolved after decision is made. This issue has been confirmed with QE and developer. The jbpm-test.jar will stay. I think this issue can be closed. |