June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1189) Automate Overview actions

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1189?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1189. ----------------------------------- Resolution: Done > Automate Overview actions > ------------------------- > > Key: SWSQE-1189 > URL: https://issues.redhat.com/browse/SWSQE-1189 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1830 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13624) Eliminate 'subclassing' of wildfly-servlet feature pack content by wildfly-ee and wildfly feature packs

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13624: --------------------------------------- Summary: Eliminate 'subclassing' of wildfly-servlet feature pack content by wildfly-ee and wildfly feature packs Key: WFLY-13624 URL: https://issues.redhat.com/browse/WFLY-13624 Project: WildFly Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 21.0.0.Beta1 See [https://lists.jboss.org/pipermail/wildfly-dev/2020-June/007342.html]... background. Eliminate direct reference to wildfly-servlet feature pack in configuration content in wildfly-ee and wildfly feature packs. This is a step toward being able to eliminate the dependency on wildfly-servlet. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13623) Organize feature pack code to facilitate separate EE 8 and EE 9 variants

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13623?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFCORE-5026 to WFLY-13623: ------------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-13623 (was: WFCORE-5026) Component/s: Build System (was: Build System) Fix Version/s: 21.0.0.Beta1 (was: 13.0.0.Beta1) > Organize feature pack code to facilitate separate EE 8 and EE 9 variants > ------------------------------------------------------------------------ > > Key: WFLY-13623 > URL: https://issues.redhat.com/browse/WFLY-13623 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 21.0.0.Beta1 > > > Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others. > See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have. > License.xml generation will likely require https://github.com/wildfly/maven-plugins/issues/10 as the split would mean the input would be split as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13623) Organize feature pack code to facilitate separate EE 8 and EE 9 variants

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13623?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13623: ------------------------------------ Description: Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others. See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have. was: Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others. See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have. License.xml generation will likely require https://github.com/wildfly/maven-plugins/issues/10 as the split would mean the input would be split as well. > Organize feature pack code to facilitate separate EE 8 and EE 9 variants > ------------------------------------------------------------------------ > > Key: WFLY-13623 > URL: https://issues.redhat.com/browse/WFLY-13623 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 21.0.0.Beta1 > > > Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others. > See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5026) Organize feature pack code to facilitate separate EE 8 and EE 9 variants

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-5026: ---------------------------------------- Summary: Organize feature pack code to facilitate separate EE 8 and EE 9 variants Key: WFCORE-5026 URL: https://issues.redhat.com/browse/WFCORE-5026 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 13.0.0.Beta1 Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others. See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have. License.xml generation will likely require https://github.com/wildfly/maven-plugins/issues/10 as the split would mean the input would be split as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13622) Upgrade WildFly maven-plugins to 2.2.0.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13622?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13622: ------------------------------------ Description: Pick up [https://github.com/wildfly/maven-plugins/issues/10] [https://github.com/wildfly/maven-plugins/compare/2.0.0.Final...2.2.0.Final] Also aligns with WildFly Core which made this move with WFCORE-5008. was: Pick up [https://github.com/wildfly/maven-plugins/issues/10] Also aligns with WildFly Core which made this move with WFCORE-5008. > Upgrade WildFly maven-plugins to 2.2.0.Final > -------------------------------------------- > > Key: WFLY-13622 > URL: https://issues.redhat.com/browse/WFLY-13622 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 21.0.0.Beta1 > > > Pick up [https://github.com/wildfly/maven-plugins/issues/10] > > [https://github.com/wildfly/maven-plugins/compare/2.0.0.Final...2.2.0.Final] > > Also aligns with WildFly Core which made this move with WFCORE-5008. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13622) Upgrade WildFly maven-plugins to 2.2.0.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13622?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13622: ------------------------------------ Description: Pick up [https://github.com/wildfly/maven-plugins/issues/10] Also aligns with WildFly Core which made this move with WFCORE-5008. was:Pick up [https://github.com/wildfly/maven-plugins/issues/10] > Upgrade WildFly maven-plugins to 2.2.0.Final > -------------------------------------------- > > Key: WFLY-13622 > URL: https://issues.redhat.com/browse/WFLY-13622 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 21.0.0.Beta1 > > > Pick up [https://github.com/wildfly/maven-plugins/issues/10] > > Also aligns with WildFly Core which made this move with WFCORE-5008. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13622) Upgrade WildFly maven-plugins to 2.2.0.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13622?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFCORE-5025 to WFLY-13622: ------------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-13622 (was: WFCORE-5025) Component/s: Build System (was: Build System) Fix Version/s: 21.0.0.Beta1 (was: 13.0.0.Beta1) > Upgrade WildFly maven-plugins to 2.2.0.Final > -------------------------------------------- > > Key: WFLY-13622 > URL: https://issues.redhat.com/browse/WFLY-13622 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 21.0.0.Beta1 > > > Pick up [https://github.com/wildfly/maven-plugins/issues/10] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5025) Upgrade WildFly maven-plugins to 2.2.0.Final

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-5025: ---------------------------------------- Summary: Upgrade WildFly maven-plugins to 2.2.0.Final Key: WFCORE-5025 URL: https://issues.redhat.com/browse/WFCORE-5025 Project: WildFly Core Issue Type: Component Upgrade Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 13.0.0.Beta1 Pick up [https://github.com/wildfly/maven-plugins/issues/10] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5012) Upgrade Jboss Threads to 2.3.6

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-5012?page=com.atlassian.jira.plug... ] Yeray Borges Santana updated WFCORE-5012: ----------------------------------------- Description: Upgrade jboss Thread to 2.3.6 (was: Upgrade jboss Thread to 2.3.5) > Upgrade Jboss Threads to 2.3.6 > ------------------------------ > > Key: WFCORE-5012 > URL: https://issues.redhat.com/browse/WFCORE-5012 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Major > > Upgrade jboss Thread to 2.3.6 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 June 2020