[JBoss JIRA] (ERT-463) DockerException in DockerExplorerContentProvider$1.run [EBZ#508266]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-463?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-463:
---------------------------------
Issue Type: Bug (was: Task)
Fix Version/s: Neon.2 (4.6)
Sprint: devex #124 December 2017
Affects Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
> DockerException in DockerExplorerContentProvider$1.run [EBZ#508266]
> -------------------------------------------------------------------
>
> Key: ERT-463
> URL: https://issues.jboss.org/browse/ERT-463
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> org.eclipse.linuxtools.docker.core.DockerException: HIDDEN
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:186)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Bundles:
> | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 |
> | org.eclipse.linuxtools.docker.ui | 2.1.0.201611050402 | 2.1.0.201611050402 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5836a... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-464) IllegalStateException below DockerImagesView$7.lambda$0 (thrown in StructuredViewer.setInput) [EBZ#508268]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-464?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon resolved ERT-464.
-------------------------------
Resolution: Done
> IllegalStateException below DockerImagesView$7.lambda$0 (thrown in StructuredViewer.setInput) [EBZ#508268]
> ----------------------------------------------------------------------------------------------------------
>
> Key: ERT-464
> URL: https://issues.jboss.org/browse/ERT-464
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1687)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerImagesView$7.lambda$0(DockerImagesView.java:459)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203)
> Bundles:
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
> | org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/583b9... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-467) DockerException in ProcessLauncher$FluentProcessBuilder.<init> [EBZ#507163]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-467?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-467:
---------------------------------
Issue Type: Bug (was: Task)
Sprint: devex #124 December 2017
Affects Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
> DockerException in ProcessLauncher$FluentProcessBuilder.<init> [EBZ#507163]
> ---------------------------------------------------------------------------
>
> Key: ERT-467
> URL: https://issues.jboss.org/browse/ERT-467
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: The 'docker-compose.exe' command could not be located in 'C:\Program Files\Docker Toolbox'
> org.eclipse.linuxtools.docker.core.DockerException: The 'docker-compose.exe' command could not be located in 'C:\Program Files\Docker Toolbox'
> at org.eclipse.linuxtools.internal.docker.core.ProcessLauncher$FluentProcessBuilder.<init>(ProcessLauncher.java:87)
> at org.eclipse.linuxtools.internal.docker.core.ProcessLauncher$FluentProcessBuilder.<init>(ProcessLauncher.java:79)
> at org.eclipse.linuxtools.internal.docker.core.ProcessLauncher.processBuilder(ProcessLauncher.java:60)
> at org.eclipse.linuxtools.internal.docker.core.DockerCompose.up(DockerCompose.java:81)
> at org.eclipse.linuxtools.internal.docker.ui.jobs.DockerComposeUpJob.lambda$0(DockerComposeUpJob.java:88)
> at java.lang.Thread.run(null:-1)
> Bundles:
> | org.eclipse.linuxtools.docker.core | 2.1.0.201609141916 | 2.1.0.201609141916 |
> | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5814a... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-464) IllegalStateException below DockerImagesView$7.lambda$0 (thrown in StructuredViewer.setInput) [EBZ#508268]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-464?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-464:
---------------------------------
Issue Type: Bug (was: Task)
Fix Version/s: Neon.2 (4.6)
Sprint: devex #124 December 2017
Affects Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
> IllegalStateException below DockerImagesView$7.lambda$0 (thrown in StructuredViewer.setInput) [EBZ#508268]
> ----------------------------------------------------------------------------------------------------------
>
> Key: ERT-464
> URL: https://issues.jboss.org/browse/ERT-464
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1687)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerImagesView$7.lambda$0(DockerImagesView.java:459)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4203)
> Bundles:
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
> | org.eclipse.swt | 3.105.1.v20160907-0248 | 3.105.1.v20160907-0248 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/583b9... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-468) AssertionFailedException below ImageBuildDialog.createDialogArea (thrown in StructuredViewer.assertElementsNotNull) [EBZ#508026]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-468?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-468:
---------------------------------
Issue Type: Bug (was: Task)
Sprint: devex #124 December 2017
Affects Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
> AssertionFailedException below ImageBuildDialog.createDialogArea (thrown in StructuredViewer.assertElementsNotNull) [EBZ#508026]
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: ERT-468
> URL: https://issues.jboss.org/browse/ERT-468
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:586)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1002)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:907)
> at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:1084)
> at org.eclipse.jface.viewers.AbstractListViewer.inputChanged(AbstractListViewer.java:318)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:286)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1696)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageBuildDialog.createDialogArea(ImageBuildDialog.java:118)
> at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:767)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1095)
> at org.eclipse.jface.window.Window.open(Window.java:783)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.createConfiguration(BuildDockerImageShortcut.java:109)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.findLaunchConfiguration(BaseResourceAwareLaunchShortcut.java:84)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.launch(BuildDockerImageShortcut.java:61)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.launch(BaseResourceAwareLaunchShortcut.java:41)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:431)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:74)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> Bundles:
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/580dd... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-457) "Tag Image" shell does not have a title [EBZ#508176]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-457?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-457:
---------------------------------
Issue Type: Bug (was: Task)
Fix Version/s: Neon.2 (4.6)
Sprint: devex #124 December 2017
Affects Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
> "Tag Image" shell does not have a title [EBZ#508176]
> ----------------------------------------------------
>
> Key: ERT-457
> URL: https://issues.jboss.org/browse/ERT-457
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> Image Tag shell does not have a title.
> Steps to reproduce:
> 1. Click on any image under Images in Docker Explorer.
> 2. Select Add Tag
> 3. New window does not have a title (in vanilla eclipse neon.1 with latest Docker Tooling - 2.1.0.201611230758 is title <2>). In devstudio is not title empty.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-470) Unable to list image tags on DockerHub [EBZ#508282]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-470?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-470:
---------------------------------
Issue Type: Bug (was: Task)
Sprint: devex #124 December 2017
Affects Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
> Unable to list image tags on DockerHub [EBZ#508282]
> ---------------------------------------------------
>
> Key: ERT-470
> URL: https://issues.jboss.org/browse/ERT-470
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> It seems like the '/v1/' endpoint has been removed, resulting in an empty list of tags in the "Search Images" wizard.
> But there's hope. The Docker Hub registry now runs on the '/v2' endpoint but requires authentication:
> curl https://index.docker.io/v2/jboss/wildfly/tags/list -v
> * Trying 54.85.12.131...
> * Connected to index.docker.io (54.85.12.131) port 443 (#0)
> * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate: *.docker.io
> * Server certificate: RapidSSL SHA256 CA - G3
> * Server certificate: GeoTrust Global CA
> > GET /v2/jboss/wildfly/tags/list HTTP/1.1
> > Host: index.docker.io
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 401 Unauthorized
> < Content-Type: application/json; charset=utf-8
> < Docker-Distribution-Api-Version: registry/2.0
> < Www-Authenticate: Bearer realm="https://auth.docker.io/token",service="registry.docker.io",scope="repository:jboss/wildfly:pull"
> < Date: Mon, 28 Nov 2016 10:29:37 GMT
> < Content-Length: 145
> < Strict-Transport-Security: max-age=31536000
> <
> {"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Name":"jboss/wildfly","Action":"pull"}]}]}
> The request above failed because not auth token was provided, but the registry returned a special 'Www.Authenticate' response header which points to the authentication service to call, along with the parameters to provide:
> curl -v https://auth.docker.io/token\?service\=registry.docker.io\&scope\=reposit...
> * Trying 52.72.61.89...
> * Connected to auth.docker.io (52.72.61.89) port 443 (#0)
> * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate: *.docker.io
> * Server certificate: RapidSSL SHA256 CA - G3
> * Server certificate: GeoTrust Global CA
> > GET /token?service=registry.docker.io&scope=repository:jboss/wildfly:pull HTTP/1.1
> > Host: auth.docker.io
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Content-Type: application/json
> < Date: Mon, 28 Nov 2016 10:29:58 GMT
> < Content-Length: 1442
> < Strict-Transport-Security: max-age=31536000
> <
> {"token":"eyJ...Rg"}
> Once the token has be retrieved, the first request can be run again, this time with the token:
> curl https://index.docker.io/v2/jboss/wildfly/tags/list -v -H "Authorization: Bearer eyJ...Rg"
> * Trying 52.207.178.113...
> * Connected to index.docker.io (52.207.178.113) port 443 (#0)
> * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate: *.docker.io
> * Server certificate: RapidSSL SHA256 CA - G3
> * Server certificate: GeoTrust Global CA
> > GET /v2/jboss/wildfly/tags/list HTTP/1.1
> > Host: index.docker.io
> > User-Agent: curl/7.43.0
> > Accept: */*
> > Authorization: Bearer eyJ...Rg
> >
> < HTTP/1.1 200 OK
> < Content-Type: application/json; charset=utf-8
> < Docker-Distribution-Api-Version: registry/2.0
> < Date: Mon, 28 Nov 2016 10:30:13 GMT
> < Content-Length: 157
> < Strict-Transport-Security: max-age=31536000
> <
> {"name":"jboss/wildfly","tags":["10.0.0.Final","10.1.0.Final","8.1.0.Final","8.2.0.Final","8.2.1.Final","9.0.0.Final","9.0.1.Final","9.0.2.Final","latest"]}
> See https://docs.docker.com/registry/spec/api/#/listing-image-tags
> and https://docs.docker.com/registry/spec/auth/token/#/requesting-a-token
> The logic to retrieve the list of tags for a given image should check if the registry is a 'v2' and if it needs authentication as described above.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-469) ClassCastException in BaseResourceAwareLaunchShortcut.launch [EBZ#508027]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-469?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-469:
---------------------------------
Issue Type: Bug (was: Task)
Sprint: devex #124 December 2017
Affects Version/s: Neon.1 (4.6)
Assignee: Xavier Coulon
> ClassCastException in BaseResourceAwareLaunchShortcut.launch [EBZ#508027]
> -------------------------------------------------------------------------
>
> Key: ERT-469
> URL: https://issues.jboss.org/browse/ERT-469
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon.1 (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> java.lang.ClassCastException: org.python.pydev.navigator.elements.PythonFile cannot be cast to org.eclipse.core.resources.IResource
> at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.launch(BaseResourceAwareLaunchShortcut.java:39)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:431)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:74)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> Bundles:
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5827b... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-4201:
-------------------------------------
You're correct, we won't support this. I don't think it's necessary to say anything about this in the doc - by default, if something isn't documented, then it's not supported, right? So why document it only to say it's not supported?
I'll be happy to hear what others think :)
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.x
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier commented on JBDS-4105:
---------------------------------------
I think that I identified what this lugin should be configured to do:
- with incremental build, it should build the "Source" that will be used by Eclipse OpenShift Tooling to hot deploy in OpenShift instance
To determine:
- what is the goal/phase to generate this full "Source"
- how to configure Eclipse OpenShift Tooling to look at the right "Source" for projects using fabric8
> Provide m2e connector for io.fabric8:fabric8-maven-plugin
> ---------------------------------------------------------
>
> Key: JBDS-4105
> URL: https://issues.jboss.org/browse/JBDS-4105
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: maven
> Reporter: Aurélien Pupier
>
> iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months