[JBoss JIRA] Created: (JBIDE-8566) Eclipse 3.7 doesn't close correctly with opened VPE sometimes
by Maxim Areshkau (JIRA)
Eclipse 3.7 doesn't close correctly with opened VPE sometimes
-------------------------------------------------------------
Key: JBIDE-8566
URL: https://issues.jboss.org/browse/JBIDE-8566
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.3.0.M1
Reporter: Maxim Areshkau
Assignee: Maxim Areshkau
Priority: Critical
Fix For: 3.3.0.M1
When close eclipse 3.7 with opened VPE error occurs.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb78573bd, pid=17777, tid=1507662704
#
# JRE version: 6.0_23-b05
# Java VM: Java HotSpot(TM) Server VM (19.0-b09 mixed mode linux-x86 )
# Problematic frame:
# C [libpthread.so.0+0x83bd] __pthread_mutex_lock+0x1d
#
# An error report file with more information is saved as:
# /home/mareshkau/Projects/jboss/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid17777.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8488) Build failure for org.jboss.tools.jsf.vpe.jsf.test
by Alexey Kazakov (JIRA)
Build failure for org.jboss.tools.jsf.vpe.jsf.test
--------------------------------------------------
Key: JBIDE-8488
URL: https://issues.jboss.org/browse/JBIDE-8488
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.3.0.M1
Reporter: Alexey Kazakov
Assignee: Maxim Areshkau
Fix For: 3.3.0.M1
[ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.10.0:compile (default-compile) on project org.jboss.tools.jsf.vpe.jsf.test: Compilation failure: Compilation failure:
[ERROR] /home/igels/Projects/trunk/jsf/tests/org.jboss.tools.jsf.vpe.jsf.test/src/org/jboss/tools/jsf/vpe/jsf/test/JsfAllTests.java (at line 126):[-1,-1]
[ERROR] JSPIndexManager.getInstance().shutdown();
[ERROR] ^^^^^^^^
[ERROR] The method shutdown() is undefined for the type JSPIndexManager
[ERROR] -> [Help 1]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8487) Decrease quantity of junit tests
by Maxim Areshkau (JIRA)
Decrease quantity of junit tests
--------------------------------
Key: JBIDE-8487
URL: https://issues.jboss.org/browse/JBIDE-8487
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core, Visual Page Editor Templates
Affects Versions: 3.3.x
Reporter: Maxim Areshkau
Assignee: Maxim Areshkau
Fix For: 3.3.0.M1
We have Component Test which open component page and closed it. Than checks log for errors.
And we have Component Content Tests which open page, check content of preview, closes than page.
So when we remove Component Tests we haven't miss coverage but decrease number of tests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8366) JBoss Tools and Java Execution Environment
by Snjezana Peco (JIRA)
JBoss Tools and Java Execution Environment
------------------------------------------
Key: JBIDE-8366
URL: https://issues.jboss.org/browse/JBIDE-8366
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, cdi (jsr-299), jsp/jsf/xml source editing
Affects Versions: 3.2.0.CR1
Reporter: Snjezana Peco
Some JBT plugins have the J2SE-1.5 execution environment set although they use classes/methods that only exist in JDK 6.
The following plugins:
org.eclipse.bpel.model
org.eclipse.bpel.ui
o.j.t.cdi.ui
o.j.t.jst.jsp
contain compile errors if there is JDK/JRE 1.5 in the workspace. Since the classes/methods that are being used aren't a part of the language, but a part of JRE, Eclipse can't find those errors because there is only JDK/JRE 1.6 in the workspace.
The solution is to change the execution environment to JavaSE-1.6
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months