January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12249) A lot of failures to install from marketplace.eclipse.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12249?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12249: ------------------------------- Attachment: JBIDE12249-upversion-to-1.3.2.patch.txt Ran this: {code} #!/bin/bash if [[ ! $1 ]]; then echo "Must specify new version, eg., $0 1.0.1"; exit fi export JAVA_HOME=/opt/sun-java2-6.0/; nice -n19 /opt/maven3/bin/mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=${1}-SNAPSHOT $2 $3 $4 {code} Got this: [^JBIDE12249-upversion-to-1.3.2.patch.txt] [~maxandersen], [~fbricon], please review and +1 so I can apply it. Seems excessive to bump **everything** in the maven component to 1.3.2, but as Max stated via email "As we have always done: the whole thing bumps .z" > A lot of failures to install from marketplace.eclipse.org > --------------------------------------------------------- > > Key: JBIDE-12249 > URL: https://issues.jboss.org/browse/JBIDE-12249 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, QA > Affects Versions: 3.3.0.Final > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Fix For: 3.3.2 > > Attachments: JBIDE12249-Indigo-installs-dropping.png, JBIDE12249-jbds6-byoe-installs-rising.png, JBIDE12249-jbt4-installs-rising.png, JBIDE12249-m2e1.2-install-conflict.png, JBIDE12249-upversion-to-1.3.2.patch.txt, JBIDE12249.patch.txt > > > It appears that most installations of JBT from marketplace concludes in an error: > See: http://marketplace.eclipse.org/content/jboss-tools-indigo/error_reports > Some of the most frequent errors: > {quote} > Cannot satisfy dependency: From: JBoss JAX-RS Tooling (UI) 1.2.2.v20120605-1934-H134-CR1 (org.jboss.tools.ws.jaxrs.ui 1.2.2.v20120605-1934-H134-CR1) To: bundle org.eclipse.debug.ui 3.7.101 > {quote} > -> JaxRs depends on 3.7.1 ? Install from 3.7.0 or <. > {quote} > JBoss Maven Integration 1.3.0.v20120613-2141-H115-Final (org.jboss.tools.maven.ui 1.3.0.v20120613-2141-H115-Final) To: bundle org.eclipse.compare 3.5.202 > {quote} > -> Maven depends on 3.7.2 ? > {quote} > Cannot satisfy dependency: From: OpenShift UI 2.3.0.v20120613-1951-H135-Final (org.jboss.tools.openshift.express.ui 2.3.0.v20120613-1951-H135-Final) To: bundle org.eclipse.egit.ui [1.0.0,2.0.0) > {quote} > -> People who don't have EGit. EGit is not part of our site. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13315) Text selection in VPE source pane is not synchronized with selection in Visual Pane

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13315?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13315: ---------------------------------------- Fix Version/s: 4.0.x (was: 3.3.2) > Text selection in VPE source pane is not synchronized with selection in Visual Pane > ----------------------------------------------------------------------------------- > > Key: JBIDE-13315 > URL: https://issues.jboss.org/browse/JBIDE-13315 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 3.3.2 > Environment: Linux 32bit JBDS Version: 5.0.2.GA Build id: v20121213-1624-H235-GA Build date: 20121213-1624 > Reporter: Vlado Pakan > Assignee: Yahor Radtsevich > Fix For: 4.0.x > > > Steps to reproduce: > 1. Open any jsp page in VPE editor and select some text in VPE source pane. The same text is selected in visual pane. > 2. Make mouse left click somewhere in visual pane. There should be no selected text. > 3. Select the same text in step 1. via source pane > 4. No text is selected in visual pane but the same text selected in source pane has to be selected in visual pane. > After reopening jsp page it's working again as mentioned above. Selection is synchronized only first time. > See screencast attached to original issue. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2395) Investigate use of SpringIDE 3.x in JBoss 6.x Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2395?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2395: ----------------------------- Fix Version/s: 6.0.1.GA > Investigate use of SpringIDE 3.x in JBoss 6.x Central > ----------------------------------------------------- > > Key: JBDS-2395 > URL: https://issues.jboss.org/browse/JBDS-2395 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 6.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 6.0.1.GA, 7.0.0.Alpha1 > > > As reported in JBDS-2280, there are two problems with Spring IDE 3.0: > * [IDE-1263|https://jira.springsource.org/browse/IDE-1263] - fixed in 3.1.0 > * [IDE-1264|https://jira.springsource.org/browse/IDE-1264] - fixed in 3.2.0.M1 > Cannot find a site w/ a 3.2.0 milestone on it (yet), but did find these: > https://dist.springframework.org/milestone/IDE/ – 3.1.0.201209120646-M1 (maybe misnamed?) > http://dist.springframework.org/snapshot/IDE/nightly/ – 3.2.0.201211201813-CI-B170 > Also, 3.1.0 release version is currently on Eclipse Marketplace. > Suggest we wait until they release 3.2.0 in March and include it then in our next release. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12347) Unable to invoke SOAP web service when using Java 7

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12347?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12347: ---------------------------------------- Fix Version/s: 4.0.1.Final (was: 3.3.2) > Unable to invoke SOAP web service when using Java 7 > --------------------------------------------------- > > Key: JBIDE-12347 > URL: https://issues.jboss.org/browse/JBIDE-12347 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.1 > Environment: Java 7 > Reporter: Jaroslav Jankovič > Assignee: Brian Fitzpatrick > Fix For: 4.0.1.Final > > > I am unable to invoke SOAP web service in WS Tester from http://www.webservicex.net/BibleWebservice.asmx?WSDL. > In Response Body of WS Tester I got the message: > {code} > javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . > at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() > at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) > at System.Web.Services.Protocols.SoapServerProtocol.Initialize() > at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) > {code} > In error log I got the error: > {code} > java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . > at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() > at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) > at System.Web.Services.Protocols.SoapServerProtocol.Initialize() > at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) > at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1803) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1789) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1706) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . > at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() > at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) > at System.Web.Services.Protocols.SoapServerProtocol.Initialize() > at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) > at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) > at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111) > at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450) > at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381) > at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502) > at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12347) Unable to invoke SOAP web service when using Java 7

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12347?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12347: --------------------------------------------- move of 3.3.2 since edgecase. > Unable to invoke SOAP web service when using Java 7 > --------------------------------------------------- > > Key: JBIDE-12347 > URL: https://issues.jboss.org/browse/JBIDE-12347 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 3.3.1 > Environment: Java 7 > Reporter: Jaroslav Jankovič > Assignee: Brian Fitzpatrick > Fix For: 4.0.1.Final > > > I am unable to invoke SOAP web service in WS Tester from http://www.webservicex.net/BibleWebservice.asmx?WSDL. > In Response Body of WS Tester I got the message: > {code} > javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . > at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() > at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) > at System.Web.Services.Protocols.SoapServerProtocol.Initialize() > at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) > {code} > In error log I got the error: > {code} > java.lang.Exception: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . > at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() > at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) > at System.Web.Services.Protocols.SoapServerProtocol.Initialize() > at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) > at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1803) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1789) > at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1706) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: . > at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() > at System.Web.Services.Protocols.SoapServerProtocol.RouteRequest(SoapServerMessage message) > at System.Web.Services.Protocols.SoapServerProtocol.Initialize() > at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing) > at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) > at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:111) > at com.sun.xml.internal.ws.client.dispatch.DispatchImpl$DispatchAsyncInvoker$1.onCompletion(DispatchImpl.java:450) > at com.sun.xml.internal.ws.client.Stub$1.onCompletion(Stub.java:381) > at com.sun.xml.internal.ws.api.pipe.Fiber.completionCheck(Fiber.java:502) > at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:420) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2395) Investigate use of SpringIDE 3.x in JBoss 6.x Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2395?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2395: ---------------------------------- Since 3.2.0 is due in March, we could *consider* including this update in JBDS 6 Central as well as JBDS 7, if the dates line up and QE is OK with that. > Investigate use of SpringIDE 3.x in JBoss 6.x Central > ----------------------------------------------------- > > Key: JBDS-2395 > URL: https://issues.jboss.org/browse/JBDS-2395 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 6.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 6.0.1.GA, 7.0.0.Alpha1 > > > As reported in JBDS-2280, there are two problems with Spring IDE 3.0: > * [IDE-1263|https://jira.springsource.org/browse/IDE-1263] - fixed in 3.1.0 > * [IDE-1264|https://jira.springsource.org/browse/IDE-1264] - fixed in 3.2.0.M1 > Cannot find a site w/ a 3.2.0 milestone on it (yet), but did find these: > https://dist.springframework.org/milestone/IDE/ – 3.1.0.201209120646-M1 (maybe misnamed?) > http://dist.springframework.org/snapshot/IDE/nightly/ – 3.2.0.201211201813-CI-B170 > Also, 3.1.0 release version is currently on Eclipse Marketplace. > Suggest we wait until they release 3.2.0 in March and include it then in our next release. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2395) Investigate use of SpringIDE 3.x in JBoss 6.x Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2395?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2395: ----------------------------- Assignee: Len DiMaggio (was: Nick Boldt) > Investigate use of SpringIDE 3.x in JBoss 6.x Central > ----------------------------------------------------- > > Key: JBDS-2395 > URL: https://issues.jboss.org/browse/JBDS-2395 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification, 3rdPartyDependencies, central > Affects Versions: 6.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 6.0.1.GA, 7.0.0.Alpha1 > > > As reported in JBDS-2280, there are two problems with Spring IDE 3.0: > * [IDE-1263|https://jira.springsource.org/browse/IDE-1263] - fixed in 3.1.0 > * [IDE-1264|https://jira.springsource.org/browse/IDE-1264] - fixed in 3.2.0.M1 > Cannot find a site w/ a 3.2.0 milestone on it (yet), but did find these: > https://dist.springframework.org/milestone/IDE/ – 3.1.0.201209120646-M1 (maybe misnamed?) > http://dist.springframework.org/snapshot/IDE/nightly/ – 3.2.0.201211201813-CI-B170 > Also, 3.1.0 release version is currently on Eclipse Marketplace. > Suggest we wait until they release 3.2.0 in March and include it then in our next release. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1943) Opening Dependency Graph in Spring Explorer through some bean is not working

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-1943?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-1943. ---------------------------- Resolution: Won't Fix Not fixing SpringIDE 2.x issues in JBDS 5. Plan is to include SpringIDE 3.something in JBDS 7. Probably. > Opening Dependency Graph in Spring Explorer through some bean is not working > ---------------------------------------------------------------------------- > > Key: JBDS-1943 > URL: https://issues.jboss.org/browse/JBDS-1943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification > Affects Versions: 5.0.0.M4 > Reporter: Jaroslav Jankovič > Assignee: Len DiMaggio > Fix For: 5.0.2.GA > > > https://jira.springsource.org/browse/IDE-1227 -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13336?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13336: ---------------------------------------- Current target: https://github.com/mickaelistria/jbosstools-build/blob/JBIDE-13336/target... [~nickboldt]: I'd like to merge it from now on (as a SNAPSHOT) so it gets ready to consume in IDE, and also I'd like to push a first SNAPSHOT to Nexus to ask developers to give it a try and collect feedback. {code} mvn clean verify -P multiple.target -DTARGET_PLATFORM_VERSION=4.3.0.M4-SNAPSHOT {code} > create target platform using Kepler dependencies > ------------------------------------------------ > > Key: JBIDE-13336 > URL: https://issues.jboss.org/browse/JBIDE-13336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > Attachments: multiple.target, multiple.target_update_hints.txt > > > Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. > I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: > http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... > http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... > Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-1942) Beans Cross Reference view is not working

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-1942?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-1942. ---------------------------- Resolution: Won't Fix Not fixing SpringIDE 2.x issues in JBDS 5. Plan is to include SpringIDE 3.something in JBDS 7. Probably. > Beans Cross Reference view is not working > ----------------------------------------- > > Key: JBDS-1942 > URL: https://issues.jboss.org/browse/JBDS-1942 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rdPartyCertification > Affects Versions: 5.0.0.M4 > Reporter: Jaroslav Jankovič > Assignee: Len DiMaggio > Priority: Critical > Fix For: 5.0.2.GA > > > https://jira.springsource.org/browse/IDE-1226 -- 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

13 years, 6 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 January 2013