January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-4959: -------------------------------------- [~nicktsek] I could use some additional information about where the project was opened and how it was moved in that tool? > Package name does not changes on copying of an existing package > --------------------------------------------------------------- > > Key: DROOLS-4959 > URL: https://issues.redhat.com/browse/DROOLS-4959 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > > After copying a package to a new one, all copied resources will remain referencing the existing one. > This becomes a bigger issue once you use guided rules, which their source cannot be edited. > Due to that, duplication alerts will be raised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4961) User / Role Permissions on package level

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4961?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-4961: -------------------------------------- [~nicktsek] The best way to do this at the moment is to use seperate projects for what would be in these packages. > User / Role Permissions on package level > ---------------------------------------- > > Key: DROOLS-4961 > URL: https://issues.redhat.com/browse/DROOLS-4961 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: David Gutierrez > Priority: Major > Labels: drools-tools > > It will be amazingly helpful to have the ability to minimize the access / permissions of a user / group on package level. > Within a project you can define several packages - for different purposes - and you need each team to be able to work on / view a specific package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4960) Reference a data object from one project to another one.

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4960?page=com.atlassian.jira.plug... ] Toni Rikkola resolved DROOLS-4960. ---------------------------------- Resolution: Explained I'll close this. Since the projects in workbench are actually Maven projects that can have each other as a dependency like Michael Anstis mentioned. > Reference a data object from one project to another one. > -------------------------------------------------------- > > Key: DROOLS-4960 > URL: https://issues.redhat.com/browse/DROOLS-4960 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Currently, nothing can be referenced from one project to another one. > Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful. > Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4809) Allow composite operation to read the model without need to acquired the write lock in domain mode

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4809?page=com.atlassian.jira.plug... ] Yeray Borges updated WFCORE-4809: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4064 > Allow composite operation to read the model without need to acquired the write lock in domain mode > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-4809 > URL: https://issues.redhat.com/browse/WFCORE-4809 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > > Currently, the web console is highly affected by the write lock acquisition. Most of the read operations done by the web console are translated into composite operations, that under some circumstances (target to a single host, non-wildcards..), require the DC write lock. This write lock acquisition has a huge impact on the web console since each operation is queued until the lock is released. > As an example, if we have a deployment that takes some minutes in the middle the user is clicking to see the server status, soon the web console gets unresponsible. > This issue tries to reduce the write lock acquisition in these cases and allow read operations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1924) EntityTest Failing on OpenJ9

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1924: ------------------------------------- Summary: EntityTest Failing on OpenJ9 Key: ELY-1924 URL: https://issues.redhat.com/browse/ELY-1924 Project: WildFly Elytron Issue Type: Bug Components: Testsuite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.11.1.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-4959: ---------------------------------------- [~Rikkola] I'd be tempted to punt to the _core_ team.. this is not a {{drools-tooling}} specific requirement... The _mechanism_ is already available (IIRC {{CopyHelper}} and {{RenameHelper}} interfaces)... > Package name does not changes on copying of an existing package > --------------------------------------------------------------- > > Key: DROOLS-4959 > URL: https://issues.redhat.com/browse/DROOLS-4959 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > After copying a package to a new one, all copied resources will remain referencing the existing one. > This becomes a bigger issue once you use guided rules, which their source cannot be edited. > Due to that, duplication alerts will be raised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4960) Reference a data object from one project to another one.

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4960?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-4960: ---------------------------------------- You should create one project containing the DO's etc you want to share and then add it as a dependency to the other project. > Reference a data object from one project to another one. > -------------------------------------------------------- > > Key: DROOLS-4960 > URL: https://issues.redhat.com/browse/DROOLS-4960 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Currently, nothing can be referenced from one project to another one. > Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful. > Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4961) User / Role Permissions on package level

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4961?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-4961: -------------------------------------- Assignee: David Gutierrez (was: Toni Rikkola) > User / Role Permissions on package level > ---------------------------------------- > > Key: DROOLS-4961 > URL: https://issues.redhat.com/browse/DROOLS-4961 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: David Gutierrez > Priority: Major > Labels: drools-tools > > It will be amazingly helpful to have the ability to minimize the access / permissions of a user / group on package level. > Within a project you can define several packages - for different purposes - and you need each team to be able to work on / view a specific package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4966) [DMN Designer] Dragging a field at the bottom of type designer

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4966: -------------------------------------- Summary: [DMN Designer] Dragging a field at the bottom of type designer Key: DROOLS-4966 URL: https://issues.redhat.com/browse/DROOLS-4966 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.32.0.Final Reporter: Edoardo Vacchi Assignee: Michael Anstis Attachments: drag-2.gif - add several fields/structures so that the list exceeds the viewport - scroll down to the bottom of the editor - try dragging the bottom field - the view does not scroll, but the field will jump "up" at seemingly random positions at the top it's nearly impossible to reorder a field when it's at the bottom -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4964) [DMN Designer] Type designer scrolls up to the top when any element of the table is clicked

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4964?page=com.atlassian.jira.plug... ] Edoardo Vacchi updated DROOLS-4964: ----------------------------------- Affects Version/s: 7.32.0.Final > [DMN Designer] Type designer scrolls up to the top when any element of the table is clicked > ------------------------------------------------------------------------------------------- > > Key: DROOLS-4964 > URL: https://issues.redhat.com/browse/DROOLS-4964 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Edoardo Vacchi > Assignee: Michael Anstis > Priority: Major > Attachments: scroll-up.gif > > > - scroll down > - click on a non-active part of the table (i.e. not a button) > result: the viewport scrolls up to the top > !scroll-up.gif! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 2020