July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22735) CDK Server adapter is not available in Quick Access bar when typing "cdk"

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22735?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22735: ----------------------------------- Fix Version/s: 4.4.1.AM3 Sprint: devex #118 July 2017 > CDK Server adapter is not available in Quick Access bar when typing "cdk" > ------------------------------------------------------------------------- > > Key: JBIDE-22735 > URL: https://issues.jboss.org/browse/JBIDE-22735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.AM3 > > > I guess this is a side effect of renaming "CDK Server Adapter" to "Container Development Environment". > We need to investigate if the only way to make the adapter available for "cdk" is to have "cdk" mentioned in the server type name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22735) CDK Server adapter is not available in Quick Access bar when typing "cdk"

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22735?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22735: ---------------------------------------- Agreed on 5x5 call. We will use "Launch Container Development Environment using Red Hat CDK". > CDK Server adapter is not available in Quick Access bar when typing "cdk" > ------------------------------------------------------------------------- > > Key: JBIDE-22735 > URL: https://issues.jboss.org/browse/JBIDE-22735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > > I guess this is a side effect of renaming "CDK Server Adapter" to "Container Development Environment". > We need to investigate if the only way to make the adapter available for "cdk" is to have "cdk" mentioned in the server type name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22739) Use simpler Surefire include/exclude pattern in root poms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22739?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22739: ------------------------------------ [~akazakov] please list which projects would benefit from a change similar to the one done for Base in JBIDE-19081 > Use simpler Surefire include/exclude pattern in root poms > --------------------------------------------------------- > > Key: JBIDE-22739 > URL: https://issues.jboss.org/browse/JBIDE-22739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22739) Use simpler Surefire include/exclude pattern in root poms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22739?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22739: ------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.AM2) > Use simpler Surefire include/exclude pattern in root poms > --------------------------------------------------------- > > Key: JBIDE-22739 > URL: https://issues.jboss.org/browse/JBIDE-22739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22739) Use simpler Surefire include/exclude pattern in root poms

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22739: ---------------------------------- Summary: Use simpler Surefire include/exclude pattern in root poms Key: JBIDE-22739 URL: https://issues.jboss.org/browse/JBIDE-22739 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Reporter: Nick Boldt Assignee: Fred Bricon Priority: Minor Fix For: 4.4.1.AM2 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: {code} include = *Test*, *Test, *TestCase exclude = *Abstract* {code} 2. If that causes test failures because running incorrectly named abstract stuff, they can refactor, add their own root pom overrides, use a TestSuite, or use @Ignore in test classes. 3. If the count of tests run suddenly DROPS because the pattern isn't running the correct # of tests, they can add their own root pom overrides, or use a TestSuite. Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22739) Use simpler Surefire include/exclude pattern in root poms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22739?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22739: ------------------------------- Git Pull Request: (was: https://github.com/jbosstools/jbosstools-build/pull/167, https://github.com/jbosstools/jbosstools-javaee/pull/398, https://github.com/jbosstools/jbosstools-jst/pull/565, https://github.com/jbosstools/jbosstools-base/pull/517) > Use simpler Surefire include/exclude pattern in root poms > --------------------------------------------------------- > > Key: JBIDE-22739 > URL: https://issues.jboss.org/browse/JBIDE-22739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.1.AM2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22739) Use simpler Surefire include/exclude pattern in root poms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22739?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22739: ---------------------------------- Assignee: Alexey Kazakov (was: Fred Bricon) > Use simpler Surefire include/exclude pattern in root poms > --------------------------------------------------------- > > Key: JBIDE-22739 > URL: https://issues.jboss.org/browse/JBIDE-22739 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.4.1.AM2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in Base root pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19081: ------------------------------- Summary: Use simpler Surefire include/exclude pattern in Base root pom (was: Use simpler Surefire include/exclude pattern in parent pom) > Use simpler Surefire include/exclude pattern in Base root pom > ------------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.1.AM2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in Base root pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19081: ------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.x) > Use simpler Surefire include/exclude pattern in Base root pom > ------------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.1.AM2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in Base root pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19081: ---------------------------------- Assignee: Fred Bricon (was: Nick Boldt) > Use simpler Surefire include/exclude pattern in Base root pom > ------------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.1.AM2 > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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

jbosstools-issues July 2016