June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14773) org.eclipse.ecf.provider.filetransfer.httpclient removed from Kepler, so use new org.eclipse.ecf.provider.filetransfer.httpclient4 bundle instead

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-14773: ---------------------------------- Summary: org.eclipse.ecf.provider.filetransfer.httpclient removed from Kepler, so use new org.eclipse.ecf.provider.filetransfer.httpclient4 bundle instead Key: JBIDE-14773 URL: https://issues.jboss.org/browse/JBIDE-14773 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.1.0.Beta2 Reporter: Nick Boldt In Kepler M7 [0], there were two similar bundles: * org.eclipse.ecf.provider.filetransfer.*httpclient* 4.0 * org.eclipse.ecf.provider.filetransfer.*httpclient4* 1.0 Now, in RC2 [1], the *httpclient* plugin is no more, so we need to use the newer *httpclient4* jar instead. [0] http://download.jboss.org/jbosstools/updates/requirements/kepler/20130510... [1] http://download.jboss.org/jbosstools/updates/requirements/kepler/20130530... Affected files: https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... (possibly others?) Reported installation problem: https://community.jboss.org/message/821652 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14729) Move to Kepler RC2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14729?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14729: ------------------------------------ Missed updating Kepler M7 -> RC2, so fixed that here: https://github.com/jbosstools/jbosstools-target-platforms/pull/4 Also put pack the org.eclipse.update.core requirement, just in case (because insufficient testing done, so might as well include it). Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ... >112 > Move to Kepler RC2 > ------------------ > > Key: JBIDE-14729 > URL: https://issues.jboss.org/browse/JBIDE-14729 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta2 > > > Use Kepler RC2 in TP 4.30.5.Alpha6-SNAPSHOT and build master against it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2653) Can't update m2e-wtp to latest version in JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2653?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-2653. ------------------------------ Assignee: Fred Bricon Resolution: Done Fixed (pending respin). Assigning to [~fbricon] to verify and close. > Can't update m2e-wtp to latest version in JBDS > ---------------------------------------------- > > Key: JBDS-2653 > URL: https://issues.jboss.org/browse/JBDS-2653 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, maven > Affects Versions: 7.0.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 7.0.0.Beta2 > > Attachments: jbds2653-updated-m2e-in-beta2.png > > > {quote} > [19:26] <@fbricon> using latest JBDS beta1, I can't upgrade m2e-wtp to the version sitting in http://download.eclipse.org/m2e-wtp/milestones/kepler/1.0.0/1.0.0.2013060... > [19:26] <@fbricon> though it seems JPA, JAXRS and JSF features can be updated > [19:27] <@fbricon> nboldt: that can't be a range restriction from the features/plugins in central, otherwise m2e-wtp 1.0.0 wouldn't be installed in JBDS at all > [19:28] <@fbricon> nboldt: m2e itself can be updated > {quote} > I can see the remediation screen and some option seems to be to uninstall JBDS to fix the issue. I also found the original error message buried in the UI : > {noformat} > Your original request has been modified. > "m2e-wtp - Maven Integration for WTP (Incubation)" is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618) > Software currently installed: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257) > Only one of the following can be installed at once: > Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130507-1357) > Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130528-1157 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130528-1157) > Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130604-1618) > Cannot satisfy dependency: > From: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257) > To: com.jboss.jbds.product.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257] > Cannot satisfy dependency: > From: Maven Integration (Selected) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.m2e.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257) > To: org.eclipse.m2e.wtp.feature.feature.group [1.0.0.20130507-1357] > Cannot satisfy dependency: > From: JBoss Developer Studio (Core Features) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.product.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257) > To: com.jboss.jbds.m2e.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257] > Cannot satisfy dependency: > From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130507-1357) > To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130507-1357] > Cannot satisfy dependency: > From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618) > To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130604-1618] > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14770) Missing components when JBT 4.1.Beta1 is installed via Marketplace

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14770?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14770: ------------------------------------- mmm do we really want to add the GWT stuff here? > Missing components when JBT 4.1.Beta1 is installed via Marketplace > ------------------------------------------------------------------ > > Key: JBIDE-14770 > URL: https://issues.jboss.org/browse/JBIDE-14770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.1.0.Beta1 > Reporter: Jiri Peterka > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Beta1 > > Attachments: jbide14770.png > > > Missing components when JBT 4.1.Beta1 is installed via Marketplace, specifially: > Some of them might be intentional: > - Arquillian support (Experimental) 1.0.4.Beta1-v20130518-2210-B3 > - Forge Tools Extensions (Forge 2.0 Support - Experimental) 1.0.0.Beta1-v20130524-1739-B66 > - JBoss BIRT Integration 1.5.0.Beta1-v20130518-0411-B36 > - JBoss Central - UI Themes for Eclipse 1.2.0.Beta1-v20130523-1233-B39 > - JBoss GWT Integration (Experimental) 1.1.0.Final-v20130205-2223-B78 > - JBoss Maven GWT Configurator 1.5.0.Beta1-v20130523-1233-B39 > - JBoss Mobile Hybrid Application Development Tools (Experimental) 1.0.0.Beta1-v20130523-2211-B7 > - JBoss Tools Apache Cordova Simulator 3.5.0.Beta1-v20130525-0825-B60 > - JBoss Tools Common - Mylyn 3.5.0.Beta1-v20130525-0108-B68 > - JBoss Tools LiveReload 1.0.0.Beta1-v20130524-1307-B28 > - Maven Integration for Eclipse JDT APT 1.0.1.201209200721 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2653) Can't update m2e-wtp to latest version in JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2653?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2653: ----------------------------- Attachment: jbds2653-updated-m2e-in-beta2.png 1. Applied this: https://github.com/jbdevstudio/jbdevstudio-product/pull/1 2. Built locally 3. Installed JBDS from installer; launched it in a new workspace. 4. Help > Install > http://download.eclipse.org/m2e-wtp/milestones/kepler/1.0.0/1.0.0.2013060... > select all > install > restart 5. Result: !jbds2653-updated-m2e-in-beta2.png! 7. Applied PR in master. 8. Respinning for Beta2 in master branch: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_ma... >=82 > Can't update m2e-wtp to latest version in JBDS > ---------------------------------------------- > > Key: JBDS-2653 > URL: https://issues.jboss.org/browse/JBDS-2653 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, maven > Affects Versions: 7.0.0.Beta1 > Reporter: Fred Bricon > Fix For: 7.0.0.Beta2 > > Attachments: jbds2653-updated-m2e-in-beta2.png > > > {quote} > [19:26] <@fbricon> using latest JBDS beta1, I can't upgrade m2e-wtp to the version sitting in http://download.eclipse.org/m2e-wtp/milestones/kepler/1.0.0/1.0.0.2013060... > [19:26] <@fbricon> though it seems JPA, JAXRS and JSF features can be updated > [19:27] <@fbricon> nboldt: that can't be a range restriction from the features/plugins in central, otherwise m2e-wtp 1.0.0 wouldn't be installed in JBDS at all > [19:28] <@fbricon> nboldt: m2e itself can be updated > {quote} > I can see the remediation screen and some option seems to be to uninstall JBDS to fix the issue. I also found the original error message buried in the UI : > {noformat} > Your original request has been modified. > "m2e-wtp - Maven Integration for WTP (Incubation)" is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618) > Software currently installed: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257) > Only one of the following can be installed at once: > Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130507-1357) > Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130528-1157 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130528-1157) > Overlay support for Eclipse WTP - UI (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.overlay.ui 1.0.0.20130604-1618) > Cannot satisfy dependency: > From: JBoss Developer Studio (Branded Product) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.all 7.0.0.Beta1-v20130529-0631-B257) > To: com.jboss.jbds.product.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257] > Cannot satisfy dependency: > From: Maven Integration (Selected) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.m2e.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257) > To: org.eclipse.m2e.wtp.feature.feature.group [1.0.0.20130507-1357] > Cannot satisfy dependency: > From: JBoss Developer Studio (Core Features) 7.0.0.Beta1-v20130529-0631-B257 (com.jboss.jbds.product.feature.feature.group 7.0.0.Beta1-v20130529-0631-B257) > To: com.jboss.jbds.m2e.feature.feature.group [7.0.0.Beta1-v20130529-0631-B257] > Cannot satisfy dependency: > From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130507-1357) > To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130507-1357] > Cannot satisfy dependency: > From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130604-1618 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130604-1618) > To: org.eclipse.m2e.wtp.overlay.ui [1.0.0.20130604-1618] > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14741) Have show in > Cheat sheets work at project level

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14741?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-14741: ------------------------------------- Assignee: Max Rydahl Andersen (was: Snjezana Peco) > Have show in > Cheat sheets work at project level > ------------------------------------------------- > > Key: JBIDE-14741 > URL: https://issues.jboss.org/browse/JBIDE-14741 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta2 > > > If a project has a cheatsheet etc. we recognize on project open users should be able to right click the Project and do Show in Cheat sheets. > This is to avoid TOOLSDOC-336 where users have to make .cheatsheet visible to find the cheatsheet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13527) [tester] freeze parsing wsdl

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13527?page=com.atlassian.jira.plugi... ] Alessio Soldano commented on JBIDE-13527: ----------------------------------------- To get the namespace of the service, you need to look at the 'name' attribute of the wsdl:service elements. In there, unless a specific namespace prefix is specified, the target namespace of wsdl applies. So, either get the 'targetNamespace' attribute of wsdl:definitions element or the xmlns:xyz attribute for the xyz prefix you might have found. > [tester] freeze parsing wsdl > ---------------------------- > > Key: JBIDE-13527 > URL: https://issues.jboss.org/browse/JBIDE-13527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.2.Final > Reporter: Alessio Soldano > Assignee: Brian Fitzpatrick > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: jaxws-complex.war, threaddump.txt > > > JBT freezes when the ws tester is used to consume the wsdl contract for the jaxws-complex.war test deployment of JBossWS testsuite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13527) [tester] freeze parsing wsdl

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13527?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13527: ------------------------------------------- Ok, so the SOAP message is generated fine apparently. The issue seems to be with how I'm getting the namespace URL from the WSDL. Basically what I do is grab the javx.wsdl.Definition and work my way through to find the service and port I'm looking for (in this case RegistrationServiceImpService and RegistrationServiceImplPort), then grab the binding associated with the port, the port type associated with the binding, and the namespace of the port type. (You can see my code below.) The namespace associated with the port type in this case is the incorrect ns (xmlns:ns1="http://types.complex.jaxws.ws.test.jboss.org/"), which is not the tns of the wsdl itself (xmlns:tns="http://complex.jaxws.ws.test.jboss.org"). Which namespace URI should I be grabbing to execute the test against? I need the ns url to create the java.xml.ws.Service I'm using to generate the SOAPMessage... {code} public static String[] getNSServiceNameAndMessageNameArray (Definition wsdlDefinition, String serviceName, String portName, String bindingName, String opName ) { Map<?, ?> services = wsdlDefinition.getServices(); Set<?> serviceKeys = services.keySet(); for( Iterator<?> it = serviceKeys.iterator(); it.hasNext(); ) { QName serviceKey = (QName) it.next(); if (serviceName != null && serviceKey.getLocalPart().contentEquals(serviceName)) { Service service = (Service) services.get( serviceKey ); Map<?, ?> ports = service.getPorts(); Set<?> portKeys = ports.keySet(); for( Iterator<?> it2 = portKeys.iterator(); it2.hasNext(); ) { String portKey = (String) it2.next(); if (portName != null && portKey.contentEquals(portName)) { Port port = (Port) ports.get( portKey ); Binding wsdlBinding = port.getBinding(); PortType portType = wsdlBinding.getPortType(); String ns = portType.getQName().getNamespaceURI(); List<?> operations = portType.getOperations(); for (Iterator<?> it3 = operations.iterator(); it3.hasNext();){ Operation operation = (Operation) it3.next(); if (opName != null && operation.getName().contentEquals(opName)) { return new String[] {ns, serviceName, portName}; } } } } } } return null; } {code} > [tester] freeze parsing wsdl > ---------------------------- > > Key: JBIDE-13527 > URL: https://issues.jboss.org/browse/JBIDE-13527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.2.Final > Reporter: Alessio Soldano > Assignee: Brian Fitzpatrick > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > Attachments: jaxws-complex.war, threaddump.txt > > > JBT freezes when the ws tester is used to consume the wsdl contract for the jaxws-complex.war test deployment of JBossWS testsuite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14772) remove "experimental" from EAP 6.1

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-14772: ------------------------------------------- Summary: remove "experimental" from EAP 6.1 Key: JBIDE-14772 URL: https://issues.jboss.org/browse/JBIDE-14772 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Reporter: Max Rydahl Andersen Fix For: 4.1.0.Beta2 EAP 6.1 is released we should remove the experimental tag -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14760) Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14760?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14760: ------------------------------------- Bugzilla Update: (was: Perform) > Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-14760 > URL: https://issues.jboss.org/browse/JBIDE-14760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Environment: jdk7 > Reporter: jing zh > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > Attachments: JBT_test.png > > > If trying to connect openshift server ,it would be failed with following error shown. > Could not verify credentials for jinzhang1: Could not request https://broker.osetestv2.com/broker/rest/api: javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 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 June 2013