February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9794) Add Elytron Web undertow-servlet module

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-9794: -------------------------------------- Summary: Add Elytron Web undertow-servlet module Key: WFLY-9794 URL: https://issues.jboss.org/browse/WFLY-9794 Project: WildFly Issue Type: Sub-task Components: Build System, Security, Web (Undertow) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 12.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7042) Elytron Test Coverage

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-7042?page=com.atlassian.jira.plugin.... ] Kabir Khan resolved WFLY-7042. ------------------------------ Resolution: Done Resolving since it looks like all blocking issues have been done > Elytron Test Coverage > --------------------- > > Key: WFLY-7042 > URL: https://issues.jboss.org/browse/WFLY-7042 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Labels: elytron_testing > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9406) Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Tibor Digana commented on WFLY-9406: ------------------------------------ [~asoldano] This issue can be marked resolved, I guess. Is JBoss responsible to upgrade Arquillian Universe. It should be updated and JaCoCo extension in Arquillian based on your changes. > Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ----------------------------------------------------------------------------- > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, JPA / Hibernate, Web Services > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Alessio Soldano > Priority: Minor > Fix For: 12.0.0.Alpha1 > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian Extension dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9406) Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Tibor Digana edited comment on WFLY-9406 at 2/9/18 11:45 PM: ------------------------------------------------------------- [~asoldano] This issue can be marked resolved, I guess. Is JBoss responsible to upgrade Arquillian Universe? It should be updated and JaCoCo extension in Arquillian based on your changes. was (Author: tibor17): [~asoldano] This issue can be marked resolved, I guess. Is JBoss responsible to upgrade Arquillian Universe. It should be updated and JaCoCo extension in Arquillian based on your changes. > Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ----------------------------------------------------------------------------- > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, JPA / Hibernate, Web Services > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Alessio Soldano > Priority: Minor > Fix For: 12.0.0.Alpha1 > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian Extension dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9792) Make it easier to switch the maven groupId in different branches

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9792?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9792: ----------------------------------- Summary: Make it easier to switch the maven groupId in different branches (was: Use ${project.groupId} where possible in our poms) > Make it easier to switch the maven groupId in different branches > ---------------------------------------------------------------- > > Key: WFLY-9792 > URL: https://issues.jboss.org/browse/WFLY-9792 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > Different branches of our code use different Maven groupId values for the modules. Simplify the task of this conversion by: > 1) Avoiding hard-coding of the groupId anywhere where it is not required, using {code}${project.groupId}{code} instead. Goal is to limit declaration of the group id to the root pom and to the groupId child element in each pom's "parent" element. Changing the groupId then becomes a task analogous to changing the maven version. > 2) Eliminating unnecessary groupId elements where a child pom redundantly declares the groupId inherited from its parent. > 3) Separating groupId elements from version elements by making sure artifactId is in between (rather than before groupId as is currently done in some poms.) This will help avoid spurious conflicts between commits the update the groupId and those that update the version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9792) Use ${project.groupId} where possible in our poms

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9792?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9792: ----------------------------------- Description: Different branches of our code use different Maven groupId values for the modules. Simplify the task of this conversion by: 1) Avoiding hard-coding of the groupId anywhere where it is not required, using {code}${project.groupId}{code} instead. Goal is to limit declaration of the group id to the root pom and to the groupId child element in each pom's "parent" element. Changing the groupId then becomes a task analogous to changing the maven version. 2) Eliminating unnecessary groupId elements where a child pom redundantly declares the groupId inherited from its parent. 3) Separating groupId elements from version elements by making sure artifactId is in between (rather than before groupId as is currently done in some poms.) This will help avoid spurious conflicts between commits the update the groupId and those that update the version. was:Different branches of our code use different Maven groupId values for the modules. Simplify the task of this conversion by avoiding hard-coding of the groupId anywhere where it is not required, using {code}${project.groupId}{code} instead. Goal is to limit declaration of the group id to the root pom and to the groupId child element in each pom's "parent" element. Changing the groupId then becomes a task analogous to changing the maven version. > Use ${project.groupId} where possible in our poms > ------------------------------------------------- > > Key: WFLY-9792 > URL: https://issues.jboss.org/browse/WFLY-9792 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > Different branches of our code use different Maven groupId values for the modules. Simplify the task of this conversion by: > 1) Avoiding hard-coding of the groupId anywhere where it is not required, using {code}${project.groupId}{code} instead. Goal is to limit declaration of the group id to the root pom and to the groupId child element in each pom's "parent" element. Changing the groupId then becomes a task analogous to changing the maven version. > 2) Eliminating unnecessary groupId elements where a child pom redundantly declares the groupId inherited from its parent. > 3) Separating groupId elements from version elements by making sure artifactId is in between (rather than before groupId as is currently done in some poms.) This will help avoid spurious conflicts between commits the update the groupId and those that update the version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9786) Add Java 9 support for RESTEasy

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9786?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9786: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10834 > Add Java 9 support for RESTEasy > ------------------------------- > > Key: WFLY-9786 > URL: https://issues.jboss.org/browse/WFLY-9786 > Project: WildFly > Issue Type: Task > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9787) JAX-RS client shoud support redirect

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9787?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9787: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10834 > JAX-RS client shoud support redirect > ------------------------------------ > > Key: WFLY-9787 > URL: https://issues.jboss.org/browse/WFLY-9787 > Project: WildFly > Issue Type: Feature Request > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 12.0.0.Alpha1 > > > Customer is requesting this fix into EAP https://issues.jboss.org/browse/RESTEASY-1075 > The RESTEasy implementation of the JAX-RS client library needs to support handling of redirects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9789) Upgrade RESTEasy to 3.5.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9789?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9789: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10819, https://github.com/wildfly/wildfly/pull/10834 (was: https://github.com/wildfly/wildfly/pull/10819) > Upgrade RESTEasy to 3.5.0.Final > ------------------------------- > > Key: WFLY-9789 > URL: https://issues.jboss.org/browse/WFLY-9789 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6459) JAX-RS 2.1 Support

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-6459?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-6459: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10834 > JAX-RS 2.1 Support > ------------------ > > Key: WFLY-6459 > URL: https://issues.jboss.org/browse/WFLY-6459 > Project: WildFly > Issue Type: Sub-task > Components: REST > Reporter: David Lloyd > Assignee: Alessio Soldano > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 February 2018