[JBoss JIRA] Created: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
11:57 a.m.
VPE Part should not show exceptions but readable explanation why it cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Maxim Areshkau
Fix For: 3.2.0.Beta2
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
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
11:59 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://jira.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin.s...
]
Denis Golovin updated JBIDE-7308:
---------------------------------
Attachment: XL-x86_64-1.png
XL-x86_64-2.png
Exceptions that appears during opening VPE on Windows 7 x86_64, that must be fixed
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Maxim Areshkau
Fix For: 3.2.0.Beta2
Attachments: XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
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
12:01 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://jira.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin.s...
]
Denis Golovin commented on JBIDE-7308:
--------------------------------------
another problem we have to fix is macosx xulrunner bundles have no architecture declared
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Maxim Areshkau
Fix For: 3.2.0.Beta2
Attachments: XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
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
2:46 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://jira.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin.s...
]
Yahor Radtsevich updated JBIDE-7308:
------------------------------------
Fix Version/s: 3.2.0.CR1
(was: 3.2.0.Beta2)
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Fix For: 3.2.0.CR1
Attachments: XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
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
12:45 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://jira.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin.s...
]
Yahor Radtsevich commented on JBIDE-7308:
-----------------------------------------
I agree that there are too many messages shown to the user. As a first step to fix this, I
have created a sub-task: JBIDE-7601 (Show XULRunner exception only once).
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.0.CR1
Attachments: XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://jira.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin.s...
]
Yahor Radtsevich commented on JBIDE-7308:
-----------------------------------------
The subtask is resolved.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.0.CR1
Attachments: XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://jira.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin.s...
]
Yahor Radtsevich commented on JBIDE-7308:
-----------------------------------------
Also I have replaced the message "Could not detect registered XULRunner to use"
by the message "Current platform ''${os}.${ws}.${arch}'' is not
supported".
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.0.CR1
Attachments: XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:10 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://jira.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin.s...
]
Yahor Radtsevich resolved JBIDE-7308.
-------------------------------------
Fix Version/s: 3.2.0.Beta2
(was: 3.2.0.CR1)
Resolution: Done
RESOLVED
Summary of what has been done:
1. The XULRunner exception is shown only once in VPE (JBIDE-7601).
2. If the exception is thrown and the platform is not supported, then VPE prints
"Current platform ''${os}.${ws}.${arch}'' is not supported"
(resolved-screenshot-1.png).
3. "JBoss Visual Editor FAQ" is updated with the list of supported platforms
( http://www.jboss.org/community/docs/DOC-10862 ).
What is related to the checkbox, which could disable VPE, my opinion is that it is
unnecessary. In any case user can use the Source tab of VPE only.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.0.Beta2
Attachments: XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:13 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://jira.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin.s...
]
Yahor Radtsevich updated JBIDE-7308:
------------------------------------
Attachment: resolved-screenshot-1.png
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://jira.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.0.Beta2
Attachments: resolved-screenshot-1.png, XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Jiri Peterka closed JBIDE-7308.
-------------------------------
Verified with JBT 3.2.0 beta2 h68, Windows 7 64-bit
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.M2
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Jiri Peterka
Labels: usability
Fix For: 3.2.0.Beta2
Attachments: resolved-screenshot-1.png, XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:41 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Yahor Radtsevich updated JBIDE-7308:
------------------------------------
Fix Version/s: 3.2.1
3.3.0.M1
(was: 3.2.0.Beta2)
Affects Version/s: 3.2.0.Final
(was: 3.2.0.M2)
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: resolved-screenshot-1.png, XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Yahor Radtsevich updated JBIDE-7308:
------------------------------------
Attachment: JBIDE-7308-2.patch
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, XL-x86_64-1.png,
XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:38 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Yahor Radtsevich commented on JBIDE-7308:
-----------------------------------------
Fixed in trunk. Now on Mac OS X with 64-bit Java the VPE prints:
??Current platform ''carbon.macosx.Ñ…86_64'' is not supported.??
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, XL-x86_64-1.png,
XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:02 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-7308:
--------------------------------------
patch should be fine, but it looks like you have wrong char in patch
!screenshot19.png!
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Denis Golovin
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:02 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Denis Golovin updated JBIDE-7308:
---------------------------------
Attachment: screenshot19.png
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Denis Golovin
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:29 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Yahor Radtsevich commented on JBIDE-7308:
-----------------------------------------
Thanks, Denis. I used Cyrillic 'x' by a mistake. Now it is fixed.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:04 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Yahor Radtsevich resolved JBIDE-7308.
-------------------------------------
Resolution: Done
RESOLVED
4QAs:
Please, ensure that
# VPE shows the message "Current platform ''${os}.${ws}.${arch}'' is
not supported" on the following environments:
#* Mac OS X Carbon with Java 64-bit
#* Mac OS X Cocoa with Java 64-bit
#* Windows 64-bit with Java 64-bit
# VPE with broken XULRunner shows the message "org.eclipse.swt.SWTError: No more
handles [Could not detect registered XULRunner to use]" on the following
environments:
#* Mac OS X Carbon with Java 32-bit
#* Mac OS X Cocoa with Java 32-bit
#* Linux 64-bit with Java 32-bit
#* Windows 64-bit with Java 32-bit
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:04 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Yahor Radtsevich commented on JBIDE-7308:
-----------------------------------------
You can break XULRunner by removing (renaming) the following directory:
jbdevstudio/studio/plugins/org.mozilla.xulrunner.{os}.${ws}.${arch}_1.9.1.2/xulrunner
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:21 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Yahor Radtsevich edited comment on JBIDE-7308 at 3/11/11 4:20 AM:
------------------------------------------------------------------
RESOLVED
4QAs:
Please, ensure that
# VPE shows the message "Current platform ''${os}.${ws}.${arch}'' is
not supported" on the following environments:
#* Mac OS X Carbon with Java 64-bit
#* Mac OS X Cocoa with Java 64-bit
#* Windows 64-bit with Java 64-bit
# VPE with broken XULRunner shows the message "org.eclipse.swt.SWTError: No more
handles [Could not detect registered XULRunner to use]" on the following
environments:
#* Mac OS X Carbon with Java 32-bit
#* Mac OS X Cocoa with Java 32-bit
#* Linux 64-bit with Java 32-bit
#* Windows 64-bit with Java 32-bit
# Of course, VPE should work on all [supported
platforms|http://community.jboss.org/docs/DOC-10862].
was (Author: yradtsevich):
RESOLVED
4QAs:
Please, ensure that
# VPE shows the message "Current platform ''${os}.${ws}.${arch}'' is
not supported" on the following environments:
#* Mac OS X Carbon with Java 64-bit
#* Mac OS X Cocoa with Java 64-bit
#* Windows 64-bit with Java 64-bit
# VPE with broken XULRunner shows the message "org.eclipse.swt.SWTError: No more
handles [Could not detect registered XULRunner to use]" on the following
environments:
#* Mac OS X Carbon with Java 32-bit
#* Mac OS X Cocoa with Java 32-bit
#* Linux 64-bit with Java 32-bit
#* Windows 64-bit with Java 32-bit
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:22 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Martin Malina commented on JBIDE-7308:
--------------------------------------
Hi Yahor,
I couldn't find any new JBDS build, so I tried to test this on
jbosstools-3.2_stable_branch.aggregate-Update-2011-03-15_08-44-17-H563.zip but it still
doesn't contain the fix (i.e. I got the message Could not open the Visual Page
Editor...).
VPE is version 3.2.0.v20110311-0855-H50-GA .
I suppose I need 3.2.1, right? But unfortunately I couldn't find it anywhere. Do you
think there is a build I can check against which would contain the fix?
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:14 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-7308:
--------------------------------------
Martin, you took right version, but with current build infrastructure changes in one
component might don't get into aggregated update site. Sad to say, but hat's what
happened it your case. The changes are in VPE H51 build from March 11th, but for some
reason it didn't get into aggregated update site from March 15th.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:29 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Yahor Radtsevich commented on JBIDE-7308:
-----------------------------------------
Hi Martin,
I just checked jbdevstudio-product-win32-4.0.1.v201103151801R-H257-CR1.jar . It contains
org.jboss.tools.vpe.xulrunner H50. I do not know about builds for other systems, but as I
can see, the changes *are included* in this win32 build.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:06 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Martin Malina commented on JBIDE-7308:
--------------------------------------
I checked jbdevstudio-product-macosx-cocoa-x86_64-4.0.1.v201103170420R-H262-CR1.jar and it
doesn't contain the fix. I guess I will have to check on some newew build later.
The problem is that it only contains H32 version of xulrunner:
org.jboss.tools.vpe.xulrunner_3.2.0.v20110224-1607-H32-GA.jar
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:12 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Yahor Radtsevich commented on JBIDE-7308:
-----------------------------------------
The last fix was committed on 10/Mar/11 . So yes, you have to wait for newer build.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Labels: usability
Fix For: 3.2.1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:16 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Denis Maliarevich commented on JBIDE-7308:
------------------------------------------
Updated on mac 64-bit
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Denis Maliarevich
Labels: usability
Fix For: 3.2.1.M1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:18 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Denis Maliarevich resolved JBIDE-7308.
--------------------------------------
Resolution: Done
Resolved.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Denis Maliarevich
Labels: usability
Fix For: 3.2.1.M1, 3.3.0.M1
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:18 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Denis Maliarevich updated JBIDE-7308:
-------------------------------------
Fix Version/s: 3.2.1.CR1
3.3.0.M2
(was: 3.2.1.M1)
(was: 3.3.0.M1)
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Denis Maliarevich
Labels: usability
Fix For: 3.2.1.CR1, 3.3.0.M2
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:20 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Denis Maliarevich commented on JBIDE-7308:
------------------------------------------
As there is a codefreeze now -- changing fix versions.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Denis Maliarevich
Labels: usability
Fix For: 3.2.1.CR1, 3.3.0.M2
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:26 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Denis Maliarevich resolved JBIDE-7308.
--------------------------------------
Resolution: Done
Committed to 3.2.x branch.
Resolved.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Denis Maliarevich
Labels: usability
Fix For: 3.2.1.CR1, 3.3.0.M2
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:57 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-7308) VPE Part should not show exceptions but readable explanation why it cannot be loaded
[
https://issues.jboss.org/browse/JBIDE-7308?page=com.atlassian.jira.plugin...
]
Vlado Pakan closed JBIDE-7308.
------------------------------
Verified on Mac OS.
VPE Part should not show exceptions but readable explanation why it
cannot be loaded
------------------------------------------------------------------------------------
Key: JBIDE-7308
URL: https://issues.jboss.org/browse/JBIDE-7308
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.2.0.Final
Environment: All other platforms except supported ones:
macosx-carbon-x86
macosx-cocoa-x86
win32-win32-x86
linux-gtk-x86
linux-gtk-x86_64
Reporter: Denis Golovin
Assignee: Denis Maliarevich
Labels: usability
Fix For: 3.2.1.CR1, 3.3.0.M2
Attachments: JBIDE-7308-2.patch, resolved-screenshot-1.png, screenshot19.png,
XL-x86_64-1.png, XL-x86_64-2.png
Exceptions related to loading xulrunner should be handled right way. Human friendly
messages would be good here for usecases we know. VPE should check for current platform
and if it is not supported do not scary users with exceptions. It should try to load XL
just in case path to XL injected outside through System property, but show explanation
instead of just exception. Something like:
"Current platform ${os}-${ws}-${arch} is not supported. To find list of supported
platforms and possible workarounds. please read this article on JBoss Tools Community
Portal". If someone is trying to inject XULRunner implementation using system
property it can say, That "Visual Editor tried to load XL from provided loaction
${pathToXulrunner} but it failed with exception, please find it in Eclipse Error Log
View".
We could also have check box to remove VE related parts from editor:
"[x] Open only source part of Visual Editor".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5397
days inactive
5631
days old
jbosstools-issues@lists.jboss.org
29 comments
6 participants
participants (6)
-
Denis Golovin (JIRA) -
Denis Maliarevich (JIRA)
-
Jiri Peterka (JIRA)
-
Martin Malina (JIRA)
-
Vlado Pakan (JIRA)
-
Yahor Radtsevich (JIRA)