[JBoss JIRA] (JBIDE-21523) Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21523:
-------------------------------------
Summary: Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects
Key: JBIDE-21523
URL: https://issues.jboss.org/browse/JBIDE-21523
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Andre Dietisheim
Assignee: Fred Bricon
Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
how to reproduce:
# EXEC: File > New > Server > OpenShift 3
# ASSERT: connection page shows up
# EXEC: provide connection and hit Next
# ASSERT: you get to the server settings page
# EXEC: hit "Workspace..." to the right of "Source Path"
!browse-workspace.png!
Result:
You get a file-chooser that defaults to the workspace and lets you choose files/directories
Expected Result:
You should get a dialog where you can pick a workspace project
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21523) Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21523?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21523:
----------------------------------
Fix Version/s: (was: 4.3.1.Beta2)
> Server Adapter Wizard: "Workspace..." lets you choose files while it should present workspace projects
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21523
> URL: https://issues.jboss.org/browse/JBIDE-21523
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Andre Dietisheim
> Assignee: Fred Bricon
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
> Attachments: browse-workspace.png
>
>
> how to reproduce:
> # EXEC: File > New > Server > OpenShift 3
> # ASSERT: connection page shows up
> # EXEC: provide connection and hit Next
> # ASSERT: you get to the server settings page
> # EXEC: hit "Workspace..." to the right of "Source Path"
> !browse-workspace.png!
> Result:
> You get a file-chooser that defaults to the workspace and lets you choose files/directories
> Expected Result:
> You should get a dialog where you can pick a workspace project
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (LOCUS-50) Locus bundle for jsonschema2pojo has corrupted Export-Package statement
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/LOCUS-50?page=com.atlassian.jira.plugin.s... ]
Paul Leacu commented on LOCUS-50:
---------------------------------
Hey - I need to take a couple of personal days. This manifest won't build while it has lang3 in it. We could either update the orbit or just drop the required bundle. [~lhein] - could you take a quick look at the jaxb additions manifests just to make sure they're okay?
Thanks,
--P
{code}
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName: org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core;singleton:=true
Bundle-Version: 0.4.13.qualifier
Archiver-Version: Plexus Archiver
Bundle-ClassPath: .
Bundle-Vendor: %providerName
Bundle-Localization: plugin
Require-Bundle: com.fasterxml.jackson.core.jackson-annotations,
com.fasterxml.jackson.core.jackson-core,
com.fasterxml.jackson.core.jackson-databind,
org.jboss.tools.locus.jaxb-core,
org.jboss.tools.locus.jaxb-impl,
org.jboss.tools.locus.jaxb-xjc,
org.apache.commons.lang3,
javax.validation
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Eclipse-BuddyPolicy: registered
Created-By: Apache Maven 3.2.5
Build-Jdk: 1.8.0_65
{code}
> Locus bundle for jsonschema2pojo has corrupted Export-Package statement
> -----------------------------------------------------------------------
>
> Key: LOCUS-50
> URL: https://issues.jboss.org/browse/LOCUS-50
> Project: JBoss Tools Locus
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Lars Heinemann
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 1.6.0
>
>
> see https://gist.github.com/lhein/47405c1fcb9dc2a7138e
> Bundle:
> org.jboss.tools.locus.jsonschema2pojo.jsonschema2pojo-core 0.4.13 from 20150709-1710
> When trying to resolve classes from this bundle it fails.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21522) Background color for JavaScript code assist changes from yellow to black the second time it is opened
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-21522:
------------------------------------
Summary: Background color for JavaScript code assist changes from yellow to black the second time it is opened
Key: JBIDE-21522
URL: https://issues.jboss.org/browse/JBIDE-21522
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: javascript
Affects Versions: 4.3.1.Beta2
Environment: RHEL 7
JBDS build:
Version: 9.1.0.Beta2
Build id: Beta2-v20160120-1207-B247
Build date: 20160120-1207
Reporter: Len DiMaggio
See the attached screenshots.
To recreate:
1) Access code assist (observe that the background is yellow)
2) Close the code assist window
3) Access code assist (observe that the background is now black)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add deployment view to OpenShift v3 explorer
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-19178:
----------------------------------
Description:
Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console
Ref: https://trello.com/c/UybD1Lgx/58-8-as-an-eclipse-user-i-would-like-a-logi...
was:Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console
> Explorer, Servers view: Add deployment view to OpenShift v3 explorer
> --------------------------------------------------------------------
>
> Key: JBIDE-19178
> URL: https://issues.jboss.org/browse/JBIDE-19178
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_deployment_view, openshift_v3
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
> Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Initial deployment view.png, Pipeline view mockup.bmml, Pipeline view mockup.png
>
>
> Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console
> Ref: https://trello.com/c/UybD1Lgx/58-8-as-an-eclipse-user-i-would-like-a-logi...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21521) Port Forwarding: Caching of checkbox for free port does not work properly
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21521:
-------------------------------------
Summary: Port Forwarding: Caching of checkbox for free port does not work properly
Key: JBIDE-21521
URL: https://issues.jboss.org/browse/JBIDE-21521
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Marián Labuda
In JBIDE-21123 was fixed caching of the checkbox for usage of free ports in case of inactivity of port forwarding. But upon checking the checkbox to use free ports and start port forwarding, closing wizard and reopening port forwarding wizard, port forwarding is still active using free ports but the checkbox is unchecked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21467) Quick access 'open via livereload' with stopped application server is misbehaving
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21467?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21467.
-------------------------------
Also closing this issue as done.
> Quick access 'open via livereload' with stopped application server is misbehaving
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21467
> URL: https://issues.jboss.org/browse/JBIDE-21467
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.1.Beta2
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 4.3.1.Beta2
>
> Attachments: livereload.png
>
>
> Add a project to a stopped application server using the server's add/remove option. This adds the project to server without starting it up. Then you can select the newly added server module and use the quick access to 'Show in web browser via livereload'.
> If you have a livereload server running, it says 'Unable to open module ...'. But if no livereload server is running, it will create/start one and then leave you with a running livereload server and a stopped application server. It produces no immediate error/warning.
> It does however add this entry to the error log:
> {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:4491)
> at org.eclipse.swt.SWT.error(SWT.java:4406)
> at org.eclipse.swt.SWT.error(SWT.java:4377)
> 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:180)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:106)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:104)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$1.done(LaunchLiveReloadServerCommandHandler.java:59)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:113)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:151)
> 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
(v6.4.11#64026)
10 years, 5 months