November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25228: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.2.AM1) > target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions > -------------------------------------------------------------------------------------------- > > Key: JBIDE-25228 > URL: https://issues.jboss.org/browse/JBIDE-25228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.5.2.AM2, 4.5.x > > > With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU. > We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails. > Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs? > Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually. > [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb... > [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4... > [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... > [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b... > [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25228: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.5.2.AM2* and sprint = *devex #141 December 2017* > target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions > -------------------------------------------------------------------------------------------- > > Key: JBIDE-25228 > URL: https://issues.jboss.org/browse/JBIDE-25228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.5.2.AM2, 4.5.x > > > With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU. > We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails. > Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs? > Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually. > [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb... > [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4... > [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... > [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... > [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b... > [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25219) Update cdk-scripts to support minishift's profile features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25219?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25219: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.2.AM1) > Update cdk-scripts to support minishift's profile features > ---------------------------------------------------------- > > Key: JBIDE-25219 > URL: https://issues.jboss.org/browse/JBIDE-25219 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.2.AM2 > > > See https://github.com/odockal/cdk-scripts/issues/17. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25219) Update cdk-scripts to support minishift's profile features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25219?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25219: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.5.2.AM2* and sprint = *devex #141 December 2017* > Update cdk-scripts to support minishift's profile features > ---------------------------------------------------------- > > Key: JBIDE-25219 > URL: https://issues.jboss.org/browse/JBIDE-25219 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.2.AM2 > > > See https://github.com/odockal/cdk-scripts/issues/17. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25314) CDK integration tests for propagation of values to launch configuration

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25314?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25314: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.2.AM1) > CDK integration tests for propagation of values to launch configuration > ----------------------------------------------------------------------- > > Key: JBIDE-25314 > URL: https://issues.jboss.org/browse/JBIDE-25314 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: cdk > Fix For: 4.5.2.AM2 > > > Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path). Also, this check can be done after CDK server adapter is created via wizard, and when CDK server editor is changed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25314) CDK integration tests for propagation of values to launch configuration

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25314?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25314: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.5.2.AM2* and sprint = *devex #141 December 2017* > CDK integration tests for propagation of values to launch configuration > ----------------------------------------------------------------------- > > Key: JBIDE-25314 > URL: https://issues.jboss.org/browse/JBIDE-25314 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: cdk > Fix For: 4.5.2.AM2 > > > Check propagation of values of CDK server configuration into these launch config's part: Main Tab: Name, Location of minishift binary, Arguments (hypervisor and profile name), Environment Tab: Environment variables check (minishift home, minishift username and path). Also, this check can be done after CDK server adapter is created via wizard, and when CDK server editor is changed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25276: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.2.AM1) > intermittent test failures in webservices > ----------------------------------------- > > Key: JBIDE-25276 > URL: https://issues.jboss.org/browse/JBIDE-25276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.2.AM2 > > > Various tests are failing intermittently. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 37 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 0.65 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 0.6 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 0.59 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication 0.1 sec 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.67 sec 2 > Can these be fixed or if not, disabled, so that we can consistently get green builds? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25276: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.5.2.AM2* and sprint = *devex #141 December 2017* > intermittent test failures in webservices > ----------------------------------------- > > Key: JBIDE-25276 > URL: https://issues.jboss.org/browse/JBIDE-25276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.2.AM2 > > > Various tests are failing intermittently. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 37 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 0.65 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 0.6 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 0.59 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication 0.1 sec 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.67 sec 2 > Can these be fixed or if not, disabled, so that we can consistently get green builds? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25275?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25275: ------------------------------- Fix Version/s: 4.5.2.AM2 (was: 4.5.2.AM1) > intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25275 > URL: https://issues.jboss.org/browse/JBIDE-25275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.2.AM2, 4.5.x > > Attachments: intermittent-test-failures-central.png > > > intermittent test failures since Oct 3, when the last commit was pushed. > !intermittent-test-failures-central.png|thumbnail! > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Should we disable this test? or fix it? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25275?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25275: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.5.2.AM1* and sprint = *devex #141 December 2017* > intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25275 > URL: https://issues.jboss.org/browse/JBIDE-25275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.2.AM1, 4.5.x > > Attachments: intermittent-test-failures-central.png > > > intermittent test failures since Oct 3, when the last commit was pushed. > !intermittent-test-failures-central.png|thumbnail! > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Should we disable this test? or fix it? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 November 2017