[JBoss JIRA] (JBIDE-26034) test failures in archives.ui.bot.*
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26034?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-26034:
------------------------------------------
Upstream issue which probably caused the failures https://bugs.eclipse.org/bugs/show_bug.cgi?id=535050 is fixed in 20180524 integration build. I successfully run the reddeer tests locally against the 20180524 build.
> test failures in archives.ui.bot.*
> ----------------------------------
>
> Key: JBIDE-26034
> URL: https://issues.jboss.org/browse/JBIDE-26034
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: archives, server
> Affects Versions: 4.6.0.AM2
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM3
>
>
> 9 tests have been failing for 25 builds:
> {code}
> org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest.testCreatingFolder no-configuration 2.4 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest.testModifyingFolder no-configuration 2.7 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest.testCreatingFileset no-configuration 2.8 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest.testModifyingFileset no-configuration 3 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.FilesetTest.testDeletingFileset no-configuration 2.8 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.UserLibrariesFilesetTest.testCreatingUserLibraryFileset no-configuration 1.8 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.CreatingArchiveTest.testCreatingArchiveWithExplorer no-configuration 0.8 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.DeletingArchiveTest.testDeletingArchiveWithExplorer no-configuration 1 sec 25
> org.jboss.ide.eclipse.archives.ui.test.bot.ModifyingArchiveTest.testModifyingArchiveWithExplorer no-configuration 1 sec 25
> {code}
> These 3 failures are newer:
> {code}
> org.jboss.ide.eclipse.archives.ui.test.bot.BuildingArchiveTest.testBuildingArchiveWithView no-configuration 0.75 sec 1
> org.jboss.ide.eclipse.archives.ui.test.bot.FolderTest.testDeletingFolder no-configuration 3.4 sec 2
> org.jboss.ide.eclipse.archives.ui.test.bot.BuildingProjectTest.testBuildingProjectWithExplorer no-configuration 0.66 sec 12
> {code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25967) Properties view: Add OC version for OpenShift connection
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25967?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25967:
------------------------------------
[~jkopriva] yes that was on purpose because trying to get the version requires to launch a process from the UI thread which we rejected. See the PR discussion
> Properties view: Add OC version for OpenShift connection
> --------------------------------------------------------
>
> Key: JBIDE-25967
> URL: https://issues.jboss.org/browse/JBIDE-25967
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM1
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Labels: oc_binary, properties
> Fix For: 4.6.0.AM2
>
> Attachments: Screenshot_20180525_101841.png
>
>
> Properties view for OpenShift connection should also contains OC version, not only path to it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25900) Support hyperlinks in Project Template Details group
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25900?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25900.
---------------------------------
Closing. Works as expected.
Verified in:
Red Hat JBoss Developer Studio
Version: 12.0.0.AM2
Build id: AM2-v20180524-2212-B2550
Build date: 20180524-2212
> Support hyperlinks in Project Template Details group
> ----------------------------------------------------
>
> Key: JBIDE-25900
> URL: https://issues.jboss.org/browse/JBIDE-25900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM3
> Reporter: Denis Golovin
> Assignee: Jeff MAURY
> Priority: Optional
> Fix For: 4.6.0.AM2
>
> Attachments: image-2018-04-04-00-36-48-807.png
>
>
> Would be good to support links in Template Details group, so copy/paste to browser would not be required.
> !image-2018-04-04-00-36-48-807.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBDS-4574) Improve naming of Karaf runtime created by installer
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBDS-4574?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík closed JBDS-4574.
------------------------------
verified - DevStudio 11.3.0.GA
> Improve naming of Karaf runtime created by installer
> ----------------------------------------------------
>
> Key: JBDS-4574
> URL: https://issues.jboss.org/browse/JBDS-4574
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: fusetools, installer, platform-installer, runtime-detection
> Affects Versions: 11.0.1.GA
> Reporter: Aurélien Pupier
> Assignee: Aurélien Pupier
> Fix For: 11.1.0.AM3
>
> Attachments: Fuse Tooling 10.1.0.AM3-JBoss Tools 4.5.1.AM3.png, image-2017-10-03-17-30-35-495.png, master history.png
>
>
> i used Development Suite installer 2.0.1 and installed Jboss Fuse Karaf Runtime from it, the name created for the Server adapter is "fuseplatformkaraf Runtime Server" which can be more user-friendly, what do you think of "Red Hat JBoss Fuse Runtime Server 6.3"?
> !image-2017-10-03-17-30-35-495.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25441) Problems with CDI Builder and scanning Jars which support Java 9
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25441?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25441:
------------------------------------
[~manuel_b1986] which version of JBoss Tools are you using ? I tried with javax.json-api-1.1.2.jar and was not able to reproduce
> Problems with CDI Builder and scanning Jars which support Java 9
> ----------------------------------------------------------------
>
> Key: JBIDE-25441
> URL: https://issues.jboss.org/browse/JBIDE-25441
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, common
> Affects Versions: 4.5.1.Final, 4.5.2.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.2.AM3
>
>
> As reported in https://developer.jboss.org/message/978446?et=watches.email.thread#978446:
> {quote}
> Setup:
> * Eclipse Oxygen 4.7.1
> * JBoss Tools 4.5.1.Final (also tested with latest development version 4.5.2.AM1)
> * An maven web application with certain dependencies
> ** So far, we found two dependencies, which lead to this jandex scaning error after upgrading to latest version
> ** org.apache.logging.log4j version 2.10.0
> ** org.ow2.asm version 6.0
>
> This leads to an CDI Builder IllegalStateException - see exception trace below.
> Both dependencies started support for Java 9, which seems to cause this exception.
>
> *Apache Log4j 2.10.0 released*: http://mail-archives.apache.org/mod_mbox/www-announce/201711.mbox/%3Cdf95...
>
> {code}
> !MESSAGE Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'Webapp'.
> !STACK 0
> java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 24
> at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:665)
> at org.jboss.jandex.Indexer.index(Indexer.java:699)
> at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56)
> at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26040) Error for JAX-RS 2.1 @Context types
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26040?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26040:
-------------------------------
Fix Version/s: 4.6.0.AM3
> Error for JAX-RS 2.1 @Context types
> -----------------------------------
>
> Key: JBIDE-26040
> URL: https://issues.jboss.org/browse/JBIDE-26040
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.3.Final
> Reporter: Rich DiCroce
> Assignee: Jeff MAURY
> Fix For: 4.6.0.AM3
>
>
> JAX-RS 2.1 adds some new types that can be injected into methods using the Context annotation, e.g. Sse and SseEventSink. Currently, JBoss Tools flags these with an error:
> {quote}
> @Context annotation is only allowed on method parameters of type '[javax.ws.rs.core.HttpHeaders, javax.ws.rs.core.UriInfo, javax.ws.rs.core.Request, javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, javax.servlet.ServletConfig, javax.servlet.ServletContext, javax.ws.rs.core.SecurityContext]'.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26040) Error for JAX-RS 2.1 @Context types
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26040?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26040:
-------------------------------
Sprint: devex #150 June 2019
> Error for JAX-RS 2.1 @Context types
> -----------------------------------
>
> Key: JBIDE-26040
> URL: https://issues.jboss.org/browse/JBIDE-26040
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.3.Final
> Reporter: Rich DiCroce
> Assignee: Jeff MAURY
> Fix For: 4.6.0.AM3
>
>
> JAX-RS 2.1 adds some new types that can be injected into methods using the Context annotation, e.g. Sse and SseEventSink. Currently, JBoss Tools flags these with an error:
> {quote}
> @Context annotation is only allowed on method parameters of type '[javax.ws.rs.core.HttpHeaders, javax.ws.rs.core.UriInfo, javax.ws.rs.core.Request, javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, javax.servlet.ServletConfig, javax.servlet.ServletContext, javax.ws.rs.core.SecurityContext]'.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26040) Error for JAX-RS 2.1 @Context types
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26040?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-26040:
----------------------------------
Assignee: Jeff MAURY
> Error for JAX-RS 2.1 @Context types
> -----------------------------------
>
> Key: JBIDE-26040
> URL: https://issues.jboss.org/browse/JBIDE-26040
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.3.Final
> Reporter: Rich DiCroce
> Assignee: Jeff MAURY
>
> JAX-RS 2.1 adds some new types that can be injected into methods using the Context annotation, e.g. Sse and SseEventSink. Currently, JBoss Tools flags these with an error:
> {quote}
> @Context annotation is only allowed on method parameters of type '[javax.ws.rs.core.HttpHeaders, javax.ws.rs.core.UriInfo, javax.ws.rs.core.Request, javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, javax.servlet.ServletConfig, javax.servlet.ServletContext, javax.ws.rs.core.SecurityContext]'.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26042) shutting down ssp via cmdline shows tons of socket errors
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26042?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-26042:
--------------------------------
Fix Version/s: 4.6.0.AM2
> shutting down ssp via cmdline shows tons of socket errors
> ---------------------------------------------------------
>
> Key: JBIDE-26042
> URL: https://issues.jboss.org/browse/JBIDE-26042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM1
> Reporter: Rob Stryker
> Fix For: 4.6.0.AM2
>
>
> mvn clean install
> cd distribution/target
> unzip org.jboss.tools.ssp.distribution-0.0.9-SNAPSHOT.zip
> cd ssp-distribution
> java -jar bin/felix.jar
> Note following output:
> {code}
> API Bundle Started
> Launching Bundle Started
> Server bundle started
> The server management server is running on port 27511
> Wildfly Server bundle started
> Enter any character to stop
> ____________________________
> Welcome to Apache Felix Gogo
> {code}
> Then press enter. The server will shutdown, but will print tons of garbage about sockets trying to reconnect. This is because the attempt to connect to clients is in a loop with a while(true) (HA).
> Easy fix: let it know when it's time to shutdown and to stop attempting to receive connections.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months