June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22584) jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22584?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22584: ------------------------------- Fix Version/s: 4.5.0.Final > jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22584 > URL: https://issues.jboss.org/browse/JBIDE-22584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, central-update > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final, 4.5.x > > > Normally, jbosstools-central is built before jbosstools-discovery. > However, running jbosstools-central build for the first time, ran into this: > {code} > 22:43:51 [INFO] org.jboss.tools.community.central .................. FAILURE [ 0.556 s] > 22:43:51 [INFO] org.jboss.tools.community.central.feature .......... SKIPPED > 22:43:51 [INFO] central.maven.examples.site ........................ SKIPPED > 22:43:52 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project org.jboss.tools.community.central: IO Error: Could not get content -> [Help 1] > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > Or, this could be a problem w/ bootstrapping values in ide-config.properties? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24141: ------------------------------- Affects Version/s: 4.5.0.AM2 > Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component > ------------------------------------------------------------ > > Key: JBIDE-24141 > URL: https://issues.jboss.org/browse/JBIDE-24141 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.4.4.AM2, 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: testfailure > Fix For: 4.5.x > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component:* > https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for webservices component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.15 sec 2 > {code} > {code} > Failed > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > Failing for the past 2 builds (Since Unstable#74 ) > Took 0.15 sec. > add description > Error Message > Expected: <6> > but: was <10> > Stacktrace > java.lang.AssertionError: > Expected: <6> > but: was <10> > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.junit.Assert.assertThat(Assert.java:956) > at org.junit.Assert.assertThat(Assert.java:923) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication(JaxrsMetamodelChangedProcessorTestCase.java:358) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24141: ------------------------------------ Same two test failures in 4.5.0.AM2: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... One appears to be intermittent: *org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication* > Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component > ------------------------------------------------------------ > > Key: JBIDE-24141 > URL: https://issues.jboss.org/browse/JBIDE-24141 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: testfailure > Fix For: 4.5.x > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component:* > https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for webservices component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.15 sec 2 > {code} > {code} > Failed > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > Failing for the past 2 builds (Since Unstable#74 ) > Took 0.15 sec. > add description > Error Message > Expected: <6> > but: was <10> > Stacktrace > java.lang.AssertionError: > Expected: <6> > but: was <10> > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.junit.Assert.assertThat(Assert.java:956) > at org.junit.Assert.assertThat(Assert.java:923) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication(JaxrsMetamodelChangedProcessorTestCase.java:358) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24237) integration tests PR check relies on outdated update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24237?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-24237. -------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.5.x) Resolution: Done [~psrna] Job is back to green so assuming this is fixed. Please verify and close or reopen if I'm wrong. > integration tests PR check relies on outdated update site > --------------------------------------------------------- > > Key: JBIDE-24237 > URL: https://issues.jboss.org/browse/JBIDE-24237 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 4.5.0.AM1 > > > My PR for jbosstools-integration-tests failed [1] to build because the build is looking at an outdated mirror, *jbosstools-coretests-mirror* = http://10.8.175.83:8081/nexus/content/repositories/jbosstools-coretests/p... > {code} > 14:17:43 [ERROR] Software being installed: org.jboss.tools.arquillian.reddeer 4.4.100.qualifier > 14:17:43 [ERROR] Missing requirement: org.jboss.tools.arquillian.reddeer 4.4.100.qualifier requires > 'bundle org.jboss.ide.eclipse.as.reddeer [3.3.0,3.4.0)' but it could not be found > {code} > -- [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbt-inte... > Why isn't the build resolving the root pom variable: > {code}jbosstools-tests-site=http://download.jboss.org/jbosstools/${eclipseReleaseName}/snapshots/updates/coretests/${stream_jbt}/{code} > If it was, you'd see the o.j.*.reddeer_3.3.0 plugins, instead of the 3.2.x version ones and the PR would build correctly. > See for yourself here - the 3.3.0 versions are here: > http://download.jboss.org/jbosstools/oxygen/snapshots/updates/coretests/m... > I've made a change to the job config [2] and have attempted to re-fire the PR build. > [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbt-inte... > {code} > -Djbosstools-coretests-mirror=http://download.jboss.org/jbosstools/oxygen/snapshots/updates/coretests/master/{code} > How can the Nexus mirror be updated? More importantly, can there be one mirror for the 4.x stream and another for the 4.5.x stream? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24237) integration tests PR check relies on outdated update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24237?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24237: ------------------------------- Description: My PR for jbosstools-integration-tests failed [1] to build because the build is looking at an outdated mirror, *jbosstools-coretests-mirror* = http://10.8.175.83:8081/nexus/content/repositories/jbosstools-coretests/p... {code} 14:17:43 [ERROR] Software being installed: org.jboss.tools.arquillian.reddeer 4.4.100.qualifier 14:17:43 [ERROR] Missing requirement: org.jboss.tools.arquillian.reddeer 4.4.100.qualifier requires 'bundle org.jboss.ide.eclipse.as.reddeer [3.3.0,3.4.0)' but it could not be found {code} -- [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbt-inte... Why isn't the build resolving the root pom variable: {code}jbosstools-tests-site=http://download.jboss.org/jbosstools/${eclipseReleaseName}/snapshots/updates/coretests/${stream_jbt}/{code} If it was, you'd see the o.j.*.reddeer_3.3.0 plugins, instead of the 3.2.x version ones and the PR would build correctly. See for yourself here - the 3.3.0 versions are here: http://download.jboss.org/jbosstools/oxygen/snapshots/updates/coretests/m... I've made a change to the job config [2] and have attempted to re-fire the PR build. [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbt-inte... {code} -Djbosstools-coretests-mirror=http://download.jboss.org/jbosstools/oxygen/snapshots/updates/coretests/master/{code} How can the Nexus mirror be updated? More importantly, can there be one mirror for the 4.x stream and another for the 4.5.x stream? was: My PR for jbosstools-integration-tests failed [1] to build because the build is looking at an outdated mirror, *jbosstools-coretests-mirror* = http://10.8.175.83:8081/nexus/content/repositories/jbosstools-coretests/p... {code} 14:17:43 [ERROR] Software being installed: org.jboss.tools.arquillian.reddeer 4.4.100.qualifier 14:17:43 [ERROR] Missing requirement: org.jboss.tools.arquillian.reddeer 4.4.100.qualifier requires 'bundle org.jboss.ide.eclipse.as.reddeer [3.3.0,3.4.0)' but it could not be found {code} -- [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbt-inte... Why isn't the build resolving the root pom variable: {code}jbosstools-tests-site=http://download.jboss.org/jbosstools/${eclipseReleaseName}/snapshots/updates/coretests/${stream_jbt}/{code} If it was, you'd see the o.j.*.reddeer_3.3.0 plugins, instead of the 3.2.x version ones and the PR would build correctly. See for yourself here - the 3.3.0 versions are here: http://download.jboss.org/jbosstools/oxygen/snapshots/updates/coretests/m... I've made a change to the job config [2] and have attempted to re-fire the PR build. [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbt-inte... {code} -Djbosstools-coretests-mirror=http://download.jboss.org/jbosstools/oxygen/snapshots/updates/coretests/master/ How can the Nexus mirror be updated? More importantly, can there be one mirror for the 4.x stream and another for the 4.5.x stream? > integration tests PR check relies on outdated update site > --------------------------------------------------------- > > Key: JBIDE-24237 > URL: https://issues.jboss.org/browse/JBIDE-24237 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Pavol Srna > Fix For: 4.5.x > > > My PR for jbosstools-integration-tests failed [1] to build because the build is looking at an outdated mirror, *jbosstools-coretests-mirror* = http://10.8.175.83:8081/nexus/content/repositories/jbosstools-coretests/p... > {code} > 14:17:43 [ERROR] Software being installed: org.jboss.tools.arquillian.reddeer 4.4.100.qualifier > 14:17:43 [ERROR] Missing requirement: org.jboss.tools.arquillian.reddeer 4.4.100.qualifier requires > 'bundle org.jboss.ide.eclipse.as.reddeer [3.3.0,3.4.0)' but it could not be found > {code} > -- [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbt-inte... > Why isn't the build resolving the root pom variable: > {code}jbosstools-tests-site=http://download.jboss.org/jbosstools/${eclipseReleaseName}/snapshots/updates/coretests/${stream_jbt}/{code} > If it was, you'd see the o.j.*.reddeer_3.3.0 plugins, instead of the 3.2.x version ones and the PR would build correctly. > See for yourself here - the 3.3.0 versions are here: > http://download.jboss.org/jbosstools/oxygen/snapshots/updates/coretests/m... > I've made a change to the job config [2] and have attempted to re-fire the PR build. > [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbt-inte... > {code} > -Djbosstools-coretests-mirror=http://download.jboss.org/jbosstools/oxygen/snapshots/updates/coretests/master/{code} > How can the Nexus mirror be updated? More importantly, can there be one mirror for the 4.x stream and another for the 4.5.x stream? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24379) javaee tests failing for linux, windows and osx

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24379?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24379: ------------------------------- Attachment: javaee-tests-failing.png > javaee tests failing for linux, windows and osx > ----------------------------------------------- > > Key: JBIDE-24379 > URL: https://issues.jboss.org/browse/JBIDE-24379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, jsf, seam2 > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.5.x > > Attachments: javaee-test-failures.png, javaee-test-failures_last_pass_jan26.png, javaee-tests-failing.png > > > JavaEE tests have been failing for months. > Please investigate. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24379) javaee tests failing for linux, windows and osx

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24379?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24379: ------------------------------------ Months later and no one has prioritized this. !javaee-tests-failing.png|thumbnail! > javaee tests failing for linux, windows and osx > ----------------------------------------------- > > Key: JBIDE-24379 > URL: https://issues.jboss.org/browse/JBIDE-24379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, jsf, seam2 > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.5.x > > Attachments: javaee-test-failures.png, javaee-test-failures_last_pass_jan26.png, javaee-tests-failing.png > > > JavaEE tests have been failing for months. > Please investigate. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18902) Add Ceylon IDE to JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18902?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18902: ------------------------------------ Three weeks later. Still need something like a +1 here from Jeff MAURY or Tim Moran or Todd Mancini to underscore that this is something we want to promote in Central... and also why. Is Ceylon something we want to promote in devstudio? > Add Ceylon IDE to JBoss Central > ------------------------------- > > Key: JBIDE-18902 > URL: https://issues.jboss.org/browse/JBIDE-18902 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.0.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.5.x > > > It's probably time to consider adding Ceylon IDE to JBoss Central, provided it doesn't break anything. > Questions are : > - Early Access or not? > - should JBDS get it? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24524) a TypeScript editor (BlueSky)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24524?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24524: ------------------------------------ [~mickael_istria] I'm happy to add this if you can any any of the above people to say they want it added. Is TypeScript editing something we want to promote in devstudio? If so, why? I'll need an explanation before we can proceed here. > a TypeScript editor (BlueSky) > ----------------------------- > > Key: JBIDE-24524 > URL: https://issues.jboss.org/browse/JBIDE-24524 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jst > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.5.x > > > BlueSky plugin ( https://marketplace.eclipse.org/content/bluesky-web-development-eclipse-i... ) brings support for TypeScript edition in Eclipse IDE relying on included language server. JBoss Tools should probably include it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20609) More accessible and visible Early Access content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20609?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20609. ------------------------------ Fix Version/s: 4.5.0.AM1 (was: 4.5.x) Assignee: Nick Boldt Resolution: Won't Fix With no commitment, no further clarification, no owner, and no push from program management, closing as won't fix. > More accessible and visible Early Access content > ------------------------------------------------ > > Key: JBIDE-20609 > URL: https://issues.jboss.org/browse/JBIDE-20609 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > In order to make early-access content more accessible, we can improve the workflow of making EA connectors visible -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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