January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2038) JBDS installer should open JBDS upon completion

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2038?page=com.atlassian.jira.plugin.... ] Daniel Azarov commented on JBDS-2038: ------------------------------------- Fred, you probably right! I googled "Installation Complete" images, most of such phrases look like "Launch <product>" I saw few cases with "Run" or "Start <product> now" I think we should do "Launch JBoss Developer Studio". > JBDS installer should open JBDS upon completion > ----------------------------------------------- > > Key: JBDS-2038 > URL: https://issues.jboss.org/browse/JBDS-2038 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 5.0.0.Beta1 > Environment: jbdevstudio-product-win32-x86_64-5.0.0.v201202250031M-H77-Beta1.jar > Reporter: Fred Bricon > Assignee: Denis Golovin > Fix For: 7.0.x > > Attachments: JBDS-2038.patch, RunJBDSAfterInstallation.png > > > As a user, once the JBDS installer completes, I expect it to open the newly installed JBDS. > On the last page of the installer, there should be a checkbox asking the user if he wants to open JBDS immediately. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ] Rob Cernich commented on JBIDE-13232: ------------------------------------- Hey Mickael, That makes sense, but I'd also say that's what SNAPSHOTs are for: evolution between releases. Once you release, you go from SNAPSHOT to Final. Also, just because you don't make changes doesn't mean you can't update the version. Think of parent poms that define configuration, dependencies and modules, if none of those change, between versions, you still roll the version on the parent. Anyway, no biggie, just providing some feedback. Best, Rob > refactor target platforms' GAVs, names, labels (was target platforms has the same name) > --------------------------------------------------------------------------------------- > > Key: JBIDE-13232 > URL: https://issues.jboss.org/browse/JBIDE-13232 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Environment: > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > Attachments: JBIDE13232.parent.pom.tweaks.txt > > > .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either. > Makes it hard to actually see which target platform to choose -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13283) Use Akamai for Target-Platform, Mirror, releases stuff

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13283?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13283: --------------------------------------------- Yes, we can only do this for things that have *additions*. Deletions and changes does not work well with Akamai. > Use Akamai for Target-Platform, Mirror, releases stuff > ------------------------------------------------------ > > Key: JBIDE-13283 > URL: https://issues.jboss.org/browse/JBIDE-13283 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least these folders would be good: > * http://download.jboss.org/jbosstools/updates/requirements/ > * http://download.jboss.org/jbosstools/updates/stable/ -- 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, 2 months

1
0
0 / 0

