[JBoss JIRA] (TOOLSDOC-483) Add info on LiveReload refresh delay option
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-483?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-483:
-------------------------------------
Sprint: 2014/S5 (31-Mar > 13-Apr)
> Add info on LiveReload refresh delay option
> -------------------------------------------
>
> Key: TOOLSDOC-483
> URL: https://issues.jboss.org/browse/TOOLSDOC-483
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - LiveReload Tools
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta1
>
> Original Estimate: 45 minutes
> Remaining Estimate: 45 minutes
>
> Use Case: It was reported that in some cases the server would return an error because of resources or libraries still being reloaded when the requests arrived. Some application servers need additional time to take the changes fully into account before the browsers send their request.
> Feature: The LiveReload Server Configuration Editor now provides users with a "Reload Delay" option to set the number of seconds to wait before "reload" messages are sent to the browsers. In the Server Editor under LiveReload Server Configuration, in the Reload delay field modify the length of time in seconds the IDE should wait before sending the LiveReload request to browsers. By default, the reload delay is set to 0. Once the configuration is saved, there is no need to restart the LiveReload server to take the new value into account. The delay appears as a job running in the Progress View and it can be cancelled if is the wait period was set too high (in which case the "reload" messages will be sent to the browsers without further waiting).
> Writer task: Edit topic 22835. Modify the topic text to include the new option. Create a new screen cap for the figure 'LiveReload Server Options in the Server Editor'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (TOOLSDOC-483) Add info on LiveReload refresh delay option
by Michelle Murray (JIRA)
Michelle Murray created TOOLSDOC-483:
----------------------------------------
Summary: Add info on LiveReload refresh delay option
Key: TOOLSDOC-483
URL: https://issues.jboss.org/browse/TOOLSDOC-483
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: User Guide - LiveReload Tools
Affects Versions: 4.2.0.Beta1
Reporter: Michelle Murray
Assignee: Michelle Murray
Fix For: 4.2.0.Beta1
Use Case: It was reported that in some cases the server would return an error because of resources or libraries still being reloaded when the requests arrived. Some application servers need additional time to take the changes fully into account before the browsers send their request.
Feature: The LiveReload Server Configuration Editor now provides users with a "Reload Delay" option to set the number of seconds to wait before "reload" messages are sent to the browsers. In the Server Editor under LiveReload Server Configuration, in the Reload delay field modify the length of time in seconds the IDE should wait before sending the LiveReload request to browsers. By default, the reload delay is set to 0. Once the configuration is saved, there is no need to restart the LiveReload server to take the new value into account. The delay appears as a job running in the Progress View and it can be cancelled if is the wait period was set too high (in which case the "reload" messages will be sent to the browsers without further waiting).
Writer task: Edit topic 22835. Modify the topic text to include the new option. Create a new screen cap for the figure 'LiveReload Server Options in the Server Editor'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBDS-2921) Dropping a file to Editor pane from Nautilus file browser doesn't work
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2921?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2921:
---------------------------------------
[~snjeza], that's great, thanks. I've updated the RN text accordingly. Please modify if I have something wrong.
> Dropping a file to Editor pane from Nautilus file browser doesn't work
> ----------------------------------------------------------------------
>
> Key: JBDS-2921
> URL: https://issues.jboss.org/browse/JBDS-2921
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Environment: Red Hat Enterprise Linux 6 (Gnome 2)
> Fedora 20 (Gnome 3)
> Reporter: Takayuki Konishi
> Assignee: Snjezana Peco
> Fix For: 8.0.0.Beta1
>
>
> Dropping a file to Editor pane from Nautilus file browser doesn't work. It works on JBDS 7.0, Eclipse 4.3.0 and Eclipse 4.3.1.
> I got this exception:
> {code:title=$WORKSPACE/.metadata/.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-19 10:56:37.879
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBDS-2921) Dropping a file to Editor pane from Nautilus file browser doesn't work
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2921?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2921:
----------------------------------
Release Notes Text: On Linux-based operating systems using GNOME desktop, dragging a file from Nautilus File Manager into an Editor view did not open the file. Drop events of type String were not recognized and consequently the drag-and-drop action for files did not work. This issue has been resolved by ensuring the IDE recognizes drop events for String types and dragging a file from Nautilus File Manager into an Editor view now successfully opens the file. (was: *Replace this text*
Write 2-3 sentences in plain language making sure you answer every question:
# What actions or circumstances caused the problem? How did the problem affect the example/tool/IDE?
_On Linux-based operating systems using GNOME desktop, dragging a file from Nautilus File Manager into an Editor view did not open the file._
# What was done to fix the problem?
# What now happens to the example/tool/IDE when the same actions/circumstances occur?)
> Dropping a file to Editor pane from Nautilus file browser doesn't work
> ----------------------------------------------------------------------
>
> Key: JBDS-2921
> URL: https://issues.jboss.org/browse/JBDS-2921
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Environment: Red Hat Enterprise Linux 6 (Gnome 2)
> Fedora 20 (Gnome 3)
> Reporter: Takayuki Konishi
> Assignee: Snjezana Peco
> Fix For: 8.0.0.Beta1
>
>
> Dropping a file to Editor pane from Nautilus file browser doesn't work. It works on JBDS 7.0, Eclipse 4.3.0 and Eclipse 4.3.1.
> I got this exception:
> {code:title=$WORKSPACE/.metadata/.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-19 10:56:37.879
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBDS-2921) Dropping a file to Editor pane from Nautilus file browser doesn't work
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2921?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2921:
----------------------------------
Release Notes Text: On Linux-based operating systems using GNOME desktop, dragging a file from Nautilus File Manager into an Editor view did not open the file. Drop events of type String were not recognized and consequently the drag-and-drop action for files did not work. This issue has been resolved by ensuring the IDE recognizes drop events of type String and dragging a file from Nautilus File Manager into an Editor view now successfully opens the file. (was: On Linux-based operating systems using GNOME desktop, dragging a file from Nautilus File Manager into an Editor view did not open the file. Drop events of type String were not recognized and consequently the drag-and-drop action for files did not work. This issue has been resolved by ensuring the IDE recognizes drop events for String types and dragging a file from Nautilus File Manager into an Editor view now successfully opens the file.)
> Dropping a file to Editor pane from Nautilus file browser doesn't work
> ----------------------------------------------------------------------
>
> Key: JBDS-2921
> URL: https://issues.jboss.org/browse/JBDS-2921
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 7.1.0.GA
> Environment: Red Hat Enterprise Linux 6 (Gnome 2)
> Fedora 20 (Gnome 3)
> Reporter: Takayuki Konishi
> Assignee: Snjezana Peco
> Fix For: 8.0.0.Beta1
>
>
> Dropping a file to Editor pane from Nautilus file browser doesn't work. It works on JBDS 7.0, Eclipse 4.3.0 and Eclipse 4.3.1.
> I got this exception:
> {code:title=$WORKSPACE/.metadata/.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-19 10:56:37.879
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: )
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop(EditorAreaDropAdapter.java:131)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(EditorAreaDropAdapter.java:87)
> at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(EditorAreaDropAdapter.java:81)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBIDE-16896) download runtime UI wizards has some weird workflow
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16896?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16896:
------------------------------------
Attachment: OS_signup.png
> download runtime UI wizards has some weird workflow
> ---------------------------------------------------
>
> Key: JBIDE-16896
> URL: https://issues.jboss.org/browse/JBIDE-16896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.2.0.Beta2
>
> Attachments: OS_signup.png
>
>
> using download runtime the dialogs gets maxed out dependent on the lenght of the URL it looks like.
> Making the wizard very clumsy to look and work with.
> - the table is just taking up all space - and the url is not useful (can't copy/paste/link it)
> - the table is in a dailog and there is 90% whitespace
> How about
> A) show the name and description in table
> B) Show the *info* url and if authorization is required enable username/password on the first page instead of requiring a second page for just that ?
> C) why can't we do authentication in a progress when clicking next instead of requiring users to manually click validate ?
> or at least tell the user to validate instead of just blanking out Next and *once* the credentials are valid actually show that isntead of just enabling Next.
> D) the license text shown is LGPL license - not $0 subscription (opening separate bug for this)
> E) the info url for the server is never actually shown in the workflow
> F) when clicking finish the dialog returns instantly to JBoss Runtime creation and it tells me the home dir does not exist...why did it not fill it in and let me wait ?
> G) It actually creates the server for me in the background *while* im in the server wizard flow....thats just weird.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBIDE-16896) download runtime UI wizards has some weird workflow
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16896?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-16896:
-----------------------------------------
[~mmalina]: not sure about a logo. But what if a user does not have a jboss.org account? Could we provide a workflow like that in OpenShift Connection wizard, with link to create an account which opens web browser on jboss.org sign up page? That might be sufficient to prompt the user.
!OS_signup.png!
> download runtime UI wizards has some weird workflow
> ---------------------------------------------------
>
> Key: JBIDE-16896
> URL: https://issues.jboss.org/browse/JBIDE-16896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.2.0.Beta2
>
> Attachments: OS_signup.png
>
>
> using download runtime the dialogs gets maxed out dependent on the lenght of the URL it looks like.
> Making the wizard very clumsy to look and work with.
> - the table is just taking up all space - and the url is not useful (can't copy/paste/link it)
> - the table is in a dailog and there is 90% whitespace
> How about
> A) show the name and description in table
> B) Show the *info* url and if authorization is required enable username/password on the first page instead of requiring a second page for just that ?
> C) why can't we do authentication in a progress when clicking next instead of requiring users to manually click validate ?
> or at least tell the user to validate instead of just blanking out Next and *once* the credentials are valid actually show that isntead of just enabling Next.
> D) the license text shown is LGPL license - not $0 subscription (opening separate bug for this)
> E) the info url for the server is never actually shown in the workflow
> F) when clicking finish the dialog returns instantly to JBoss Runtime creation and it tells me the home dir does not exist...why did it not fill it in and let me wait ?
> G) It actually creates the server for me in the background *while* im in the server wizard flow....thats just weird.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (JBIDE-16973) Corrupted JSF nature for openshift project
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16973?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16973:
-----------------------------------
Description:
1. Create a WildFly 8 project in www.openshift.com
2. Import it in JBT as an existing openshift project
3. See eclipse log:
"Project P/<projectname> has corrupted nature: org.jboss.tools.jsf.jsfnature"
was:
1. Create a WildFly project in www.openshift.com
2. Import it in JBT as an existing openshift project
3. See eclipse log:
"Project P/<projectname> has corrupted nature: org.jboss.tools.jsf.jsfnature"
> Corrupted JSF nature for openshift project
> ------------------------------------------
>
> Key: JBIDE-16973
> URL: https://issues.jboss.org/browse/JBIDE-16973
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.2.0.Beta1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Beta2
>
>
> 1. Create a WildFly 8 project in www.openshift.com
> 2. Import it in JBT as an existing openshift project
> 3. See eclipse log:
> "Project P/<projectname> has corrupted nature: org.jboss.tools.jsf.jsfnature"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years