April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-249) Upgrade byteman from 4.0.4 to 4.0.6

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-249?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-249: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/244, https://github.com/jboss-logging/jboss-logmanager/pull/247, https://github.com/jboss-logging/jboss-logmanager/pull/248 (was: https://github.com/jboss-logging/jboss-logmanager/pull/244, https://github.com/jboss-logging/jboss-logmanager/pull/247) > Upgrade byteman from 4.0.4 to 4.0.6 > ----------------------------------- > > Key: LOGMGR-249 > URL: https://issues.jboss.org/browse/LOGMGR-249 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.1.9.Final, 2.2.0.Final, 3.0.0.Final > > > Upgrade byteman 4.0.4 to 4.0.6 which is used for tests only. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-251) Upgrade wildfly-common from 1.2.0.Final to 1.5.1.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-251?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-251: --------------------------------- Fix Version/s: 2.2.0.Final 3.0.0.Final 2.1.10.Final > Upgrade wildfly-common from 1.2.0.Final to 1.5.1.Final > ------------------------------------------------------ > > Key: LOGMGR-251 > URL: https://issues.jboss.org/browse/LOGMGR-251 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.1.10.Final, 2.2.0.Final, 3.0.0.Final > > > Upgrade {{org.wildfly.common:wildfly-common}} from 1.2.0.Final to 1.5.1.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-251) Upgrade wildfly-common from 1.2.0.Final to 1.5.1.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-251?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-251: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/246, https://github.com/jboss-logging/jboss-logmanager/pull/247, https://github.com/jboss-logging/jboss-logmanager/pull/248 (was: https://github.com/jboss-logging/jboss-logmanager/pull/246, https://github.com/jboss-logging/jboss-logmanager/pull/247) > Upgrade wildfly-common from 1.2.0.Final to 1.5.1.Final > ------------------------------------------------------ > > Key: LOGMGR-251 > URL: https://issues.jboss.org/browse/LOGMGR-251 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.1.10.Final, 2.2.0.Final, 3.0.0.Final > > > Upgrade {{org.wildfly.common:wildfly-common}} from 1.2.0.Final to 1.5.1.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-252) Upgrade jboss-logging form 3.3.2.Final to 3.4.0.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-252?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-252: --------------------------------- Fix Version/s: 3.0.0.Final > Upgrade jboss-logging form 3.3.2.Final to 3.4.0.Final > ----------------------------------------------------- > > Key: LOGMGR-252 > URL: https://issues.jboss.org/browse/LOGMGR-252 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 3.0.0.Final > > > Upgrade {{org.jboss.logging:jboss-logging}} from 3.3.2.Final to 3.4.0.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-248) Upgrade jboss-modules from 1.7.0.Final to 1.9.0.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-248?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-248: --------------------------------- Fix Version/s: 2.2.0.Final 3.0.0.Final > Upgrade jboss-modules from 1.7.0.Final to 1.9.0.Final > ----------------------------------------------------- > > Key: LOGMGR-248 > URL: https://issues.jboss.org/browse/LOGMGR-248 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.1.9.Final, 2.2.0.Final, 3.0.0.Final > > > Upgrade {{org.jboss.modules:jboss-modules}} from 1.7.0.Final to 1.9.0.Final. This kind of upgrade is not usually done in a micro release, however this should be safe. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-248) Upgrade jboss-modules from 1.7.0.Final to 1.9.0.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-248?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-248: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/244, https://github.com/jboss-logging/jboss-logmanager/pull/247, https://github.com/jboss-logging/jboss-logmanager/pull/248 (was: https://github.com/jboss-logging/jboss-logmanager/pull/244, https://github.com/jboss-logging/jboss-logmanager/pull/247) > Upgrade jboss-modules from 1.7.0.Final to 1.9.0.Final > ----------------------------------------------------- > > Key: LOGMGR-248 > URL: https://issues.jboss.org/browse/LOGMGR-248 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 2.1.9.Final, 2.2.0.Final, 3.0.0.Final > > > Upgrade {{org.jboss.modules:jboss-modules}} from 1.7.0.Final to 1.9.0.Final. This kind of upgrade is not usually done in a micro release, however this should be safe. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-252) Upgrade jboss-logging form 3.3.2.Final to 3.4.0.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-252?page=com.atlassian.jira.plugin... ] James Perkins moved WFCORE-4427 to LOGMGR-252: ---------------------------------------------- Project: JBoss Log Manager (was: WildFly Core) Key: LOGMGR-252 (was: WFCORE-4427) > Upgrade jboss-logging form 3.3.2.Final to 3.4.0.Final > ----------------------------------------------------- > > Key: LOGMGR-252 > URL: https://issues.jboss.org/browse/LOGMGR-252 > Project: JBoss Log Manager > Issue Type: Component Upgrade > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Upgrade {{org.jboss.logging:jboss-logging}} from 3.3.2.Final to 3.4.0.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4427) Upgrade jboss-logging form 3.3.2.Final to 3.4.0.Final

by James Perkins (Jira)

James Perkins created WFCORE-4427: ------------------------------------- Summary: Upgrade jboss-logging form 3.3.2.Final to 3.4.0.Final Key: WFCORE-4427 URL: https://issues.jboss.org/browse/WFCORE-4427 Project: WildFly Core Issue Type: Component Upgrade Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.logging:jboss-logging}} from 3.3.2.Final to 3.4.0.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3841) [DMN Designer] Included Models - An error is raised when a DMN file with imports is saved

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3841?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3841: ---------------------------------------- This is an issue relating to _incremental builds_. If I create a DMN file that imports another and save it the reported compilation issue is indeed observed. If however I subsequentially perform a full build it is successful and no errors are evident. > [DMN Designer] Included Models - An error is raised when a DMN file with imports is saved > ----------------------------------------------------------------------------------------- > > Key: DROOLS-3841 > URL: https://issues.jboss.org/browse/DROOLS-3841 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.20.0.Final > Reporter: Guilherme Gomes > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > An error is raised when a DMN file with imports is saved > *Steps to reproduce:* Create two empty dmn models (a.dmn, b.dmn). Then in one of them include the other one and click save button of the dmn editor. The following error will appear in the server log. > *Error:* > {code} > 13:32:05,601 ERROR [org.kie.dmn.core.compiler.DMNCompilerImpl] (EJB default - 9) Required import not found: Could not locate required dependency while importing DMN for namespace: https://github.com/kiegroup/drools/kie-dmn/_0C5353A4-0B49-4D1B-A22B-24C60..., name: first, modelName: null. for node 'org.kie.dmn.model.v1_2.TImport@268ce829' > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4426) Upgrade wildfly-common from 1.5.0.Final to 1.5.1.Final

by James Perkins (Jira)

James Perkins created WFCORE-4426: ------------------------------------- Summary: Upgrade wildfly-common from 1.5.0.Final to 1.5.1.Final Key: WFCORE-4426 URL: https://issues.jboss.org/browse/WFCORE-4426 Project: WildFly Core Issue Type: Component Upgrade Components: Server Reporter: James Perkins Assignee: James Perkins Upgrade {{org.wildfly.common:wildfly-common}} from 1.5.0.Final to 1.5.1.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 April 2019