[JBoss JIRA] (JBIDE-21825) Duplicate templates in different OpenShift projects are not distinguishable from each other
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21825?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21825:
-------------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.4.0.Alpha1)
> Duplicate templates in different OpenShift projects are not distinguishable from each other
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-21825
> URL: https://issues.jboss.org/browse/JBIDE-21825
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: screenshot-1.png, TemplateLableWithNamespace.png
>
>
> New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ]
Jan Richter updated JBIDE-21821:
--------------------------------
Attachment: jbt-error
Strangely, JBDS 9.1.0.CR1 worked just fine for me, but JBT 4.3.1.CR1 did not.
See [^jbt-error].
> JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2
> ----------------------------------------------------------------
>
> Key: JBIDE-21821
> URL: https://issues.jboss.org/browse/JBIDE-21821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, marketplace
> Reporter: Thomas Mäder
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
> Attachments: FrameworkEvent ERROR.txt, jbt-error
>
>
> Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break.
> # Install Eclipse 4.5.2
> # In the Marketplace, search for "jboss developer studio"
> # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA
> # Install it
> # Restart
> # Observe: the EGit views and preferences are missing
> # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3671) sshd needs to be installed and started
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3671?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3671:
---------------------------------
Fix Version/s: 9.1.0.CR1
> sshd needs to be installed and started
> --------------------------------------
>
> Key: JBDS-3671
> URL: https://issues.jboss.org/browse/JBDS-3671
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Hardy Ferentschik
> Fix For: 9.1.0.CR1
>
>
> As parts of the Docker story we need to be able to mount the users home directory into the VM (as docker-machine does as well). Only this way the user can then use Docker mounts to mount for example project directories into a Docker container.
> docker-machine uses the vbguest additions for that, but we still need to determine whether this is possible for us due to potential licensing issues.
> An alternative approach is to use [sshfs|https://github.com/dustymabe/vagrant-sshfs/] and use ssh to mount the user's home directory into the VM. sshfs, however, requires a running sshd on the host. On Windows I am aware of two ways of doing that
> * Cygwin - http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cyg...
> * Win32-OpenSSH - https://github.com/PowerShell/Win32-OpenSSH
> I think the Windows ssh port would be the preferred solution, however, when testing it, the connection failed when using sshfs. I was able to simple ssh from the guest (CDK) to the host (Windows), but when using sshfs the connection would just abort. More investigation is required for using vagrant-sshfs with Win32-OpenSSH. It might just be that the Windows port is not fully functional which would leave use with the cygwin approach.
> Bottom line, if we want to use the sshfs approach as an alternative for vbguest additions, we need to get sshd installed one way or the other.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21821:
--------------------------------------
Assignee: Nick Boldt
> JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2
> ----------------------------------------------------------------
>
> Key: JBIDE-21821
> URL: https://issues.jboss.org/browse/JBIDE-21821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, marketplace
> Reporter: Thomas Mäder
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
> Attachments: FrameworkEvent ERROR.txt
>
>
> Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break.
> # Install Eclipse 4.5.2
> # In the Marketplace, search for "jboss developer studio"
> # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA
> # Install it
> # Restart
> # Observe: the EGit views and preferences are missing
> # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21817) Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21817?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21817:
-----------------------------------------------
This code hags Eclipse when user pushes OK in dialog started from loading editor if it is activated at Eclipse start.
Job cannot be sheduled until event sent by push button is processed. But button wants to wait for job (that mocks progress monitor).
{code}
import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.core.runtime.IStatus;
import org.eclipse.core.runtime.Status;
import org.eclipse.core.runtime.jobs.Job;
import org.eclipse.jface.dialogs.Dialog;
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Shell;
import org.eclipse.ui.PlatformUI;
public class SyncTest {
public void execute() {
Display.getDefault().syncExec(new Runnable() {
@Override
public void run() {
System.out.println("Modal dialog will be started");
new MyDialog(PlatformUI.getWorkbench().getActiveWorkbenchWindow().getShell()).open();
System.out.println("Modal dialog is completed");
}
});
}
}
class MyDialog extends Dialog {
protected MyDialog(Shell parentShell) {
super(parentShell.getShell());
}
@Override
protected void okPressed() {
Job job = new Job("test job") {
@Override
protected IStatus run(IProgressMonitor monitor) {
System.out.println("Run job");
return Status.OK_STATUS;
}
};
job.schedule();
while(job.getState() == Job.WAITING) {
System.out.println("Waiting for job to start");
try {
Thread.sleep(100);
} catch (InterruptedException e) {
break;
}
}
super.okPressed();
}
}
{code}
We can try to open an issue in Eclipse Bugzilla, but I am afraid it will be regected.
> Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21817
> URL: https://issues.jboss.org/browse/JBIDE-21817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: jstack.txt, LockAtStart.png
>
>
> 1. Close Eclipse with
> - Server Editor for OpenShift 2 server adapter open;
> - password for an Opebshift 2 connection not saved in the secure storage;
> - OpenShift Explorer active (maybe not important).
> 2. Open Eclipse - Sign In to OpenShift wizard appears while the application window remains only partially loaded (see screenshot). Once this is reproduced, it is reproduced at each Eclipse start.
> 3. Enter password and finish.
> 4. Progress appears but job does not start (I checked it in debugger) - ui jobs are locked.
> 5. Only red button cancelling connection is active, press it, wizard is unlocked (null pointer exception is fixed in JBIDE-21707).
> 6. Press Cancel, wizard is closed, Application window completes loading. - That
> 7. Connection may be established by Refresh action.
> Stack trace that calls Sign In to Openshift wizard before main window is loaded, it shows that call is initiated by loading Server Editor:
> {code}
> Thread [main] (Suspended (breakpoint at line 274 in Window))
> WizardDialog(Window).<init>(IShellProvider) line: 274
> WizardDialog(Dialog).<init>(IShellProvider) line: 438
> WizardDialog(Dialog).<init>(Shell) line: 419
> WizardDialog(TrayDialog).<init>(Shell) line: 138
> WizardDialog(TitleAreaDialog).<init>(Shell) line: 130
> WizardDialog.<init>(Shell, IWizard) line: 308
> WizardUtils.openWizardDialog(IWizard, Shell) line: 242
> CredentialsPrompter$1.run() line: 44
> UISynchronizer(Synchronizer).syncExec(Runnable) line: 186
> UISynchronizer.syncExec(Runnable) line: 145
> Display.syncExec(Runnable) line: 4634
> CredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 33
> LazyCredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 39
> ExpressConnection.promptForCredentials() line: 284
> ExpressConnection.createUser() line: 218
> ExpressConnection.connect() line: 198
> ExpressServerUtils.getApplication(IServerAttributes) line: 161
> ExpressServerUtils.getDeployFolder(IServerAttributes) line: 251
> ExpressServerEditorSection.initWidgets() line: 117
> ExpressServerEditorSection.createSection(Composite) line: 100
> OverviewEditorPart(ServerEditorPart).insertSections(Composite, String) line: 327
> OverviewEditorPart.createPartControl(Composite) line: 279
> ServerEditor(MultiPageEditorPart).addPage(int, IEditorPart, IEditorInput) line: 244
> ServerEditor(MultiPageEditorPart).addPage(IEditorPart, IEditorInput) line: 214
> ServerEditor.createPages() line: 247
> ServerEditor(MultiPageEditorPart).createPartControl(Composite) line: 363
> CompatibilityEditor(CompatibilityPart).createPartControl(IWorkbenchPart, Composite) line: 151
> CompatibilityEditor.createPartControl(IWorkbenchPart, Composite) line: 99
> CompatibilityEditor(CompatibilityPart).create() line: 341
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> MethodRequestor.execute() line: 56
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 925
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 906
> InjectorImpl.inject(Object, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 148
> InjectorImpl.internalMake(Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 372
> InjectorImpl.make(Class<T>, PrimaryObjectSupplier) line: 291
> ContextInjectionFactory.make(Class<T>, IEclipseContext) line: 162
> ReflectionContributionFactory.createFromBundle(Bundle, IEclipseContext, IEclipseContext, URI) line: 105
> ReflectionContributionFactory.doCreate(String, IEclipseContext, IEclipseContext) line: 74
> ReflectionContributionFactory.create(String, IEclipseContext) line: 56
> ContributedPartRenderer.createWidget(MUIElement, Object) line: 129
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> StackRenderer.showTab(MUIElement) line: 1306
> StackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> AreaRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine$1.run() line: 537
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement, Object, IEclipseContext) line: 521
> ElementReferenceRenderer.createWidget(MUIElement, Object) line: 70
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PerspectiveRenderer.processContents(MElementContainer<MUIElement>) line: 49
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveStackRenderer.showTab(MUIElement) line: 82
> PerspectiveStackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PerspectiveStackRenderer.postProcess(MUIElement) line: 63
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> WBWRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> WBWRenderer.processContents(MElementContainer<MUIElement>) line: 614
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PartRenderingEngine$4.run() line: 1066
> Realm.runWithDefault(Realm, Runnable) line: 336
> PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 1023
> E4Workbench.createAndRunUI(MApplicationElement) line: 157
> Workbench$5.run() line: 651
> Realm.runWithDefault(Realm, Runnable) line: 336
> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 595
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 150
> IDEApplication.start(IApplicationContext) line: 138
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 134
> EclipseAppLauncher.start(Object) line: 104
> EclipseStarter.run(Object) line: 388
> EclipseStarter.run(String[], Runnable) line: 243
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> Main.invokeFramework(String[], URL[]) line: 670
> Main.basicRun(String[]) line: 609
> Main.run(String[]) line: 1516
> Main.main(String[]) line: 1489
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21701?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21701:
-----------------------------------
Assignee: Xavier Coulon
> Enable port forwarding on a given pod and a given debug port
> ------------------------------------------------------------
>
> Key: JBIDE-21701
> URL: https://issues.jboss.org/browse/JBIDE-21701
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug).
> The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration.
> If port forwarding is already enabled on the remote pod, then the current local debug port should be returned
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21701?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21701:
-------------------------------------
Actually the debug port that we open in the deployment config will not necessarily be listed in the list of ports, so it's gonna be trickier than expected
> Enable port forwarding on a given pod and a given debug port
> ------------------------------------------------------------
>
> Key: JBIDE-21701
> URL: https://issues.jboss.org/browse/JBIDE-21701
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug).
> The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration.
> If port forwarding is already enabled on the remote pod, then the current local debug port should be returned
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-20568) Duplicate templates in different OpenShift projects are not distinguishable from each other
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20568?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20568:
------------------------------------------
+1, looks good, thanks!
> Duplicate templates in different OpenShift projects are not distinguishable from each other
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-20568
> URL: https://issues.jboss.org/browse/JBIDE-20568
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
> Attachments: screenshot-1.png, TemplateLableWithNamespace.png
>
>
> New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21824) Content assist for image names in "Deploy Docker Image" wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21824?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21824:
----------------------------------------
Assignee: Xavier Coulon (was: Andre Dietisheim)
> Content assist for image names in "Deploy Docker Image" wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-21824
> URL: https://issues.jboss.org/browse/JBIDE-21824
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection.
> If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month