[JBoss JIRA] (JBIDE-25669) Unexpected JAX-RS validation error for Feature
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25669?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25669:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.3.AM2)
> Unexpected JAX-RS validation error for Feature
> ----------------------------------------------
>
> Key: JBIDE-25669
> URL: https://issues.jboss.org/browse/JBIDE-25669
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.5.2.Final
> Reporter: Cody Lerum
> Assignee: Jeff MAURY
> Labels: jax-rs, respin-a
> Fix For: 4.5.x
>
>
> We are using JAX-RS client filters in our project. One of the classes looks like this:
> ...
> import java.io.IOException;
> import javax.ws.rs.client.ClientRequestContext;
> import javax.ws.rs.client.ClientRequestFilter;
> import javax.ws.rs.ext.Provider;
> ...
> @Provider
> public class ClientFilter implements ClientRequestFilter
> {
> ...
> }
> The class is part of a Dynamic Web Project with JAX-RS support turned on.
> The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error:
> The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver.
> I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25755) Delete Resources: Search filter does not show correct results
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25755?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25755.
---------------------------------
Closing: Usecase 1. is fixed and usecase 2. is tracked in different JIRA: Please see linked JIRAs.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.AM2
Build id: AM2-v20180301-2015-B2134
Build date: 20180301-2015
> Delete Resources: Search filter does not show correct results
> -------------------------------------------------------------
>
> Key: JBIDE-25755
> URL: https://issues.jboss.org/browse/JBIDE-25755
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM2
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM2
>
> Attachments: afterChangingFilter.png, afterOpening.png
>
>
> Delete resources filter does not work as expected - there are 2 use cases:
> 1. After opening wizard there are shown also *Secret* type resources:
> !afterOpening.png|thumbnail!
> , but after changing filter a deleting it, *Secret*s are not shown:
> !afterChangingFilter.png|thumbnail!
> 2. In my opinion *Label filter* should also work for columns *Name* and *Type*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25762) Delete Resources: removing character off filter expression wont update "selection" in matching label portions
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25762?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25762.
---------------------------------
Looks good to me. Closing.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.AM2
Build id: AM2-v20180301-2015-B2134
Build date: 20180301-2015
> Delete Resources: removing character off filter expression wont update "selection" in matching label portions
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25762
> URL: https://issues.jboss.org/browse/JBIDE-25762
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: delete_resources
> Fix For: 4.5.3.AM2
>
>
> # ASSERT: have a project with resources
> # EXEC: open up "Delete Resources" wizard
> # EXEC: enter a filter expression that contains several characters
> # ASSERT: only resources with matching filter are listed, matching label parts are highlighted
> # EXEC: remove a character from the filter expression
> Result:
> highlighted ("selected") label part in the "Labels" column is *NOT* updated.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ERT-580) Upgrade Batik version in Orbit to 1.9.1 [EBZ#522740]
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/ERT-580?page=com.atlassian.jira.plugin.sy... ]
Roland Grunberg reassigned ERT-580:
-----------------------------------
Assignee: Roland Grunberg
> Upgrade Batik version in Orbit to 1.9.1 [EBZ#522740]
> ----------------------------------------------------
>
> Key: ERT-580
> URL: https://issues.jboss.org/browse/ERT-580
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Orbit
> Reporter: Nick Boldt
> Assignee: Roland Grunberg
> Labels: Photon_M5, bundles, bzira
> Fix For: Photon (4.8) M6
>
>
> The Oxygen Orbit R20170516192513 provides org.apache.batik.css versions 1.6.0, 1.7.0, 1.8.0; very reasonable.
> The latest Photon Orbit S20170912163609 provides org.apache.batik.css versions 1.6.0, 1.7.0, 1.9.0.
> What happened to 1.8.0? If there is an incompatibility, why hasn't it been announced on cross-project-dev.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25666) Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25666?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25666.
---------------------------------
Closing, no error message is shown.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.3.0.AM2
Build id: AM2-v20180301-2015-B2134
Build date: 20180301-2015
> Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-25666
> URL: https://issues.jboss.org/browse/JBIDE-25666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: build_log, oc_binary, preferences
> Fix For: 4.5.3.AM2
>
> Attachments: build-logs-using-oc-location-in-prefs.png
>
>
> # ASSERT: have the "oc" location set in Eclipse preferences
> # EXEC: start some build in OpenShift (ex. by creating an app via nodejs-mongo-persistent template)
> # EXEC: kill the oc that preferences is pointing to
> # EXEC: set the "Override oc location" for your OpenShift connection to some valid oc binary
> # EXEC: in Properties > Builds: select your build and pick "Build Log"
> Result:
> The "Console" view is opened but instead of the log you'll see the following error (<invalid path> is the path that you have set in preferences:
> {code}
> Does your OpenShift binary location exist? Error starting process: Cannot run program <invalid path to oc from Eclipse preferences>: error=2, No such file or directory
> {code}
> !build-logs-using-oc-location-in-prefs.png!
> "Build Logs" obviously doesnt honour the oc location override for the connection, it is using the value in the Eclipse preferences.
> Expected result:
> The "Build Log" should use the override in the Connection and show the build log
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25771) Update Docker Tooling to 3.2.1
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25771?page=com.atlassian.jira.plugi... ]
Jeff Johnston commented on JBIDE-25771:
---------------------------------------
The Mar 1st build has the deadlock patch according to Jenkins. If you already took the Mar 1st build and seeing a deadlock then there is an additional issue. I did fix a deadlock with the close method whereby it was holding two locks in opposite order of the Refresh Manager. That no longer occurs. I intend to build the RC4 (final release) of Linux tools 6.2.1 today with latest CDT. I have already kicked off a new build, but I also need to check if any user guides need updating before the final aggregation tomorrow. Any of these builds should have the fix if you do not wish to wait until tomorrow.
> Update Docker Tooling to 3.2.1
> ------------------------------
>
> Key: JBIDE-25771
> URL: https://issues.jboss.org/browse/JBIDE-25771
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: docker, target-platform
> Affects Versions: 4.5.3.AM2
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM3
>
>
> Please update Docker Tooling to latest version to include this patch:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=531883
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25556) OpenJDK9 + org.jboss.tools.common: java.lang.Exception: No valid JDK found
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25556?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25556:
-------------------------------------
https://github.com/jbosstools/jbosstools-base/pull/611
> OpenJDK9 + org.jboss.tools.common: java.lang.Exception: No valid JDK found
> ---------------------------------------------------------------------------
>
> Key: JBIDE-25556
> URL: https://issues.jboss.org/browse/JBIDE-25556
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.5.2.AM3
> Environment: FC27 + OpenJDK9
> Reporter: Josef Kopriva
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> Error message from error log:
> {code:java}
> eclipse.buildId=11.2.0.AM3-v20180105-1612-B1822
> java.version=9.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/devstudio_B1822-Java9-2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.common.jdt.debug
> Error
> Thu Jan 11 10:45:50 CET 2018
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.base/java.util.TimerThread.mainLoop(Timer.java:556)
> at java.base/java.util.TimerThread.run(Timer.java:506)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month