January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2268) Add more fine-grained control on all assets

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2268?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2268: ---------------------------------------- [~rbourner] Ah, my mistake, you're after permissions per file. [~porcelli] Thoughts? > Add more fine-grained control on all assets > ------------------------------------------- > > Key: DROOLS-2268 > URL: https://issues.jboss.org/browse/DROOLS-2268 > Project: Drools > Issue Type: Enhancement > Components: Artifact Repository > Affects Versions: 6.5.0.Final > Reporter: Richard Bourner > Assignee: Michael Anstis > Priority: Minor > > Currently, permissions within Business Central are only at projects level. > It would be interesting to be able to enable permissions at a more fine-grained level. > For instance, in a single project of one repository, having some people with read-only access on some assets, and other people have read/write access to the same assets. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2268) Add more fine-grained control on all assets

by Richard Bourner (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2268?page=com.atlassian.jira.plugi... ] Richard Bourner commented on DROOLS-2268: ----------------------------------------- My understanding is that you can indeed assign permissions to roles/groups (using the kie-cli with V6 or the UI in V7) but only at project level, not at rules (or other assets) level. > Add more fine-grained control on all assets > ------------------------------------------- > > Key: DROOLS-2268 > URL: https://issues.jboss.org/browse/DROOLS-2268 > Project: Drools > Issue Type: Enhancement > Components: Artifact Repository > Affects Versions: 6.5.0.Final > Reporter: Richard Bourner > Assignee: Michael Anstis > Priority: Minor > > Currently, permissions within Business Central are only at projects level. > It would be interesting to be able to enable permissions at a more fine-grained level. > For instance, in a single project of one repository, having some people with read-only access on some assets, and other people have read/write access to the same assets. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2266) [DMN Designer] Override newSizeHandler for DMNSVGShapeDefImpl

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2266?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2266: ----------------------------------- Sprint: 2018 Week 03-04 > [DMN Designer] Override newSizeHandler for DMNSVGShapeDefImpl > ------------------------------------------------------------- > > Key: DROOLS-2266 > URL: https://issues.jboss.org/browse/DROOLS-2266 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > > Due to changes in JBPM-6512, we should override the _newSizeHandler_ in the class [DMNSVGShapeDefImpl.java|https://github.com/kiegroup/kie-wb-common/blob/ma...] to introduce the same approach in min/max size constraint handling through Stunner, DMN and Forms. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2268) Add more fine-grained control on all assets

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2268?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2268: ---------------------------------------- [~rbourner] I thought you could also assign permissions to roles/groups (of Users)? [~davidredhat] This is true is it not? > Add more fine-grained control on all assets > ------------------------------------------- > > Key: DROOLS-2268 > URL: https://issues.jboss.org/browse/DROOLS-2268 > Project: Drools > Issue Type: Enhancement > Components: Artifact Repository > Affects Versions: 6.5.0.Final > Reporter: Richard Bourner > Assignee: Michael Anstis > Priority: Minor > > Currently, permissions within Business Central are only at projects level. > It would be interesting to be able to enable permissions at a more fine-grained level. > For instance, in a single project of one repository, having some people with read-only access on some assets, and other people have read/write access to the same assets. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2268) Add more fine-grained control on all assets

by Richard Bourner (JIRA)

Richard Bourner created DROOLS-2268: --------------------------------------- Summary: Add more fine-grained control on all assets Key: DROOLS-2268 URL: https://issues.jboss.org/browse/DROOLS-2268 Project: Drools Issue Type: Enhancement Components: Artifact Repository Affects Versions: 6.5.0.Final Reporter: Richard Bourner Assignee: Michael Anstis Priority: Minor Currently, permissions within Business Central are only at projects level. It would be interesting to be able to enable permissions at a more fine-grained level. For instance, in a single project of one repository, having some people with read-only access on some assets, and other people have read/write access to the same assets. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2267) Scope of enumeration

by Richard Bourner (JIRA)

