October 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12974: ---------------------------------- Summary: add missing IUs to coretests and soatests sites Key: JBIDE-12974 URL: https://issues.jboss.org/browse/JBIDE-12974 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing, updatesite Affects Versions: 4.0.0.CR1 Reporter: Nick Boldt Assignee: Martin Malina Fix For: 4.1.x The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content. [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/ Are there any other missing IUs you need on those sites? -- 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, 4 months

2
9
0 / 0

[JBoss JIRA] (JBIDE-11065) Replace build.xml by a Maven plugin

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11065: -------------------------------------- Summary: Replace build.xml by a Maven plugin Key: JBIDE-11065 URL: https://issues.jboss.org/browse/JBIDE-11065 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Mickael Istria In order to improve the build infrastructure and make it easier to share and consumes with all components, we should replace build.xml by a Maven plugin and make it available througn Nexus. It should follow the parent pom versioning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
11
0 / 0

[JBoss JIRA] (JBIDE-12061) Cannot install the ESB tools and ESB detector with Juno

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-12061: ------------------------------------ Summary: Cannot install the ESB tools and ESB detector with Juno Key: JBIDE-12061 URL: https://issues.jboss.org/browse/JBIDE-12061 Project: Tools (JBoss Tools) Issue Type: Bug Components: SOA Tooling Affects Versions: 3.3.0.CR1 Environment: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta2.soa... http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.CR1.core/ Eclipse Juno: Version: 4.2.0 Build id: I20120524-2100 Reporter: Len DiMaggio Assignee: Nick Boldt Priority: Critical Fix For: 3.4.x Cannot complete the install because of a conflicting dependency. Software being installed: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector.feature.feature.group 1.3.0.v20120522-1702-H4-Beta2-SOA) Software currently installed: Eclipse SDK 4.2.0.I20120524-2100 (org.eclipse.sdk.ide 4.2.0.I20120524-2100) Only one of the following can be installed at once: Core Runtime 3.8.0.v20120521-2346 (org.eclipse.core.runtime 3.8.0.v20120521-2346) Core Runtime 3.8.0.v20120511-1333 (org.eclipse.core.runtime 3.8.0.v20120511-1333) Core Runtime 3.7.0.v20110110 (org.eclipse.core.runtime 3.7.0.v20110110) Cannot satisfy dependency: From: Eclipse e4 Rich Client Platform 1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm (org.eclipse.e4.rcp.feature.group 1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm) To: org.eclipse.core.runtime [3.8.0.v20120521-2346] Cannot satisfy dependency: From: Eclipse Platform 4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD (org.eclipse.platform.feature.group 4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD) To: org.eclipse.rcp.feature.group [4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3] Cannot satisfy dependency: From: Eclipse RCP 4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3 (org.eclipse.rcp.feature.group 4.2.0.v20120403-2031-7IAPA7BrHQicRoOdPwOavbGRB3N3) To: org.eclipse.e4.rcp.feature.group [1.1.0.v20120521-2329-8yFTIGF3GGduEYaFQA2M2RMm] Cannot satisfy dependency: From: Eclipse Project SDK 4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb (org.eclipse.sdk.feature.group 4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb) To: org.eclipse.platform.feature.group [4.2.0.v20120508-1726-9JF7AHV8FyMteja0CggfF3FfqHnxgnrWaBmfoD] Cannot satisfy dependency: From: Eclipse SDK 4.2.0.I20120524-2100 (org.eclipse.sdk.ide 4.2.0.I20120524-2100) To: org.eclipse.sdk.feature.group [4.2.0.v20120522-2109-7T7mDFDPz-3FdpcTdH3vf9z-X_aZ4Bz-tcBJLHHhcWJnb] Cannot satisfy dependency: From: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector 1.3.0.v20120522-1702-H4-Beta2-SOA) To: bundle org.eclipse.core.runtime [3.7.0,3.8.0) Cannot satisfy dependency: From: JBoss Runtime ESB Detector 1.3.0.v20120522-1702-H4-Beta2-SOA (org.jboss.tools.runtime.esb.detector.feature.feature.group 1.3.0.v20120522-1702-H4-Beta2-SOA) To: org.jboss.tools.runtime.esb.detector [1.3.0.v20120522-1702-H4-Beta2-SOA] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] (JBIDE-12863) Fix the order of JAX-RS parameters located in JAX-RS explorer

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12863: ----------------------------------------- Summary: Fix the order of JAX-RS parameters located in JAX-RS explorer Key: JBIDE-12863 URL: https://issues.jboss.org/browse/JBIDE-12863 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 4.0.0.Beta1 Reporter: Jaroslav Jankovič Assignee: Xavier Coulon Fix For: 4.0.0.Beta1, 4.0.x -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-12953) Investigate usage of Windows Tester Pro for UI Tests

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12953: -------------------------------------- Summary: Investigate usage of Windows Tester Pro for UI Tests Key: JBIDE-12953 URL: https://issues.jboss.org/browse/JBIDE-12953 Project: Tools (JBoss Tools) Issue Type: Task Components: QA Reporter: Mickael Istria Assignee: Len DiMaggio Fix For: 4.0.0.CR1 {quote:Mickael} During EclipseCon Europe, I chatted with a guy who's a pure technology-agnostic guy (not a guru, not an evangelist, just a user who gives his user story in an objective way). He used to use SWTBot to write tests, but he started using Google WindowTester Pro [1] tool since it was released under EPL by Google [2]. He told me that WindowTester Pro has a bot API quite similar to SWTBot, compatible with JUnit and Tycho; and the most interesting point is that Window Tester contains a recorder which allows to record tests pretty easily. This could help us to write tests, but also be used by end-users to provide their failing scenarios as WindowTester scenarios. The recorder simply logs all SWT events and tries to turn meaningful sequences of Events to user-grained UI operations (such as click). I was reported that 90% of code written by the recorder is good for industrial testing, the 10 remaining % requires some refactoring and Java coding; and that using WindowTester Pro takes half the time as recording+writing SWTBot tests to provide exactly the same thing, with the same level of (re)usability and maintainability. {quote} -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12897) openshift explorer does not distinguish between default and real server

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-12897: ------------------------------------------- Summary: openshift explorer does not distinguish between default and real server Key: JBIDE-12897 URL: https://issues.jboss.org/browse/JBIDE-12897 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Fix For: 4.0.0.CR1 create a connection with default server create a connection with specific server with same name as default server. Now there are two identical entires in the explorer with no way to differentiate. I suggest: A) Properties View shows the actual url/key for verifciation/testing/info purposes. B) the label/decoration should somehow indicate its a default server. i.e. redhat(a)xam.dk - openshift.redhat.com (default) -- 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, 4 months

