[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21719:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.3.AM2)
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.5.0.AM1
>
> Attachments: JBossPerspective_PropertiesMayBeWider.png, jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-3587) Uninstalling features from central is misleading if the feature is required in JBDS
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-3587?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-3587:
-----------------------------
Fix Version/s: 11.0.0.AM1
(was: 10.x)
> Uninstalling features from central is misleading if the feature is required in JBDS
> -----------------------------------------------------------------------------------
>
> Key: JBDS-3587
> URL: https://issues.jboss.org/browse/JBDS-3587
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 9.1.0.Beta2
> Reporter: Jan Richter
> Fix For: 11.0.0.AM1
>
>
> Since some features are both in default JBDS installation and in central, you can try uninstalling them from central. The uninstall wizard will show a strange cryptic message saying:
> {noformat}"#the selected feature# cannot be fully uninstalled because other installed software requires it. The parts that are not required will be uninstalled".{noformat}
> That basically means nothing gets uninstalled, but it still requires a restart just for good measure.
> The question is - Can it either be more clear that you can't just uninstall those features using central, or just allow it?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21593:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.4.AM1)
> Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21593
> URL: https://issues.jboss.org/browse/JBIDE-21593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: Fedora 22, GTK 3.
> Reporter: Marián Labuda
> Labels: application_wizard, explorer, openshift_v3
> Fix For: 4.4.3.Final
>
> Attachments: empty_project.png
>
>
> When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot
> !empty_project.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21593:
-------------------------------
Fix Version/s: 4.4.4.AM1
(was: 4.4.3.Final)
> Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21593
> URL: https://issues.jboss.org/browse/JBIDE-21593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: Fedora 22, GTK 3.
> Reporter: Marián Labuda
> Labels: application_wizard, explorer, openshift_v3
> Fix For: 4.4.4.AM1
>
> Attachments: empty_project.png
>
>
> When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot
> !empty_project.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-22290) Open via livereload quick access errors when no livereload server is present
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22290?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22290:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.3.AM2)
> Open via livereload quick access errors when no livereload server is present
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22290
> URL: https://issues.jboss.org/browse/JBIDE-22290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 4.5.0.AM1
>
>
> The following error is produced while the livereload server is starting:
> {noformat}
> Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4522)
> at org.eclipse.swt.SWT.error(SWT.java:4437)
> at org.eclipse.swt.SWT.error(SWT.java:4408)
> at org.eclipse.swt.widgets.Display.error(Display.java:1186)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
> at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
> at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:189)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:114)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:112)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$2.done(LaunchLiveReloadServerCommandHandler.java:67)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:106)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:144)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-3900) The "Java EE Web Project" link from Red Hat Central doesn't work
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-3900?page=com.atlassian.jira.plugin.... ]
Jeff MAURY commented on JBDS-3900:
----------------------------------
[~psrna] can you verify this one before the 10.3 GA release ?
> The "Java EE Web Project" link from Red Hat Central doesn't work
> ----------------------------------------------------------------
>
> Key: JBDS-3900
> URL: https://issues.jboss.org/browse/JBDS-3900
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 9.1.0.GA
> Environment: Windows 10 Pro 64 bits
> Intel Core i7 4GB RAM
> jdk1.8.0_91
> Direct internet connection
> Reporter: Claudio Costagliola
> Assignee: Pavol Srna
> Labels: application_wizard
> Fix For: 10.3.0.GA
>
> Attachments: jbosstools-diagnostics-20160523002632.zip
>
>
> The "Java EE Web Project" link from Red Hat Central doesn't work.
> If I select the same project type from "File - New" menu, it pops up a window saying "Failed to load Wizard",
> "Wizard metadata could not be loaded", "Please check your internet connection, Proxy Settings and try again!".
> I have a direct internet connection.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23869:
-------------------------------
Fix Version/s: 4.4.4.AM1
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
> Fix For: 4.4.4.AM1
>
> Attachments: image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23869:
-------------------------------
Affects Version/s: (was: 4.4.4.AM1)
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Reporter: Aurélien Pupier
> Fix For: 4.4.4.AM1
>
> Attachments: image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBDS-3900) The "Java EE Web Project" link from Red Hat Central doesn't work
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-3900?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-3900:
--------------------------------
Assignee: Pavol Srna
> The "Java EE Web Project" link from Red Hat Central doesn't work
> ----------------------------------------------------------------
>
> Key: JBDS-3900
> URL: https://issues.jboss.org/browse/JBDS-3900
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 9.1.0.GA
> Environment: Windows 10 Pro 64 bits
> Intel Core i7 4GB RAM
> jdk1.8.0_91
> Direct internet connection
> Reporter: Claudio Costagliola
> Assignee: Pavol Srna
> Labels: application_wizard
> Fix For: 10.3.0.GA
>
> Attachments: jbosstools-diagnostics-20160523002632.zip
>
>
> The "Java EE Web Project" link from Red Hat Central doesn't work.
> If I select the same project type from "File - New" menu, it pops up a window saying "Failed to load Wizard",
> "Wizard metadata could not be loaded", "Please check your internet connection, Proxy Settings and try again!".
> I have a direct internet connection.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month