[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:
---------------------------------------
You can see how this issue has been fixed within the central component - https://github.com/snjeza/jbosstools-central/commit/6526bfe6017112f573b79...
> 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
[JBoss JIRA] (JBIDE-16224) VPE test failure at new target platform
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16224?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-16224:
----------------------------------
Workaround Description:
*Under Ubuntu Linux*
# For running from dev environment in launch configuration select Environment tab and add SWT_GTK3=0 variable
# For running from terminal add SWT_GTK3=0 in command like this
{code}SWT_GTK3=0 mvn clean install{code}
*Under Windows*
(TBD)
> 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
[JBoss JIRA] (JBIDE-16224) VPE test failure at new target platform
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16224?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-16224:
---------------------------------------
on linux libxul.so fails
{code}Stack: [0x00007f2316ac1000,0x00007f2316bc2000], sp=0x00007f2316bbaf30, free space=999k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2{code}
> 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
[JBoss JIRA] (JBIDE-16224) VPE test failure at new target platform
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16224?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-16224:
----------------------------------
Environment:
win7 x64, java7 32bit, maven 3
linux x86_64 java 64bit, maven3
was:win7 x64, java7 32bit, maven 3
> 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
[JBoss JIRA] (TOOLSDOC-437) Screenshots in Figure 6.2. HTML5 Project Wizard and Figure 6.4. kitchensink-html5-mobile Wizard are reversed
by Len DiMaggio (JIRA)
Len DiMaggio created TOOLSDOC-437:
-------------------------------------
Summary: Screenshots in Figure 6.2. HTML5 Project Wizard and Figure 6.4. kitchensink-html5-mobile Wizard are reversed
Key: TOOLSDOC-437
URL: https://issues.jboss.org/browse/TOOLSDOC-437
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Components: User Guide
Environment: Build Name: 22443, User Guide-7.1
Build Date: 05-12-2013 12:18:09
Topic ID: 22840-561972 [Latest]
Reporter: Len DiMaggio
Assignee: Michelle Murray
Priority: Blocker
Title: Create a Mobile Web Project
Describe the issue:
The order of the screen shots should be reversed - they do not match the captions.
Suggestions for improvement:
Additional information:
--
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
[JBoss JIRA] (JBIDE-16226) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16226?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-16226.
------------------------------
Assignee: Nick Boldt (was: Mickael Istria)
Resolution: Done
Welcome to Donesville. Population: us.
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch
> --------------------------------------------
>
> Key: JBIDE-16226
> URL: https://issues.jboss.org/browse/JBIDE-16226
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha1
>
>
> For JBIDE 4.2.0.Alpha1: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.0.Alpha1x
> {code}
> 5. 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...]
> See also: JBDS-2855
--
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
[JBoss JIRA] (JBIDE-16200) For JBIDE 4.1.1.Final: Prepare for Final/GA release [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16200?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-16200.
-------------------------------
Resolution: Done
done
> For JBIDE 4.1.1.Final: Prepare for Final/GA release [Server]
> ------------------------------------------------------------
>
> Key: JBIDE-16200
> URL: https://issues.jboss.org/browse/JBIDE-16200
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Final
>
>
> For JBIDE 4.1.1.Final [Server]: 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 Server 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
[JBoss JIRA] (JBIDE-16231) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16231?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-16231.
-------------------------------
Resolution: Done
done
> For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Server]
> -----------------------------------------------------
>
> Key: JBIDE-16231
> URL: https://issues.jboss.org/browse/JBIDE-16231
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.Alpha2
>
>
> For JBIDE 4.2.0.Alpha1 [Server]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha1x
> git push origin jbosstools-4.2.0.Alpha1x
> {code}
> 5. 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 Server 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