December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16269) Parameterize URL from which to install SWTBot with install-grinder is setting up

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16269?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16269: ------------------------------- Description: Install grinder tends to crap out when installing from download.eclipse.org, so we should have a way to override that URL and instead use a jboss.org URL where we've already mirrored the update site. {code:title=https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scripts/src/main/groovy/testInstall.groovy#L201} proc.setArgs("-application org.eclipse.equinox.p2.director " + "-repository http://download.eclipse.org/technology/swtbot/releases/latest/," + {code} Latest stable release of SWTBot is mirrored here: http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.1.1.20... was: Install grinder tends to crap out when installing from download.eclipse.org, so we should have a way to override that URL and instead use a jboss.org URL where we've already mirrored the update site. {code:title=https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scripts/src/main/groovy/testInstall.groovy#L201} proc.setArgs("-application org.eclipse.equinox.p2.director " + "-repository http://download.eclipse.org/technology/swtbot/releases/latest/," + {code} > Parameterize URL from which to install SWTBot with install-grinder is setting up > -------------------------------------------------------------------------------- > > Key: JBIDE-16269 > URL: https://issues.jboss.org/browse/JBIDE-16269 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, testing-tools > Affects Versions: 4.1.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > > Install grinder tends to crap out when installing from download.eclipse.org, so we should have a way to override that URL and instead use a jboss.org URL where we've already mirrored the update site. > {code:title=https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scripts/src/main/groovy/testInstall.groovy#L201} > proc.setArgs("-application org.eclipse.equinox.p2.director " + > "-repository http://download.eclipse.org/technology/swtbot/releases/latest/," + > {code} > Latest stable release of SWTBot is mirrored here: > http://download.jboss.org/jbosstools/updates/requirements/swtbot/2.1.1.20... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16269) Parameterize URL from which to install SWTBot with install-grinder is setting up

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-16269: ---------------------------------- Summary: Parameterize URL from which to install SWTBot with install-grinder is setting up Key: JBIDE-16269 URL: https://issues.jboss.org/browse/JBIDE-16269 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, testing-tools Affects Versions: 4.1.1.Final Reporter: Nick Boldt Assignee: Nick Boldt Install grinder tends to crap out when installing from download.eclipse.org, so we should have a way to override that URL and instead use a jboss.org URL where we've already mirrored the update site. {code:title=https://github.com/jbosstools/jbosstools-install-grinder/blob/master/scripts/src/main/groovy/testInstall.groovy#L201} proc.setArgs("-application org.eclipse.equinox.p2.director " + "-repository http://download.eclipse.org/technology/swtbot/releases/latest/," + {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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16253) Central tests failures on Luna

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16253?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16253: ---------------------------------------- Instead of propagating configuration here and there, I'd rather understand why this module does not inherit from parent pom configuration and fix the root cause. > Central tests failures on Luna > ------------------------------ > > Key: JBIDE-16253 > URL: https://issues.jboss.org/browse/JBIDE-16253 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Fred Bricon > Fix For: 4.2.0.Alpha1 > > > There are the following issues: > - the o.e.e4.rcp feature is required (https://github.com/jbosstools/jbosstools-build/pull/127 hasn't been applied yet) > - the examples tests require the o.e.help.ui plugin when opening the Cheat Sheets view > - the central tests freeze with GTK 3. GTK 3 seems not to be stable. See http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M3-201310302000.... The tests pass with GTK2 > It is possible that some other components have a similar issue. > Fred's fixes for the conversion and configurator plugin work correctly. > I have tested these issues on Linux and Windows. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16268) JST Web UI tests doesn't close New Wizard Dialogs after tests finished

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16268?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-16268. ---------------------------------- > JST Web UI tests doesn't close New Wizard Dialogs after tests finished > ---------------------------------------------------------------------- > > Key: JBIDE-16268 > URL: https://issues.jboss.org/browse/JBIDE-16268 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Alpha2 > Reporter: Denis Golovin > Assignee: Daniel Azarov > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > Why it is bad: > # It can lead to test errors in other tests executed after; > # It waste memory > # Covers workbench window so there is no way to see what is going on in other tests -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8445) Do not create markers at internal attribute validation by XModel

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8445?page=com.atlassian.jira.plugin... ] Alexey Kazakov closed JBIDE-8445. --------------------------------- > Do not create markers at internal attribute validation by XModel > ---------------------------------------------------------------- > > Key: JBIDE-8445 > URL: https://issues.jboss.org/browse/JBIDE-8445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 3.2.0.CR1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha2 > > > This framework needs improvement/refactoring. It was created before WTP validation framework and is not integrated into it. In many cases problem markers created by our validation duplicate markers created by WTP validation. > It is ok to have some internal validation for model consistency, but it should not interfere with the standard framework. Markers should be created by delegates of the validation job. > Now, trees and forms of JBoss Tools editors recognize markers created by XModel and display them. We may try to replace this by > 1) either to be able to bind any markers with model objects > Profit: that would immensely improve displaying problems in tree/form in JBoss Tools editors > Possible Minus: It may be very resource consuming; > 2) or to store the found problems as internal objects, not as markers, and refactor editors/views to displaying them > Profit: Preserve feature at the current level > Minus: Developing internal framework that cannot be reused; > 3) or just drop it > Profit: No need for development, just do not create markers. > Minus: Problems in tree/form in JBoss Tools editors will not be displayed. Also, other possible unexpected aftermath should be addressed to. > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16196) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16196?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-16196. -------------------------------- Resolution: Done > For JBIDE 4.1.1.Final: Prepare for Final/GA release [Aerogear] > -------------------------------------------------------------- > > Key: JBIDE-16196 > URL: https://issues.jboss.org/browse/JBIDE-16196 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.1.1.Final > > > For JBIDE 4.1.1.Final [Aerogear]: Please perform the following tasks: > 0. If nothing has changed in your component since JBT 4.1.0.Final or JBDS 7.0.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise, for all other projects: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA > [Unresolved JIRAs with fixVersion = 4.1.1.CR1, 4.1.1.Final, 7.1.0.CR1, 7.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}4.1.1.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.1.1.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Final-SNAPSHOT</version> > </parent> > {code} > 2. In the *{color:orange}4.1.x{color}* branch, update your root pom to use parent pom version *{color:orange}4.1.2.Alpha1-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.2.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.30.6.Final > mvn clean verify -Dtpc.version=4.31.1.Final > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16268) JST Web UI tests doesn't close New Wizard Dialogs after tests finished

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-16268: ------------------------------------- Summary: JST Web UI tests doesn't close New Wizard Dialogs after tests finished Key: JBIDE-16268 URL: https://issues.jboss.org/browse/JBIDE-16268 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.0.Alpha2 Reporter: Denis Golovin Assignee: Daniel Azarov Priority: Minor Why it is bad: # It can lead to test errors in other tests executed after; # It waste memory # Covers workbench window so there is no way to see what is going on in other tests -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16224) VPE test failure at new target platform

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16224?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16224: --------------------------------------- SWT_GTK3 seems to be added to the Jenkins vpe job. If SWT_GTK3 isn't exported, the issue should be reproduced on any Linux that includes GTK3. > VPE test failure at new target platform > --------------------------------------- > > Key: JBIDE-16224 > URL: https://issues.jboss.org/browse/JBIDE-16224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Alpha1 > Environment: win7 x64, java7 32bit, maven 3 > linux x86_64 java 64bit, maven3 > Reporter: Konstantin Marmalyukov > Assignee: Denis Golovin > Priority: Critical > > VPE test failures during maven build. > Test result for docbook test is the following: > {quote} > Failed tests: testTip(org.jboss.tools.vpe.docbook.test.DocbookComponentContent > Test): Editor should be opened. > testNote(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testXref(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testLiteral(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testCaution(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testImportant(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testWarning(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testProgramlisting(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > Tests run: 8, Failures: 8, Errors: 0, Skipped: 0 > {quote} > Unfortunately my console does not allow me to see full stacktrace. After debug it looks like the essence of failure is in IDE.openEditor method, which returns null and does not open the editor(according to javadoc it must open editor anyway). > Also when tests runs from Eclipse everything passes fine. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Brian Leathem commented on JBDS-2727: ------------------------------------- [~fbricon] updated. > Cheatsheets for JBoss Central archetypes > ---------------------------------------- > > Key: JBDS-2727 > URL: https://issues.jboss.org/browse/JBDS-2727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 7.1.0.GA > > Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md > > > Our archetypes should have cheatsheets when imported/opened into eclipse. > Priority > 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim > 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java > Basically walk the user through the flow of events (from the UI to the backend) in the application > 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16224) VPE test failure at new target platform

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16224?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-16224: ------------------------------------------------ Denis, test written about in description passes already fine on Jenkins. we got blue vpe build. [~dgolovin], [~snjeza], do I need smth specific being installed to reproduce this failure on Fedora x64? > VPE test failure at new target platform > --------------------------------------- > > Key: JBIDE-16224 > URL: https://issues.jboss.org/browse/JBIDE-16224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Alpha1 > Environment: win7 x64, java7 32bit, maven 3 > linux x86_64 java 64bit, maven3 > Reporter: Konstantin Marmalyukov > Assignee: Denis Golovin > Priority: Critical > > VPE test failures during maven build. > Test result for docbook test is the following: > {quote} > Failed tests: testTip(org.jboss.tools.vpe.docbook.test.DocbookComponentContent > Test): Editor should be opened. > testNote(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testXref(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testLiteral(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testCaution(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testImportant(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testWarning(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > testProgramlisting(org.jboss.tools.vpe.docbook.test.DocbookComponentContentTest): Editor should be opened. > Tests run: 8, Failures: 8, Errors: 0, Skipped: 0 > {quote} > Unfortunately my console does not allow me to see full stacktrace. After debug it looks like the essence of failure is in IDE.openEditor method, which returns null and does not open the editor(according to javadoc it must open editor anyway). > Also when tests runs from Eclipse everything passes fine. -- 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, 4 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 December 2013