[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 resolved JBIDE-12249. -------------------------------- Resolution: Done Subtasks done. Verification requires that we put 3.3.2 onto Marketplace and watch that the install errors drop in # over time. Can also re-run the install tests to verify those are all blue. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stabl... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-3.3_stabl... > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13406) BrowserSim: Integrate firebug-lite

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13406?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13406: ------------------------------------------ JavaScript code to inject FireBug Lite: {code} var e = document.createElement('script'); e.type = 'text/javascript'; e.src = 'https://getfirebug.com/firebug-lite.js#startOpened=false'; document.head.appendChild(e); {code} Open/close FireBug Lite in a pop-up window: {code} Firebug.chrome.toggle(true, true); //Opens in pop-up, does not do anything if it is already opened Firebug.chrome.close(); //Closes pop-up, does not do anything if it is already closed {code} > BrowserSim: Integrate firebug-lite > ---------------------------------- > > Key: JBIDE-13406 > URL: https://issues.jboss.org/browse/JBIDE-13406 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Affects Versions: 4.1.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Alpha1 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2450) No Error reported when WS Client code generation fails

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2450?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-2450: --------------------------------- Description: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: bq.Failed to invoke WSDLToJava org.apache.cxf.tools.common.ToolException: Thrown by JAXB: Thrown by JAXB: Two declarations cause a collision in the ObjectFactory class. ... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. was: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: bq. Failed to invoke WSDLToJava org.apache.cxf.tools.common.ToolException: Thrown by JAXB: Thrown by JAXB: Two declarations cause a collision in the ObjectFactory class. ... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBDS-2450 > URL: https://issues.jboss.org/browse/JBDS-2450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Error Reporting > Affects Versions: 6.0.0.GA > Reporter: Mustafa Musaji > Labels: web_service_client > Attachments: echoService.wsdl > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > bq.Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2450) No Error reported when WS Client code generation fails

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2450?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-2450: --------------------------------- Description: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: bq. Failed to invoke WSDLToJava bq. org.apache.cxf.tools.common.ToolException: Thrown by JAXB: bq. Thrown by JAXB: bq. Two declarations cause a collision in the ObjectFactory class. bq. ... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. was: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: bq.Failed to invoke WSDLToJava org.apache.cxf.tools.common.ToolException: Thrown by JAXB: Thrown by JAXB: Two declarations cause a collision in the ObjectFactory class. ... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBDS-2450 > URL: https://issues.jboss.org/browse/JBDS-2450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Error Reporting > Affects Versions: 6.0.0.GA > Reporter: Mustafa Musaji > Labels: web_service_client > Attachments: echoService.wsdl > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > bq. Failed to invoke WSDLToJava > bq. org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > bq. Thrown by JAXB: > bq. Two declarations cause a collision in the ObjectFactory class. > bq. ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2450) No Error reported when WS Client code generation fails

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2450?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-2450: --------------------------------- Description: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: Failed to invoke WSDLToJava org.apache.cxf.tools.common.ToolException: Thrown by JAXB: Thrown by JAXB: Two declarations cause a collision in the ObjectFactory class. ... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. was: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: bq.Failed to invoke WSDLToJava bq.org.apache.cxf.tools.common.ToolException: Thrown by JAXB: bq.Thrown by JAXB: bq.Two declarations cause a collision in the ObjectFactory class. bq.... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBDS-2450 > URL: https://issues.jboss.org/browse/JBDS-2450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Error Reporting > Affects Versions: 6.0.0.GA > Reporter: Mustafa Musaji > Labels: web_service_client > Attachments: echoService.wsdl > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2450) No Error reported when WS Client code generation fails

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2450?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-2450: --------------------------------- Description: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: bq.Failed to invoke WSDLToJava bq.org.apache.cxf.tools.common.ToolException: Thrown by JAXB: bq.Thrown by JAXB: bq.Two declarations cause a collision in the ObjectFactory class. bq.... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. was: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: bq. Failed to invoke WSDLToJava bq. org.apache.cxf.tools.common.ToolException: Thrown by JAXB: bq. Thrown by JAXB: bq. Two declarations cause a collision in the ObjectFactory class. bq. ... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBDS-2450 > URL: https://issues.jboss.org/browse/JBDS-2450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Error Reporting > Affects Versions: 6.0.0.GA > Reporter: Mustafa Musaji > Labels: web_service_client > Attachments: echoService.wsdl > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > bq.Failed to invoke WSDLToJava > bq.org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > bq.Thrown by JAXB: > bq.Two declarations cause a collision in the ObjectFactory class. > bq.... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2450) No Error reported when WS Client code generation fails

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-2450?page=com.atlassian.jira.plugin.... ] Mustafa Musaji updated JBDS-2450: --------------------------------- Description: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: bq. Failed to invoke WSDLToJava org.apache.cxf.tools.common.ToolException: Thrown by JAXB: Thrown by JAXB: Two declarations cause a collision in the ObjectFactory class. ... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. was: If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: Failed to invoke WSDLToJava org.apache.cxf.tools.common.ToolException: Thrown by JAXB: Thrown by JAXB: Two declarations cause a collision in the ObjectFactory class. ... However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBDS-2450 > URL: https://issues.jboss.org/browse/JBDS-2450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Error Reporting > Affects Versions: 6.0.0.GA > Reporter: Mustafa Musaji > Labels: web_service_client > Attachments: echoService.wsdl > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > bq. > Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- 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, 2 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