Richard Bourner created DROOLS-2267: --------------------------------------- Summary: Scope of enumeration Key: DROOLS-2267 URL: https://issues.jboss.org/browse/DROOLS-2267 Project: Drools Issue Type: Enhancement Components: decision tables, Enumerations Editor Affects Versions: 6.5.0.Final Environment: Business Central / BRMS 6 Reporter: Richard Bourner Assignee: Mario Fusco Priority: Minor Currently the scope of an enumeration file is per package. It would be nice to expand the scope in order to avoir duplicating all enumerations in each package of one project. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2244) Use of TP.internal_pool can result in classloader leaks

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2244?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2244. ---------------------------- Resolution: Done Added methods to get and set both the internal pool itself and the associated thread pool factory. You may want to use {{setInternalThreadPool()}} directly... > Use of TP.internal_pool can result in classloader leaks > ------------------------------------------------------- > > Key: JGRP-2244 > URL: https://issues.jboss.org/browse/JGRP-2244 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0 > Reporter: Paul Ferraro > Assignee: Bela Ban > Fix For: 4.0.10 > > > As of JGroups 4.0, the ThreadFactory of the internal thread pool cannot be overridden. Consequently, there is no mechanism to associate newly spawned threads with a specific classloader. If an application thread results in the spawning of an thread in this internal pool [1], the application class loader can leak to other threads used the the JGroups channel. > [1] https://github.com/belaban/JGroups/blob/master/src/org/jgroups/protocols/... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9726) Upgrade JSF based on Mojarra 2.2.13.SP5

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9726?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated WFLY-9726: -------------------------------- Description: Upgrade JSF based on Mojarra 2.2.13.SP. This incorporates the patch for WFLY-8573 / [JAVASERVERFACES_SPEC_PUBLIC-671 | https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-671] (was: Upgrade JSF based on Mojarra 2.2.13.SP4. This incorporates the patch for JBEAP-10758/[JAVASERVERFACES-4240 | https://java.net/jira/browse/JAVASERVERFACES-4240]) > Upgrade JSF based on Mojarra 2.2.13.SP5 > --------------------------------------- > > Key: WFLY-9726 > URL: https://issues.jboss.org/browse/WFLY-9726 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Ivo Studensky > Assignee: Bartosz Spyrko-Śmietanko > > Upgrade JSF based on Mojarra 2.2.13.SP. This incorporates the patch for WFLY-8573 / [JAVASERVERFACES_SPEC_PUBLIC-671 | https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-671] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-33) Support non-jar artifacts properly

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-33?page=com.atlassian.jira.plugin... ] Peter Palaga commented on WFBUILD-33: ------------------------------------- Work in progress https://github.com/ppalaga/wildfly-build-tools/commits/WFBUILD-33 > Support non-jar artifacts properly > ---------------------------------- > > Key: WFBUILD-33 > URL: https://issues.jboss.org/browse/WFBUILD-33 > Project: WildFly Build Tools > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Peter Palaga > > The immediate impetus for reporting this is the fact that after upgrading from 1.1.6.Final to 1.2.6.Final our > {code} > <copy-artifact artifact="io.hawt:hawtio-wildfly" to-location="standalone/deployments/"/> > {code} > stopped working for the FP plugin. Changing it to > {code}<copy-artifact artifact="io.hawt:hawtio-wildfly:war" to-location="standalone/deployments/"/>{code} > by adding :war made the FP plugin happy, but it made the provisioning plugin fail with an NPE. > It looks like the code parsing and the rendering the groupId:artifactId:type:classifier:version strings is scattered over several methods whose behavior is not 100% consistent. > The current objective is: > (1) Write a few integration tests to pin the behavior before the change, identifying the broken cases > (2) Write the actual fix in such a way that the plugins stay as backwards compatible as possible. > I have a fix that works for me, I just need to ensure, my changes keep the plugins backwards compatible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9726) Upgrade JSF based on Mojarra 2.2.13.SP5

by Ivo Studensky (JIRA)

Ivo Studensky created WFLY-9726: ----------------------------------- Summary: Upgrade JSF based on Mojarra 2.2.13.SP5 Key: WFLY-9726 URL: https://issues.jboss.org/browse/WFLY-9726 Project: WildFly Issue Type: Component Upgrade Components: JSF Reporter: Ivo Studensky Assignee: Bartosz Spyrko-Śmietanko Fix For: 11.0.0.Beta1 Upgrade JSF based on Mojarra 2.2.13.SP4. This incorporates the patch for JBEAP-10758/[JAVASERVERFACES-4240 | https://java.net/jira/browse/JAVASERVERFACES-4240] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2018