[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24141:
-------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.5.0.AM1)
> 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.0.AM2
>
>
> *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, 1 month
[JBoss JIRA] (JBIDE-22713) IOException in CentralHelper.extractIfNeeded
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22713?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22713:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> IOException in CentralHelper.extractIfNeeded
> --------------------------------------------
>
> Key: JBIDE-22713
> URL: https://issues.jboss.org/browse/JBIDE-22713
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Jeff MAURY
> Fix For: 4.5.0.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: Unable to open C:\eclipse\plugins\org.jboss.tools.central_2.0.1.Final-v20160401-1059-B103\resources\jbosstools-central-webpage.zip
> {noformat}
> java.io.IOException: D:\OneDrive\TreinaWeb\Java Básico\JSE\.metadata\.plugins\org.jboss.tools.central\central\bc8a80b\index.html can not be found
> at org.jboss.tools.central.internal.CentralHelper.extractIfNeeded(CentralHelper.java:203)
> at org.jboss.tools.central.internal.CentralHelper.getCentralPageUrl(CentralHelper.java:122)
> at org.jboss.tools.central.internal.CentralHelper.getCentralUrl(CentralHelper.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$5.run(GettingStartedHtmlPage.java:252)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.1.0.qualifier |
> Operating Systems:
> | Linux | 3.2.0 | 4.5.7.fc23 |
> | MacOSX | 10.10.5 | 10.11.5 |
> | Windows | 5.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571659e0e4b055563f...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 1 month
[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23402:
-------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.5.0.AM1)
> [WATCHER] Explorer: can "Deploy Latest" even if the build failed
> ----------------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Fix For: 4.5.0.AM2
>
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 1 month
[JBoss JIRA] (JBIDE-23402) [WATCHER] Explorer: can "Deploy Latest" even if the build failed
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23402?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23402:
----------------------------------
Assignee: Jeff MAURY
> [WATCHER] Explorer: can "Deploy Latest" even if the build failed
> ----------------------------------------------------------------
>
> Key: JBIDE-23402
> URL: https://issues.jboss.org/browse/JBIDE-23402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.2.AM2
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Fix For: 4.5.0.AM2
>
> Attachments: JBIDE-23402-a.png, JBIDE-23402-b.png
>
>
> When right-clicking on an application, we can select "Deploy Latest". This will start both a build and a deploy pod. The deploy pod will wait for the build pod to complete.
> In this case, due to github being unavailable, the build pod will fail very quickly. The deploy pod will then continue waiting up to 10 minutes even though what it is waiting for has already failed. This 10 minutes is wasted. It should fail quickly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 1 month
[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21674:
-------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.5.0.AM1)
> Enable hierarchical view by default in Project Explorer
> -------------------------------------------------------
>
> Key: JBIDE-21674
> URL: https://issues.jboss.org/browse/JBIDE-21674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common, upstream
> Reporter: Xavier Coulon
> Fix For: 4.5.0.AM2
>
>
> Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects).
> After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 1 month
[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-21674:
----------------------------------
Assignee: Jeff MAURY
> Enable hierarchical view by default in Project Explorer
> -------------------------------------------------------
>
> Key: JBIDE-21674
> URL: https://issues.jboss.org/browse/JBIDE-21674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common, upstream
> Reporter: Xavier Coulon
> Assignee: Jeff MAURY
> Fix For: 4.5.0.AM2
>
>
> Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects).
> After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 1 month