June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10606) Remove cdi-api-bridge, support only CDI 2.0

by Matej Novotny (JIRA)

Matej Novotny created WFLY-10606: ------------------------------------ Summary: Remove cdi-api-bridge, support only CDI 2.0 Key: WFLY-10606 URL: https://issues.jboss.org/browse/WFLY-10606 Project: WildFly Issue Type: Task Components: CDI / Weld Affects Versions: 13.0.0.Final Reporter: Matej Novotny Assignee: Matej Novotny We need to remove the bridge module and possibly temper with the intergration code to take that into consideration. See previous issue for changes done to enable this - WFLY-9768. Following this change, we will also perform additional changes in Weld codebase which currently support dual CDI versioning (hence we can shake off few hacks from there). This issue may/should go hand in hand with Weld component upgrade in WFLY. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3937) Error when running configured wildfly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3937: ------------------------------------------ This is failing in a call to Files.move, which has this javadoc: {code} * When invoked to move a * directory that is not empty then the directory is moved if it does not * require moving the entries in the directory. For example, renaming a * directory on the same {@link FileStore} will usually not require moving * the entries in the directory. When moving a directory requires that its * entries be moved then this method fails (by throwing an {@code * IOException}). {code} The directory won't be empty but it's strange that there's a need to move the entries in the dir, i.e. the two paths should in the same FileStore. > Error when running configured wildfly > ------------------------------------- > > Key: WFCORE-3937 > URL: https://issues.jboss.org/browse/WFCORE-3937 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Final > Reporter: Stephen Buergler > Assignee: Jeff Mesnil > Priority: Minor > Attachments: Dockerfile > > > 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current > ... > 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot. > To reproduce: > docker build -ttesting . > docker run --rm -it testing -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10587) Re-enable CompensationScopedTestCase

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-10587?page=com.atlassian.jira.plugin... ] Petr Kremensky closed WFLY-10587. --------------------------------- Resolution: Duplicate Issue Duplicates WFLY-9937 > Re-enable CompensationScopedTestCase > ------------------------------------ > > Key: WFLY-10587 > URL: https://issues.jboss.org/browse/WFLY-10587 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Petr Kremensky > Assignee: Petr Kremensky > > org.jboss.as.test.xts.annotation.compensationScoped.CompensationScopedTestCase was ignored as intermittently failing due to WFLY-9871. Since WFLY-9871 is now resolved, the test should be re-enabled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3935) CLI, revisit modular context detection

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3935?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3935: ----------------------------------------- Description: It seems that we could get rid-off loading and initialisation of JBoss org.jboss.modules.Module class when the CLI introspect its execution context. Doing so some complexity will go away. (was: It seems that we could get rid-off loading and initialize JBoss org.jboss.modules.Module class when the CLI introspect its execution context. Doing so some complexity will go away.) > CLI, revisit modular context detection > -------------------------------------- > > Key: WFCORE-3935 > URL: https://issues.jboss.org/browse/WFCORE-3935 > Project: WildFly Core > Issue Type: Task > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > It seems that we could get rid-off loading and initialisation of JBoss org.jboss.modules.Module class when the CLI introspect its execution context. Doing so some complexity will go away. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3937) Error when running configured wildfly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3937: ---------------------------------------- Component/s: Management Assignee: Jeff Mesnil (was: Jason Greene) > Error when running configured wildfly > ------------------------------------- > > Key: WFCORE-3937 > URL: https://issues.jboss.org/browse/WFCORE-3937 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Final > Reporter: Stephen Buergler > Assignee: Jeff Mesnil > Priority: Minor > Attachments: Dockerfile > > > 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current > ... > 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot. > To reproduce: > docker build -ttesting . > docker run --rm -it testing -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3937) Error when running configured wildfly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3937?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-10605 to WFCORE-3937: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3937 (was: WFLY-10605) Affects Version/s: 5.0.0.Final (was: 13.0.0.Final) > Error when running configured wildfly > ------------------------------------- > > Key: WFCORE-3937 > URL: https://issues.jboss.org/browse/WFCORE-3937 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 5.0.0.Final > Reporter: Stephen Buergler > Assignee: Jason Greene > Priority: Minor > Attachments: Dockerfile > > > 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current > ... > 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot. > To reproduce: > docker build -ttesting . > docker run --rm -it testing -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10585) BanTransitiveDependencies enforcer violations while building wildfly-galleon-pack module on IBM jdk

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-10585?page=com.atlassian.jira.plugin... ] Alessio Soldano reassigned WFLY-10585: -------------------------------------- Assignee: R Searls (was: Alessio Soldano) > BanTransitiveDependencies enforcer violations while building wildfly-galleon-pack module on IBM jdk > --------------------------------------------------------------------------------------------------- > > Key: WFLY-10585 > URL: https://issues.jboss.org/browse/WFLY-10585 > Project: WildFly > Issue Type: Bug > Components: Build System, Web Services > Reporter: Petr Kremensky > Assignee: R Searls > > Building WildFly: Full Galleon Pack using IBM jdk fails with enforcer BanTransitiveDependencies violation. > *reproduce* > {noformat} > wildfly] $ mvn package -pl galleon-pack > ... > [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (ban-transitive-deps) @ wildfly-galleon-pack --- > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message: > org.wildfly:wildfly-galleon-pack:pom:14.0.0.Beta1-SNAPSHOT > org.apache.cxf:cxf-rt-features-logging:jar:3.2.4-jbossorg-1:compile has transitive dependencies: > xalan:xalan:jar:2.7.1.jbossorg-4:compile > xalan:serializer:jar:2.7.1.jbossorg-4:compile > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 21.949 s > [INFO] Finished at: 2018-06-18T13:30:17+02:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (ban-transitive-deps) on project wildfly-galleon-pack: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1] > {noformat} > *workaround* > Skip enforcer by adding {{-Denforcer.skip=true}} property > *environment* > {noformat} > $ mvn -version > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00) > Maven home: /usr/lib/maven > Java version: 1.8.0_171, vendor: IBM Corporation > Java home: /usr/lib/java/ibm-java-8.0-5.16/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.16.15-300.fc28.x86_64", arch: "amd64", family: "unix" > $ git rev-parse --short HEAD > 4eff06230b > {noformat} > *ibm jdk download* > https://developer.ibm.com/javasdk/downloads/sdk8/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10605) Error when running configured wildfly

