March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6352) Build Fails with maven 3.3.9 Oracle JDK 8

by Eric Lemesre (JIRA)

[ https://issues.jboss.org/browse/WFLY-6352?page=com.atlassian.jira.plugin.... ] Eric Lemesre updated WFLY-6352: ------------------------------- Description: When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module). Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 Apache Maven 3.3.9 Maven home: /usr/share/maven Java version: 1.8.0_72, vendor: Oracle Corporation Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre Default locale: fr_FR, platform encoding: UTF-8 OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix" $ mvn clean install -PRelease .... [INFO] ------------------------------------------------------------------------ [INFO] Building WildFly: Full Feature Pack 10.0.0.Final [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack --- [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message: org.wildfly:wildfly-feature-pack:pom:10.0.0.Final dom4j:dom4j:jar:1.6.1:compile has transitive dependencies: jaxme:jaxme-api:jar:0.3:compile msv:xsdlib:jar:20030807:compile msv:relaxngDatatype:jar:20030807:compile pull-parser:pull-parser:jar:2:compile xpp3:xpp3:jar:1.1.3.3:compile was: When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module). Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 Apache Maven 3.3.9 Maven home: /usr/share/maven Java version: 1.8.0_72, vendor: Oracle Corporation Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre Default locale: fr_FR, platform encoding: UTF-8 OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix" $ mvn clean install -PRelease .... ~[INFO] ------------------------------------------------------------------------ [INFO] Building WildFly: Full Feature Pack 10.0.0.Final [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack --- [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message: org.wildfly:wildfly-feature-pack:pom:10.0.0.Final dom4j:dom4j:jar:1.6.1:compile has transitive dependencies: jaxme:jaxme-api:jar:0.3:compile msv:xsdlib:jar:20030807:compile msv:relaxngDatatype:jar:20030807:compile pull-parser:pull-parser:jar:2:compile xpp3:xpp3:jar:1.1.3.3:compile ~ > Build Fails with maven 3.3.9 Oracle JDK 8 > ------------------------------------------ > > Key: WFLY-6352 > URL: https://issues.jboss.org/browse/WFLY-6352 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 10.0.0.Final > Environment: > Reporter: Eric Lemesre > Assignee: Paul Gier > > When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module). > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 > Apache Maven 3.3.9 > Maven home: /usr/share/maven > Java version: 1.8.0_72, vendor: Oracle Corporation > Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre > Default locale: fr_FR, platform encoding: UTF-8 > OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix" > $ mvn clean install -PRelease > .... > [INFO] ------------------------------------------------------------------------ > [INFO] Building WildFly: Full Feature Pack 10.0.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack --- > [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message: > org.wildfly:wildfly-feature-pack:pom:10.0.0.Final > dom4j:dom4j:jar:1.6.1:compile has transitive dependencies: > jaxme:jaxme-api:jar:0.3:compile > msv:xsdlib:jar:20030807:compile > msv:relaxngDatatype:jar:20030807:compile > pull-parser:pull-parser:jar:2:compile > xpp3:xpp3:jar:1.1.3.3:compile -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6352) Build Fails with maven 3.3.9 Oracle JDK 8

by Eric Lemesre (JIRA)

Eric Lemesre created WFLY-6352: ---------------------------------- Summary: Build Fails with maven 3.3.9 Oracle JDK 8 Key: WFLY-6352 URL: https://issues.jboss.org/browse/WFLY-6352 Project: WildFly Issue Type: Bug Components: Build System Affects Versions: 10.0.0.Final Environment: Reporter: Eric Lemesre Assignee: Paul Gier When trying to build 10.0.0.Final with Maven 3.3.9 I get the following error from maven-enforcer plugin (at wildfly-feature-pack module). Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 Apache Maven 3.3.9 Maven home: /usr/share/maven Java version: 1.8.0_72, vendor: Oracle Corporation Java home: /usr/lib/jvm/jdk-8-oracle-x64/jre Default locale: fr_FR, platform encoding: UTF-8 OS name: "linux", version: "4.2.0-1-amd64", arch: "amd64", family: "unix" $ mvn clean install -PRelease .... ~[INFO] ------------------------------------------------------------------------ [INFO] Building WildFly: Full Feature Pack 10.0.0.Final [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-bad-dependencies) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-java-version) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (enforce-maven-version) @ wildfly-feature-pack --- [INFO] [INFO] --- maven-enforcer-plugin:1.4:enforce (ban-transitive-deps) @ wildfly-feature-pack --- [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BanTransitiveDependencies failed with message: org.wildfly:wildfly-feature-pack:pom:10.0.0.Final dom4j:dom4j:jar:1.6.1:compile has transitive dependencies: jaxme:jaxme-api:jar:0.3:compile msv:xsdlib:jar:20030807:compile msv:relaxngDatatype:jar:20030807:compile pull-parser:pull-parser:jar:2:compile xpp3:xpp3:jar:1.1.3.3:compile ~ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6333) Difficult to identify data-source with wrong credentials if multiple data-sources are defined.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6333?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6333: ----------------------------------------------- Lin Gao <lgao(a)redhat.com> changed the Status of [bug 1315439|https://bugzilla.redhat.com/show_bug.cgi?id=1315439] from ASSIGNED to MODIFIED > Difficult to identify data-source with wrong credentials if multiple data-sources are defined. > ---------------------------------------------------------------------------------------------- > > Key: WFLY-6333 > URL: https://issues.jboss.org/browse/WFLY-6333 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Affects Versions: 10.0.0.Final > Reporter: Lin Gao > Assignee: Lin Gao > > If the password for any datasource is invalid, and there are multiple datasources defined, it is difficult to identify the problematic datasource from the the console log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1420) CLI shutdown command doesn't support graceful shutdown

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1420?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1420: ------------------------------------- Fix Version/s: 2.1.0.CR2 (was: 3.0.0.Alpha1) > CLI shutdown command doesn't support graceful shutdown > ------------------------------------------------------ > > Key: WFCORE-1420 > URL: https://issues.jboss.org/browse/WFCORE-1420 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.1.0.CR1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.1.0.CR2 > > > The shutdown command needs to support a timeout param so users can have a graceful shutdown. > I'm calling this a bug because the low level :shutdown op is not reliable for CLI users due to the issues with handling of connection closing that the shutdown command takes care of. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3248) Clustering Extended testsuite is broken

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3248?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-3248: -------------------------------------- Fix for ClusterPassivationDDTestCase https://github.com/wildfly/wildfly/pull/8776 > Clustering Extended testsuite is broken > --------------------------------------- > > Key: WFLY-3248 > URL: https://issues.jboss.org/browse/WFLY-3248 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 8.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > What we did a while back, we made the sync-tcp the default configuration for running the clustering tests. However, we kept a extended testsuite with other combinations and other unimportant clustering tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-443) Update KeyStore backed security realm to iterate it's entries to attempt to find a matching alias for the evidence.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-443: ------------------------------------ Summary: Update KeyStore backed security realm to iterate it's entries to attempt to find a matching alias for the evidence. Key: ELY-443 URL: https://issues.jboss.org/browse/ELY-443 Project: WildFly Elytron Issue Type: Feature Request Components: Realms Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta5 Ideally an EvidenceDecoder would have been used up front but as this is technically possible to implement we should do so. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-165) Can not call "visibility" bridged methods

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JBEE-165?page=com.atlassian.jira.plugin.s... ] Scott Marlow closed JBEE-165. ----------------------------- Resolution: Done > Can not call "visibility" bridged methods > ----------------------------------------- > > Key: JBEE-165 > URL: https://issues.jboss.org/browse/JBEE-165 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-el-api > Reporter: Trond G. Ziarkowski > Assignee: Scott Marlow > Labels: el > Fix For: jboss-el-api_3.0_spec-1.0.6.Final > > > After fix of WFLY-3456 all bridged methods are filtered which causes javax.el.MethodNotFoundException for "visibility" bridged methods. > This has been commented by [~bodist] in WFLY-3456, but nothing has been done to fix it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-165) Can not call "visibility" bridged methods

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JBEE-165?page=com.atlassian.jira.plugin.s... ] Scott Marlow reopened JBEE-165: ------------------------------- > Can not call "visibility" bridged methods > ----------------------------------------- > > Key: JBEE-165 > URL: https://issues.jboss.org/browse/JBEE-165 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Trond G. Ziarkowski > Assignee: Scott Marlow > Labels: el > Fix For: jboss-el-api_3.0_spec-1.0.6.Final > > > After fix of WFLY-3456 all bridged methods are filtered which causes javax.el.MethodNotFoundException for "visibility" bridged methods. > This has been commented by [~bodist] in WFLY-3456, but nothing has been done to fix it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-165) Can not call "visibility" bridged methods

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JBEE-165?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated JBEE-165: ------------------------------ Component/s: jboss-el-api > Can not call "visibility" bridged methods > ----------------------------------------- > > Key: JBEE-165 > URL: https://issues.jboss.org/browse/JBEE-165 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-el-api > Reporter: Trond G. Ziarkowski > Assignee: Scott Marlow > Labels: el > Fix For: jboss-el-api_3.0_spec-1.0.6.Final > > > After fix of WFLY-3456 all bridged methods are filtered which causes javax.el.MethodNotFoundException for "visibility" bridged methods. > This has been commented by [~bodist] in WFLY-3456, but nothing has been done to fix it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-165) Can not call "visibility" bridged methods

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/JBEE-165?page=com.atlassian.jira.plugin.s... ] Scott Marlow moved WFLY-6280 to JBEE-165: ----------------------------------------- Project: JBoss JavaEE Spec APIs (was: WildFly) Key: JBEE-165 (was: WFLY-6280) Workflow: classic default workflow (was: GIT Pull Request workflow ) Affects Version/s: (was: 9.0.2.Final) (was: 10.0.0.Final) Fix Version/s: jboss-el-api_3.0_spec-1.0.6.Final (was: 10.1.0.Final) > Can not call "visibility" bridged methods > ----------------------------------------- > > Key: JBEE-165 > URL: https://issues.jboss.org/browse/JBEE-165 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Trond G. Ziarkowski > Assignee: Scott Marlow > Labels: el > Fix For: jboss-el-api_3.0_spec-1.0.6.Final > > > After fix of WFLY-3456 all bridged methods are filtered which causes javax.el.MethodNotFoundException for "visibility" bridged methods. > This has been commented by [~bodist] in WFLY-3456, but nothing has been done to fix it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 March 2016