[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3868:
-----------------------------
Fix Version/s: 11.3.0.GA
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.3.0.GA
>
> Attachments: cnf-review.png, confirmation-page.png, screenshot-1.png
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBDS-3868) Document (and check) required disk space before beginning install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3868?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3868:
-----------------------------
Fix Version/s: (was: 11.x)
> Document (and check) required disk space before beginning install
> -----------------------------------------------------------------
>
> Key: JBDS-3868
> URL: https://issues.jboss.org/browse/JBDS-3868
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.3.0.GA
>
> Attachments: cnf-review.png, confirmation-page.png, screenshot-1.png
>
>
> The installer and it's documentation should indicate the minimum required disk space before beginning the download and installation process.
> Between temporary files, and download/installs going on in parallel. I'm guessing at least 10-15 GB free is needed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26043) Two paths to OC client in properties view for OpenShift connection
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26043?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26043.
---------------------------------
Closing. Issue is fixed,
Verified in:
Red Hat Developer Studio
Version: 12.0.0.GA
Build id: GA-v20180626-0421-B2872
Build date: 20180626-0421
> Two paths to OC client in properties view for OpenShift connection
> ------------------------------------------------------------------
>
> Key: JBIDE-26043
> URL: https://issues.jboss.org/browse/JBIDE-26043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: oc_binary, properties
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-05-28-14-48-08-877.png, screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png
>
>
> !image-2018-05-28-14-48-08-877.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22138:
-------------------------------------
It should be entering private final boolean deltaAffectsModules(IResourceDelta delta) { in ProjectModuleFactoryDelegate when you modify the component file. This should wipe out the cache.
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22138:
------------------------------------
Please submit a gerrit request against http://git.eclipse.org/c/servertools/webtools.servertools.git/ and I'll ensure this is pushed into 3.10.1 / 3.11.0
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.6.0.Final
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26070) [SSP] Client Managed workflow
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26070?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-26070:
----------------------------------
Component/s: stack-server-protocol
(was: server)
> [SSP] Client Managed workflow
> -----------------------------
>
> Key: JBIDE-26070
> URL: https://issues.jboss.org/browse/JBIDE-26070
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM3
>
>
> aged flow
> @startuml
> Client -> Adaptor : findservers
> Client <- Adaptor : serverlist
> Client -> Adaptor : create server
> Client <- Adaptor : serverAdded (id)
> Client -> Adaptor : getLaunchProperties()
> Adapter -> Client : here’s a list
> Client -> Adaptor : getLaunchCommand(String serverId, String mode, Map<String,String> properties)
> Client <- Adaptor : launch string (id)
> Client -> Adaptor : server started
> Client -> Adaptor : server stopped
> Client -> Adaptor : publish
> @enduml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26019) Show in Web Browser on running server throws an internal error
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26019?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-26019.
---------------------------------
Verified in devstudio-12.0.0.AM3-2737.
> Show in Web Browser on running server throws an internal error
> --------------------------------------------------------------
>
> Key: JBIDE-26019
> URL: https://issues.jboss.org/browse/JBIDE-26019
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.6.0.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM3
>
>
> When I start a server and then I right-click it in Servers view and select Show in Web Browser, I get an error:
> {code}
> 'Fetching Welcome Page URL' has encountered a problem.
> An internal error occurred during: "Fetching Welcome Page URL".
> Invalid thread access
> {code}
> And there is a bit more of info in the error log view:
> {code}
> An internal error occurred during: "Fetching Welcome Page URL".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4552)
> at org.eclipse.swt.SWT.error(SWT.java:4467)
> at org.eclipse.swt.SWT.error(SWT.java:4438)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:807)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:594)
> at org.eclipse.swt.widgets.Tree.getSelection(Tree.java:1819)
> at org.eclipse.jface.viewers.TreeViewer.getSelection(TreeViewer.java:228)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getSelection(AbstractTreeViewer.java:2975)
> at org.eclipse.ui.navigator.CommonViewer.getSelection(CommonViewer.java:485)
> at org.jboss.ide.eclipse.as.ui.views.server.extensions.ShowInWelcomePageActionProvider.getSelection(ShowInWelcomePageActionProvider.java:292)
> at org.jboss.ide.eclipse.as.ui.views.server.extensions.ShowInWelcomePageActionProvider.getServer(ShowInWelcomePageActionProvider.java:269)
> at org.jboss.ide.eclipse.as.ui.views.server.extensions.ShowInWelcomePageActionProvider.getUrl(ShowInWelcomePageActionProvider.java:173)
> at org.jboss.ide.eclipse.as.ui.views.server.extensions.ShowInWelcomePageActionProvider.access$0(ShowInWelcomePageActionProvider.java:171)
> at org.jboss.ide.eclipse.as.ui.views.server.extensions.ShowInWelcomePageActionProvider$1$1.run(ShowInWelcomePageActionProvider.java:85)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60)
> {code}
> This was in a situation where I had two servers - one WF 12 and the other EAP 7.1. It happens for both. So it seems it would happen with any server probably.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months