3
15
0 / 0

[JBoss JIRA] (JBIDE-12213) OpenShiftTimeoutException when embedding more cartridges

by Stefan Bunciak (JIRA)

13 years, 4 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-12744) Bad location for problem marker on JAX-RS Resource Method

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12744: ------------------------------------- Summary: Bad location for problem marker on JAX-RS Resource Method Key: JBIDE-12744 URL: https://issues.jboss.org/browse/JBIDE-12744 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 4.0.0.Alpha2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.Alpha2 Problem marker is located at the java method name instead of the @Path annotation. -- 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, 4 months

2
8
0 / 0

[JBoss JIRA] (JBIDE-12956) WS tests not running right

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created JBIDE-12956: ----------------------------------------- Summary: WS tests not running right Key: JBIDE-12956 URL: https://issues.jboss.org/browse/JBIDE-12956 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 4.0.0.Beta1 Having issues getting the JBoss Web Services tooling tests running right after the git migration and the changes made to the AS Tools component. Believe it's due to a missing dependency in the pom. -- 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, 4 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-12765) Unable to parse web.xml

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12765: ----------------------------------------- Summary: Unable to parse web.xml Key: JBIDE-12765 URL: https://issues.jboss.org/browse/JBIDE-12765 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 4.0.0.Alpha2 Reporter: Jaroslav Jankovič Assignee: Xavier Coulon Fix For: 4.0.0.Beta1 Error is thrown when it cannot parse xml. I think, that error marker in xml editor is sufficient for user. There is no need to log an error for it, IMO. -- 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, 4 months

2
7
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 October 2012