Bug 1008503 - Mandatory group for new repositories - inconsistency
Summary: Mandatory group for new repositories - inconsistency
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ER5
: 6.0.0
Assignee: Alexandre Porcelli
QA Contact: Tomas David
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-16 13:41 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:08 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Zuzana Krejčová 2013-09-16 13:41:17 UTC 
Description of problem:
Group is only mandatory for new or cloned repositories, if there is some group. If there is no group, it isn't needed.

We should either require the group all the time, or it should never be mandatory.
Comment 1 manstis 2013-09-20 07:50:08 UTC 
@Alexandre, IIRC you were changing how the "mandatory" logic worked by adding a flag (instead of checking whether there were any Groups?)
Comment 5 Alexandre Porcelli 2013-10-25 19:14:53 UTC 
Issue fixed on Uberfire master and 0.3.x branches:

https://github.com/droolsjbpm/uberfire/commit/f457588f1
https://github.com/droolsjbpm/uberfire/commit/0c7c1fe5b
Comment 6 Tomas David 2013-12-13 15:04:42 UTC 
Verified on BPMS 6.0.0.ER5.
Note You need to log in before you can comment on or make changes to this bug.