[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19933:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.x)
> Copy master snapshot to 4.5.oxygen update site at code freeze to initiate it
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19933
> URL: https://issues.jboss.org/browse/JBIDE-19933
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master).
> Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch.
> It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point.
> For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years
[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)
7 years
[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)
7 years
[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)
7 years
[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)
7 years
[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)
7 years