[JBoss JIRA] Created: (JBIDE-7957) JBoss Tools crashes editing a facelets template
by Jozef Hartinger (JIRA)
JBoss Tools crashes editing a facelets template
-----------------------------------------------
Key: JBIDE-7957
URL: https://issues.jboss.org/browse/JBIDE-7957
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.2.0.Beta2
Environment: Linux x86_64
1.6.0_23 64-Bit Server VM
Reporter: Jozef Hartinger
Assignee: Alexey Kazakov
Priority: Blocker
The issue is probably not related to seam (related to facelets themselves), however, I did not try reproducing the issue outside of seam.
Steps to reproduce:
1.) Create new seam project (war)
2.) Open the home.xhtml file (war_project/WebContent/home.xhtml) in the JBoss Tools HTML Editor (the default option)
3.) Modify the file somehow (i.e. change the heading)
4.) Hit ctrl+s to save
5.) Close the tab by clicking the tab's cross.
6.) After the sixth step JBoss Tools freezes and after a while the application crashes. I cannot see any error in the log.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBIDE-8060) SpringComponentContentTest failure
by Alexey Kazakov (JIRA)
SpringComponentContentTest failure
----------------------------------
Key: JBIDE-8060
URL: https://issues.jboss.org/browse/JBIDE-8060
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.2.0.CR1
Reporter: Alexey Kazakov
Assignee: Maxim Areshkau
Got it when run the test in tycho (locally).
Tests run: 27, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 49.541 sec <<< FAILURE!
testHasBindErrors(org.jboss.tools.vpe.spring.test.SpringComponentContentTest) Time elapsed: 0.549 sec <<< FAILURE!
junit.framework.AssertionFailedError: /home/igels/Projects/trunk/vpe/tests/org.jboss.tools.vpe.spring.test/target/work/data/SpringTest/src/main/webapp/WEB-INF/jsp/hasBindErrors.jsp.xml[/tests/test[1]/DIV/DIV/DIV/UL/SPAN]:
name of tag is "DIV"but must be "SPAN"
at junit.framework.Assert.fail(Assert.java:47)
at org.jboss.tools.vpe.base.test.ComponentContentTest.compareContent(ComponentContentTest.java:118)
at org.jboss.tools.vpe.base.test.ComponentContentTest.performContentTestByFullPath(ComponentContentTest.java:98)
at org.jboss.tools.vpe.spring.test.SpringComponentContentTest.testHasBindErrors(SpringComponentContentTest.java:61)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBIDE-7763) use existing (amazon provided) key to launch instance on ec2
by Andre Dietisheim (JIRA)
use existing (amazon provided) key to launch instance on ec2
------------------------------------------------------------
Key: JBIDE-7763
URL: https://jira.jboss.org/browse/JBIDE-7763
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
how to reproduce:
1) have a deltacloud instance with ec2 running
2) choose "Launch instance" in the Cloud view context menu
3) choose the image you want to launch an instance of
4) in the keys, hit "Manage"
5) browse to the dir where you stored the PEM file you recieved from amazon
6) hit finish
Result:
You get an error dialog that tells you of an internal server error on the deltacloud server
Expected result:
instance could be launched
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBIDE-7557) Cloud View: should be able to select running and stopped instances and stop the running ones
by Andre Dietisheim (JIRA)
Cloud View: should be able to select running and stopped instances and stop the running ones
--------------------------------------------------------------------------------------------
Key: JBIDE-7557
URL: https://jira.jboss.org/browse/JBIDE-7557
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
how to reproduce:
1) select stoped and started instances in the cloud viewer (control in the properties view that you have instances in both states)
2) open the context menu
Result:
Start is disabled in the context menu
Expected result:
Start is disabled, the instances that are stopped shall be started.
The same applies to all instance related action:
- start
- stop
- destroy
- reboot
of course, if there are several stopped instances, a dialog shall be opened and present only the stopped ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months