[JBoss JIRA] Created: (RHDS-183) jre installation page is worse than having no page
by Max Andersen (JIRA)
jre installation page is worse than having no page
--------------------------------------------------
Key: RHDS-183
URL: http://jira.jboss.com/jira/browse/RHDS-183
Project: Red Hat Developer Studio
Issue Type: Bug
Components: installer
Affects Versions: 1.0.0.beta1
Reporter: Max Andersen
Priority: Blocker
Fix For: 1.0.0.beta2
1) I should not be required to select one if i dont' want it hardcoded
2) the text says "Red Hat Developer needs a J..." ..what does that mean ? what should I select ? (I would expect a jre/jdk root folder and then the page would figure out the actual vm/file to choose)
3) it does not prefill with the vm i'm already running with
4) the button is cut of in the layout
5) it does not check if im selecting a gcj or not
6) pressing browse is *slooow* (maybe just java filechooser and my machine...but looks suspicious)
7) I can select any folder and it accepts it (which then ofcourse fails when I launch the ide)
8) it does not test if I acidently selects GCJ java which is what we are trying to avoid
...in short: if you don't know *exactly* what you need to point to (and most users won't) so our users won't get through the installer.
My suggestion is that we fix all of the above and provide two options:
1) Use default Java
2) Select alternate java: [ selection field as now, but prefilled with the running one ]
And then put a warning if the selected is an GCJ (option 1: check the running vm, option 2: check the selected vm) so users are aware that using GCJ can be an issue; but is not forced do anything if the default one is fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (JBIDE-948) ConcurrentModificationException in SeamELValidator
by Viacheslav Kabanovich (JIRA)
ConcurrentModificationException in SeamELValidator
--------------------------------------------------
Key: JBIDE-948
URL: http://jira.jboss.com/jira/browse/JBIDE-948
Project: JBoss Tools
Issue Type: Bug
Reporter: Viacheslav Kabanovich
Assigned To: Viacheslav Kabanovich
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
at java.util.HashMap$KeyIterator.next(Unknown Source)
at org.jboss.tools.seam.internal.core.validation.SeamELValidator.validateAll(SeamELValidator.java:106)
at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateAll(SeamValidatorManager.java:84)
at org.jboss.tools.seam.internal.core.validation.SeamValidatorManager.validateInJob(SeamValidatorManager.java:64)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:75)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Commented: (JBIDE-538) first time open of visual editor is slooow
by Max Andersen (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-538?page=comments#action_12378622 ]
Max Andersen commented on JBIDE-538:
------------------------------------
wtp web page editor is also mozilla.
so they have the same problem as we do....
looking up registred editor is something that is almost instant in eclipse for any other editor, so much be the mozilla init....from my point of view at least ;)
but if they have the same "blocking" behavior then i guess we can live with it for now if not easy to fix ;)
> first time open of visual editor is slooow
> ------------------------------------------
>
> Key: JBIDE-538
> URL: http://jira.jboss.com/jira/browse/JBIDE-538
> Project: JBoss Tools
> Issue Type: Feature Request
> Components: integration
> Affects Versions: ExadelStudioPro4
> Reporter: Max Andersen
> Assigned To: Sergey Vasilyev
> Priority: Critical
>
> First time a visual editor is opened Eclipse freezes and in the worst case it turns all white.
> I assume this is because of the first start of the mozilla engine.
> We should investigate if it wouldn't be possible to start this in the background; showing a "Starting visual editor...." in the visual part of the editor until it is ready.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month
[JBoss JIRA] Commented: (JBIDE-538) first time open of visual editor is slooow
by Sergey Vasilyev (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-538?page=comments#action_12378608 ]
Sergey Vasilyev commented on JBIDE-538:
---------------------------------------
Unfortunately on my machine it true. Opening WTP's Web Page Editor takes about the same time as Red Hat HTML Editor. Can you try to do it on your computer. Clear time without eclipse of starting Red Hat HTML Editor takes no more then 10 seconds.
I can put ProgressDialog into start of VE and you will see what about I'm talking.
> first time open of visual editor is slooow
> ------------------------------------------
>
> Key: JBIDE-538
> URL: http://jira.jboss.com/jira/browse/JBIDE-538
> Project: JBoss Tools
> Issue Type: Feature Request
> Components: integration
> Affects Versions: ExadelStudioPro4
> Reporter: Max Andersen
> Assigned To: Sergey Vasilyev
> Priority: Critical
>
> First time a visual editor is opened Eclipse freezes and in the worst case it turns all white.
> I assume this is because of the first start of the mozilla engine.
> We should investigate if it wouldn't be possible to start this in the background; showing a "Starting visual editor...." in the visual part of the editor until it is ready.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month