by Stephen Buergler (JIRA)

Stephen Buergler created WFLY-10605: --------------------------------------- Summary: Error when running configured wildfly Key: WFLY-10605 URL: https://issues.jboss.org/browse/WFLY-10605 Project: WildFly Issue Type: Bug Affects Versions: 13.0.0.Final Reporter: Stephen Buergler Assignee: Jason Greene Priority: Minor Attachments: Dockerfile 08:32:20,676 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0056: Could not rename /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current to /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/20180619-083220673: java.nio.file.DirectoryNotEmptyException: /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current ... 08:50:08,531 WARN [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0414: Could not create a timestamped backup of current history dir /opt/jboss/wildfly/standalone/configuration/standalone_xml_history/current, so it may still include versions from the previous boot. To reproduce: docker build -ttesting . docker run --rm -it testing -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3936) classfilewriter 1.2.3.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFCORE-3936: -------------------------------------- Summary: classfilewriter 1.2.3.Final Key: WFCORE-3936 URL: https://issues.jboss.org/browse/WFCORE-3936 Project: WildFly Core Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3935) CLI, revisit modular context detection

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-3935: -------------------------------------------- Summary: CLI, revisit modular context detection Key: WFCORE-3935 URL: https://issues.jboss.org/browse/WFCORE-3935 Project: WildFly Core Issue Type: Task Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise It seems that we could get rid-off loading and initialize JBoss org.jboss.modules.Module class when the CLI introspect its execution context. Doing so some complexity will go away. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 June 2018