April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21876) Cannot deploy docker image to OpenShift with manually entered details

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21876?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21876. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > Cannot deploy docker image to OpenShift with manually entered details > --------------------------------------------------------------------- > > Key: JBIDE-21876 > URL: https://issues.jboss.org/browse/JBIDE-21876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: manually_filled.png, Screenshot 2016-03-03 11.14.38.png, selected_image.png > > > When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). > There is no error in error log. > Manually filled in details screenshot: > !manually_filled.png! > Automatically filled details via selecting a specific image screenshot: > !selected_image.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-731) Update: JBDS IS 9.0.0 GA Install Guide

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-731?page=com.atlassian.jira.plug... ] Supriya Bharadwaj reassigned TOOLSDOC-731: ------------------------------------------ Assignee: Andrej Podhradsky (was: Supriya Bharadwaj) > Update: JBDS IS 9.0.0 GA Install Guide > -------------------------------------- > > Key: TOOLSDOC-731 > URL: https://issues.jboss.org/browse/TOOLSDOC-731 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: Installation Guide > Reporter: Supriya Bharadwaj > Assignee: Andrej Podhradsky > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-682) Fix bugs in the Guides Test

by Matej Kralik (JIRA)

Matej Kralik created JBTIS-682: ---------------------------------- Summary: Fix bugs in the Guides Test Key: JBTIS-682 URL: https://issues.jboss.org/browse/JBTIS-682 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE, teiid Affects Versions: 4.3.0.Beta1 Reporter: Matej Kralik Assignee: Matej Kralik -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21581) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21581?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21581. ------------------------------- Verified in 4.4.0.Alpha1 > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21581 > URL: https://issues.jboss.org/browse/JBIDE-21581 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20976) Create and use Neon M4 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-20976. ------------------------------- Closing as done. > Create and use Neon M4 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, p2diff.jbdevstudio.neonm4.txt, p2diff.jbdevstudio.neonm4_latest.txt, p2diff.jbdevstudio_v2.txt, p2diff.jbosstools.neonm4.txt, p2diff.jbosstools.neonm4_latest.txt, p2diff.jbosstools.txt, p2diff.jbtcentral.neonM4.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-731) Update: JBDS IS 9.0.0 GA Install Guide

by Supriya Bharadwaj (JIRA)

Supriya Bharadwaj created TOOLSDOC-731: ------------------------------------------ Summary: Update: JBDS IS 9.0.0 GA Install Guide Key: TOOLSDOC-731 URL: https://issues.jboss.org/browse/TOOLSDOC-731 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Components: Installation Guide Reporter: Supriya Bharadwaj Assignee: Supriya Bharadwaj -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21985) Unexpected JAX-RS validation error for client filters

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21985?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21985. ------------------------------- Verified in 10.0.0.Alpha1 B5240. > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-21985 > URL: https://issues.jboss.org/browse/JBIDE-21985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.4.0.Alpha1 > > > 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 (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22255: ------------------------------------- Summary: Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 Key: JBIDE-22255 URL: https://issues.jboss.org/browse/JBIDE-22255 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Marián Labuda When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. Example: I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22255: ---------------------------------- Priority: Minor (was: Major) > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, ux > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22255: ---------------------------------- Labels: openshift_v3 ux (was: ) > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3, ux > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016