[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25504 at 2/15/18 11:17 AM:
--------------------------------------------------------------------
work in progress: [adding utility facet to springboot project dependencies|https://github.com/jbosstools/jbosstools-central/pull/420]
This patch for jbosstools-central is adding the utility facet to the dependencies of the springboot project, if those already exist in the workspace. It wont handle the case where one would import those dependencies to the workspace once the springboot project already exists (to be implemented).
was (Author: adietish):
work in progress: [adding utility facet to springboot project dependencies|https://github.com/jbosstools/jbosstools-central/pull/417]
This patch for jbosstools-central is adding the utility facet to the dependencies of the springboot project, if those already exist in the workspace. It wont handle the case where one would import those dependencies to the workspace once the springboot project already exists (to be implemented).
> Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25504
> URL: https://issues.jboss.org/browse/JBIDE-25504
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.3.AM2
>
> Attachments: springboot-dependencies.zip
>
>
> When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case:
> * the SpringBoot app has a dependency which is avalailable in the workspace
> * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[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 commented on JBIDE-25669:
------------------------------------
[~clerum] Can't reproduce using the helloworld-rs provided by Red Hat Central. Can you give the steps to reproduce ?
> 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.3.AM2
>
>
> 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-25736) deprecate features from JBoss Tools with low usage / low development
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-25736:
---------------------------------------
>From jbosstools-javaee we should keep at least jsf sub-module.
> deprecate features from JBoss Tools with low usage / low development
> --------------------------------------------------------------------
>
> Key: JBIDE-25736
> URL: https://issues.jboss.org/browse/JBIDE-25736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM2
>
>
> This issue is to consider deprecating the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
> * jbosstools-portlet
> * jbosstools-aerogear
> * jbosstools-browsersim
> * jbosstools-livereload
> * jbosstools-webservices
> * jbosstools-javaee
> * jbosstools-forge
> For supporting arguments, see this doc (RH only, sorry):
> https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25736) deprecate features from JBoss Tools with low usage / low development
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25736?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-25736:
---------------------------------------
Definitely +100 to keep jbosstools-forge (y)
> deprecate features from JBoss Tools with low usage / low development
> --------------------------------------------------------------------
>
> Key: JBIDE-25736
> URL: https://issues.jboss.org/browse/JBIDE-25736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim, build, cdi, forge, jsf, livereload, portal-gatein, seam2, webservices
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM2
>
>
> This issue is to consider deprecating the following parts of JBoss Tools. Suggest we mark them deprecated in feature.properties, and add/update connectors in Central to be similarly marked.
> * jbosstools-portlet
> * jbosstools-aerogear
> * jbosstools-browsersim
> * jbosstools-livereload
> * jbosstools-webservices
> * jbosstools-javaee
> * jbosstools-forge
> For supporting arguments, see this doc (RH only, sorry):
> https://docs.google.com/spreadsheets/d/1PTep1KGK2DVbmaWGwQOPhtbSsyROL_PY6...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month