August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10958) Fix verifier and docs version

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFLY-10958?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-10958: -------------------------------- Summary: Fix verifier and docs version (was: Fix verifier version) > Fix verifier and docs version > ----------------------------- > > Key: WFLY-10958 > URL: https://issues.jboss.org/browse/WFLY-10958 > Project: WildFly > Issue Type: Task > Reporter: Yeray Borges > Assignee: Yeray Borges > > It was left over changing the verifier version after the final release. After each new release the product.docs.server.version and verifier.product.release.version properties should be changed as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10959) Update product.release.version to 15.0

by Marek Kopecký (JIRA)

Marek Kopecký created WFLY-10959: ------------------------------------ Summary: Update product.release.version to 15.0 Key: WFLY-10959 URL: https://issues.jboss.org/browse/WFLY-10959 Project: WildFly Issue Type: Bug Reporter: Marek Kopecký Assignee: Marek Kopecký Priority: Blocker Update product.release.version to 15.0 WF can't be built without this change: {noformat} [INFO] ------------------------------------------------------------------------ [INFO] Building WildFly: Distribution 15.0.0.Alpha1-SNAPSHOT [INFO] ------------------------------------------------------------------------ .... [error] [Verifier] File [/home/mkopecky/git/base/dist/target/wildfly-15.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/as/product/wildfly-full/dir/META-INF/MANIFEST.MF] does not match regexp [JBoss-Product-Release-Version: 14.0] {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10958) Fix verifier version

by Yeray Borges (JIRA)

Yeray Borges created WFLY-10958: ----------------------------------- Summary: Fix verifier version Key: WFLY-10958 URL: https://issues.jboss.org/browse/WFLY-10958 Project: WildFly Issue Type: Task Reporter: Yeray Borges Assignee: Yeray Borges It was left over changing the verifier version after the final release. After each new release the product.docs.server.version and verifier.product.release.version properties should be changed as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2549?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-2549. ------------------------------------ Resolution: Done > [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase > ------------------------------------------------------------------- > > Key: DROOLS-2549 > URL: https://issues.jboss.org/browse/DROOLS-2549 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Fix For: 7.11.0.Final > > > {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes. > At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}). > Changes required for this JIRA (split into sub-tasks when work starts):- > * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller (/) > * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children (/) > * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/) > * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}} (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10784) WeldStartCompletionService failed when optional components not installed

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin... ] Matej Novotny updated WFLY-10784: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/11481, https://github.com/wildfly/wildfly/pull/11625 (was: https://github.com/wildfly/wildfly/pull/11481) > WeldStartCompletionService failed when optional components not installed > ------------------------------------------------------------------------ > > Key: WFLY-10784 > URL: https://issues.jboss.org/browse/WFLY-10784 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 12.0.0.Final, 13.0.0.Final > Reporter: Alexander Kudrevatykh > Assignee: Matej Novotny > Attachments: arq-test.tar.xz > > > WebComponents are optional and fail in initialising it not causes fail of deployment, but when starting EAR application with included WAR fail in deployment since Wildfly 12 because WeldStartCompletionService depends on all components regardless of their type -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2943) DMN DecisionServiceCompiler not correctly wired for DMNv1.2 format

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2943: -------------------------------------- Summary: DMN DecisionServiceCompiler not correctly wired for DMNv1.2 format Key: DROOLS-2943 URL: https://issues.jboss.org/browse/DROOLS-2943 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-267) ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes

by Shigeru Chiba (JIRA)

[ https://issues.jboss.org/browse/JASSIST-267?page=com.atlassian.jira.plugi... ] Shigeru Chiba closed JASSIST-267. --------------------------------- > ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes > ------------------------------------------------------------------------------------------------------------ > > Key: JASSIST-267 > URL: https://issues.jboss.org/browse/JASSIST-267 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.21.0-GA, 3.22.0-CR1 > Environment: Linux/Windows 7, Java 1.7 and 1.8 > Reporter: Ning Zhang > Assignee: Shigeru Chiba > Priority: Critical > Attachments: IssueMethodsHaveSameNameInParent.java > > > As in the attachment, if there are multiple methods in non-public parent class,then the MethodHandler will not take effect. > If use 3.12.0-GA, this issue will be gone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-267) ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes

by Shigeru Chiba (JIRA)

[ https://issues.jboss.org/browse/JASSIST-267?page=com.atlassian.jira.plugi... ] Shigeru Chiba resolved JASSIST-267. ----------------------------------- Resolution: Done > ProxyFactory will not invoke MethodHandler on methods having same name declared in non-public parent classes > ------------------------------------------------------------------------------------------------------------ > > Key: JASSIST-267 > URL: https://issues.jboss.org/browse/JASSIST-267 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.21.0-GA, 3.22.0-CR1 > Environment: Linux/Windows 7, Java 1.7 and 1.8 > Reporter: Ning Zhang > Assignee: Shigeru Chiba > Priority: Critical > Attachments: IssueMethodsHaveSameNameInParent.java > > > As in the attachment, if there are multiple methods in non-public parent class,then the MethodHandler will not take effect. > If use 3.12.0-GA, this issue will be gone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1383) Dependency of ironjacamar-spec-api should be in provided scope

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1383?page=com.atlassian.jira.plugin... ] Lin Gao commented on JBJCA-1383: -------------------------------- PR: https://github.com/ironjacamar/ironjacamar/pull/675 > Dependency of ironjacamar-spec-api should be in provided scope > -------------------------------------------------------------- > > Key: JBJCA-1383 > URL: https://issues.jboss.org/browse/JBJCA-1383 > Project: IronJacamar > Issue Type: Bug > Components: Build > Reporter: Lin Gao > Assignee: Lin Gao > > Module +ironjacamar-spec-api+ is provided by application server. Like in WildFly server, so the dependency of this artifact should be in +provided+ scope. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1383) Dependency of ironjacamar-spec-api should be in provided scope

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1383?page=com.atlassian.jira.plugin... ] Lin Gao updated JBJCA-1383: --------------------------- Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/675 > Dependency of ironjacamar-spec-api should be in provided scope > -------------------------------------------------------------- > > Key: JBJCA-1383 > URL: https://issues.jboss.org/browse/JBJCA-1383 > Project: IronJacamar > Issue Type: Bug > Components: Build > Reporter: Lin Gao > Assignee: Lin Gao > > Module +ironjacamar-spec-api+ is provided by application server. Like in WildFly server, so the dependency of this artifact should be in +provided+ scope. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2018