Bug 988752
Summary: | Remove bpm_console deps from droolsjbpm-parent | ||
---|---|---|---|
Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Ryan Zhang <rzhang> |
Component: | BRE | Assignee: | Geoffrey De Smet <gdesmet> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Lukáš Petrovický <lpetrovi> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0 | CC: | gdesmet |
Target Milestone: | ER2 | ||
Target Release: | 6.0.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-06 20:18:26 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: |
Description
Ryan Zhang
2013-07-26 09:54:43 UTC
Fixed on master and on 6.0.x: https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/commit/568d0cef2a725ffa6c6823616edb0dada09fe2d5 for community 6.0.0.CR2 @Ryan Can you check the target milestone? Bugzilla forced me to fill in something, so I filled in CR2 - but that's wrong if it's asking for the BRMS release version actually (which can only be defined going from modified->on_QA, not from assigned->modified because productization might actually start building a release at the same time as I am fixing an issue). Yep, you are correct. I will update the milestone to ER1 after I release the next version. Thanks for checking, Geffrey. (In reply to Geoffrey De Smet from comment #3) > @Ryan Can you check the target milestone? Bugzilla forced me to fill in > something, so I filled in CR2 - but that's wrong if it's asking for the BRMS > release version actually (which can only be defined going from > modified->on_QA, not from assigned->modified because productization might > actually start building a release at the same time as I am fixing an issue). This BZ has been part of the 6.0.0 stream. |