[JBoss JIRA] (JBIDE-19119) Tern error when opening a jsp file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19119?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-19119:
----------------------------------------
Tern.java team is going to release a maitanance relase - Tern.java 0.7.1 with this fix. So we will have to update Tern for 4.2.x.
> Tern error when opening a jsp file
> ----------------------------------
>
> Key: JBIDE-19119
> URL: https://issues.jboss.org/browse/JBIDE-19119
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing, upstream
> Affects Versions: 4.3.0.Beta2
> Reporter: Martin Malina
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: tern-error.png
>
>
> I was just verying something in master for Rob and hit this issue:
> I created a dynamic web project, then a jsp file. Once the jsp was opened in Eclipse, I got this error popup immediately:
> !tern-error.png!
> This was in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2015-01-29 17:04:14.678
> !MESSAGE An internal error occurred during: "Refresh tern project job".
> !STACK 0
> java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: P/dynproj2
> at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
> at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134)
> at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333)
> at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85)
> at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:298)
> at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:118)
> at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2251)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1347)
> at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1401)
> at tern.eclipse.ide.internal.core.builder.TernBuilder.addTernBuilder(TernBuilder.java:231)
> at tern.eclipse.ide.internal.core.resources.IDETernProject.doLoad(IDETernProject.java:186)
> at tern.resources.TernProject.load(TernProject.java:332)
> at tern.eclipse.ide.internal.core.resources.RefreshTernProjectJob.runInWorkspace(RefreshTernProjectJob.java:49)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This was JBT nightly from today (2015/01/29) from http://download.jboss.org/jbosstools/updates/nightly/mars/ on top of Eclipse Mars M4. On top of that, I had one server PR of Rob's installed, but that shouldn't have any effect.
> My platform is OS X 10.10 Yosemite, running Oracle JDK 1.7.
> I realize this is master and it might be a known issue, but better to be safe :)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19259) JSF or HTML5 support choosing issues
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19259?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19259:
-----------------------------------
Fix Version/s: 4.3.0.Alpha2
> JSF or HTML5 support choosing issues
> ------------------------------------
>
> Key: JBIDE-19259
> URL: https://issues.jboss.org/browse/JBIDE-19259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.3.0.Alpha1
> Environment: Fedora 20 GNOME 64 bit, Open JDK 7, Alpha2-v20150212-0919-B9496
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha2
>
>
> # GKT2 + xulrunner loaded + JSF support enabled: HTML5 page not rendered - visual part of VPE should contain similar message as in case HTML5 support is enabled for XHTML page informing users about possibility to enable HTML5 suppport
> # VPE Preference page should contain checkbox with choice: "Always ask" otherwise user will never be able to get dialog asking to choose between JSF and HTML5 support once he will check check box "Do not show this message again"
> # When support is changed page is opened and then Eclipse is restarted it would look better if page won't be opened before Eclipse is restarted. Page should be opened after restart
> # With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden it would be more user friendly just disable it and add some label why it's disabled?.The same way as selecting of GTK for BrowserSim/CordovaSim works.
> # Confusing scenario #1:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Open .html page
> ## Restart Eclipse
> ## Close .html page
> ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed. It's confusing to ask this when page is closed.
> # Confusing scenario #2:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Restart Eclipse
> ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-19259) JSF or HTML5 support choosing issues
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19259?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19259:
--------------------------------------
Assignee: Konstantin Marmalyukov
> JSF or HTML5 support choosing issues
> ------------------------------------
>
> Key: JBIDE-19259
> URL: https://issues.jboss.org/browse/JBIDE-19259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.3.0.Alpha1
> Environment: Fedora 20 GNOME 64 bit, Open JDK 7, Alpha2-v20150212-0919-B9496
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
>
> # GKT2 + xulrunner loaded + JSF support enabled: HTML5 page not rendered - visual part of VPE should contain similar message as in case HTML5 support is enabled for XHTML page informing users about possibility to enable HTML5 suppport
> # VPE Preference page should contain checkbox with choice: "Always ask" otherwise user will never be able to get dialog asking to choose between JSF and HTML5 support once he will check check box "Do not show this message again"
> # When support is changed page is opened and then Eclipse is restarted it would look better if page won't be opened before Eclipse is restarted. Page should be opened after restart
> # With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden it would be more user friendly just disable it and add some label why it's disabled?.The same way as selecting of GTK for BrowserSim/CordovaSim works.
> # Confusing scenario #1:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Open .html page
> ## Restart Eclipse
> ## Close .html page
> ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed. It's confusing to ask this when page is closed.
> # Confusing scenario #2:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Restart Eclipse
> ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-7379) Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7379?page=com.atlassian.jira.plugin... ]
Rob Stryker commented on JBIDE-7379:
------------------------------------
> The upshot of this is that with your API only expecting to export server configuration, only the Teiid server configuration would be exportable. However, Teiid also has file artefacts, stored in other parts of the workspace which need a separate storage unit (not implemented yet).
The API I wrote completely allows any import / export participant to add an arbitrary number of files to the resultant archive. I didn't add them yet, but I have two additional files I'd like to be adding for JBoss AS / wildfly servers. They would just be contributed in a higher-level plugin of mine so I didn't get around to do it yet.
I think it's reasonable to expect a specific archive format for our import/export, and I think a zip / jar is a reasonable decision. So I think this is a fair assumption that I'd like to keep.
I think you'll find you can actually add any number of files to the jar. It is *not* limited to server configuration / runtime / launch. You can add anything you want at any path you want. Of course if there's any changes you'd like to suggest, I'd be willing to hear.
I already have the import / export actions with some minimal UI but I had planned to enable a more fully-featured UI eventually... so some discussion on what type of UI we'd like for the import could be useful.
> Importing / Exporting of AS servers ignore command line args, filesets, xpaths, and even runtimes
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-7379
> URL: https://issues.jboss.org/browse/JBIDE-7379
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.2.0.Beta1
> Reporter: Rob Stryker
> Assignee: Paul Richardson
> Fix For: 4.3.x
>
>
> Exporting of servers is incomplete. It does not export any saved filesets, xpaths, or custom launch configuration args.
> Importing of servers is also incomplete, not importing any of these elements. Also, while the servers themselves are imported, sometimes their runtimes are not created at all, and you get a server with no runtime. This has been very hard to track down, but no runtimeAdded event is ever fired, and in our code it looks as if they're not even created or looked for.
> This needs to be re-visited and tested extensively. I expect I will move import / export functionality into the AS plugin for now since hte o.j.t.runtime plugin already depends on AS. This will allow me to use classes already in the AS test suite for filesets and xpaths properly. I will keep the handler in the runtimes plugin but merely have it delegate to the functionality stored in the as plugin.
> It currently seems to be saving only servers and not the runtimes.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months