Bug 988752 - Remove bpm_console deps from droolsjbpm-parent
Summary: Remove bpm_console deps from droolsjbpm-parent
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: BRE
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER2
: 6.0.0
Assignee: Geoffrey De Smet
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-26 09:54 UTC by Ryan Zhang
Modified: 2014-08-06 20:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:18:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ryan Zhang 2013-07-26 09:54:43 UTC
Description of problem:
There should be no dependencies on org.jboss.bpm artifacts. 
So probably we could remove them from droolsjbpm-parent pom.

Already talked to Maciej, so assigned directly to Maciej.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Geoffrey De Smet 2013-08-02 08:50:22 UTC
Fixed on master
and on 6.0.x:
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/commit/568d0cef2a725ffa6c6823616edb0dada09fe2d5

for community 6.0.0.CR2

Comment 3 Geoffrey De Smet 2013-08-02 08:54:10 UTC
@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).

Comment 4 Ryan Zhang 2013-08-02 11:03:06 UTC
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).

Comment 9 Lukáš Petrovický 2014-02-07 16:15:11 UTC
This BZ has been part of the 6.0.0 stream.


Note You need to log in before you can comment on or make changes to this bug.