[JBoss JIRA] (JBIDE-26453) Adapters/vscode-openshift tooling onboarding
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26453?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26453:
-------------------------------
Sprint: devex #157 November 2019, devex #159 December 2018, devex #161 January 2019, devex #162 February 2020 (was: devex #157 November 2019, devex #159 December 2018, devex #161 January 2019)
> Adapters/vscode-openshift tooling onboarding
> --------------------------------------------
>
> Key: JBIDE-26453
> URL: https://issues.jboss.org/browse/JBIDE-26453
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.10.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: integration-test, quality
> Fix For: 4.11.0.AM1
>
>
> Jump in adapters stuff:
> * go through repos, get familiar with plugins
> * start exploring locally, build it, run it
> * pick up github issues and start implementing in typescript/java
> * increase unit tests coverage
> * get familiar with infrastructure
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26454) Proxy usage within QE teams, needs and requirements for deploying
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26454?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26454:
-------------------------------
Sprint: devex #159 December 2018, devex #161 January 2019, devex #162 February 2020 (was: devex #159 December 2018, devex #161 January 2019)
> Proxy usage within QE teams, needs and requirements for deploying
> -----------------------------------------------------------------
>
> Key: JBIDE-26454
> URL: https://issues.jboss.org/browse/JBIDE-26454
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.10.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: quality
> Fix For: 4.11.0.AM1
>
>
> Find out:
> * existing solutions within RH
> * needs of other teams
> * usability of open source proxy technologies/solutions
> * usage among different OS
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26506) Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26506?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26506:
-------------------------------
Sprint: devex #161 January 2019, devex #162 February 2020 (was: devex #161 January 2019)
> Remediation page showing up when installing RHAMT from central - missing org.eclipse.emf.transaction
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26506
> URL: https://issues.jboss.org/browse/JBIDE-26506
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, central-update
> Affects Versions: 4.11.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.11.x
>
>
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final)
> Missing requirement: Model 4.2.0.Final (org.jboss.tools.windup.model 4.2.0.Final) requires 'osgi.bundle; org.eclipse.emf.transaction 0.0.0' but it could not be found
> Cannot satisfy dependency:
> From: RHAMT 4.2.0.Final (org.jboss.tools.windup.feature.feature.group 4.2.0.Final)
> To: org.eclipse.equinox.p2.iu; org.jboss.tools.windup.model [4.2.0.Final,4.2.0.Final]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 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 updated JBIDE-25669:
-------------------------------
Sprint: devex #145 February 2018, devex #161 January 2019, devex #162 February 2020 (was: devex #145 February 2018, devex #161 January 2019)
> 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
> Priority: Major
> Labels: jax-rs, respin-a
> Fix For: 4.11.0.AM1
>
>
> 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.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-25814:
----------------------------------
Sprint: devex #162 February 2020 (was: devex #161 January 2019)
> Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25814
> URL: https://issues.jboss.org/browse/JBIDE-25814
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Josef Kopriva
> Priority: Major
> Labels: server_adapter_wizard
> Fix For: 4.11.0.AM1
>
>
> steps:
> # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online)
> # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application
> # ASSERT: Connection selection page pops up
> # EXEC: select your 2nd connection, get to the next page. But then, cancel the wizard, dont get any further.
> # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter
> # ASSERT: Connection selection page pops up
> Result:
> the connection selection page has the 1st connection selected, not the one that we used most recently.
> (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently)
> Bonus: some wizards even inspect the currently selected element in the OpenShift Explorer and deduce what they need. The server adapter wizard could inspect the resource that's selected and infer the connection from it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month