[JBoss JIRA] (JBIDE-25148) New application wizard: fails to create a new adapter if I switch cdk
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-25148:
----------------------------------------
Summary: New application wizard: fails to create a new adapter if I switch cdk
Key: JBIDE-25148
URL: https://issues.jboss.org/browse/JBIDE-25148
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk, openshift
Affects Versions: 4.5.1.AM2
Reporter: Andre Dietisheim
Fix For: 4.5.x
# ASSERT: have minishift 3.1.1 running
# ASSERT: have an application running that you created from eap64-basic-s2i (or nodejs-mongo-persistent)
# ASSERT: have a server adapter for your application
# EXEC: in the cmd-line:
* kill your existing cdk (minishift delete, remove ~/.minishift etc)
* setup new cdk (ex. 3.2.Alpha1)
# EXEC: in Eclipse: create new connection, then create a new application using the same template
# EXEC: when asked if you want to create a server adapter, say yes
Result:
No adapter is created.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24491 at 10/4/17 12:09 PM:
--------------------------------------------------------------------
[~mmalina] i see your point, but to me a text field "image registry URL" without any explanation nor facilities to look it up somehow is even worse. How would a user know what to do if he has this field presented as it was before? He would have 0 clue and keep wondering what he's expected to provide here and how to figure it out.
To me the updating mechanism is also a kind of black magic: if it works fine, but still completely intransparent. How would a user know when the value came in, where it was retrieved from and what he would have to do if it wasnt set?
What we could do is add some explanations to this field. Other than that I really dont know.
How would you improve things?
was (Author: adietish):
[~mmalina] i see your point, but to me a text field "image registry URL" without any explanation nor facilities to look it up somehow is even worse. How would a user know what to do if he has this field presented as it was before? He would have 0 clue and keep wondering what he's expected to provide here and how to figure it out.
To me the updating mechanism is also a kind of black magic, how would a user know when the value came in?
What we could do is add some explanations to this field. Other than that I really dont know.
How would you improve things?
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM3
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24491 at 10/4/17 12:08 PM:
--------------------------------------------------------------------
[~mmalina] i see your point, but to me a text field "image registry URL" without any explanation nor facilities to look it up somehow is even worse. How would a user know what to do if he has this field presented as it was before? He would have 0 clue and keep wondering what he's expected to provide here and how to figure it out.
To me the updating mechanism is also a kind of black magic, how would a user know when the value came in?
What we could do is add some explanations to this field. Other than that I really dont know.
How would you improve things?
was (Author: adietish):
[~mmalina] i see your point, but to me a text field "image registry URL" without any explanation nor facilities to look it up somehow is even worse. How would a user know what to do if he has this field presented as it as before? He would have 0 clue and keep wondering.
To me the updating mechanism is also a kind of black magic, how would a user know when the value came in?
What we could do is add some explanations to this field. Other than that I really dont know.
How would you improve things?
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM3
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24491 at 10/4/17 12:07 PM:
--------------------------------------------------------------------
[~mmalina] i see your point, but to me a text field "image registry URL" without any explanation nor facilities to look it up somehow is even worse. How would a user know what to do if he has this field presented as it as before? He would have 0 clue and keep wondering.
To me the updating mechanism is also a kind of black magic, how would a user know when the value came in?
What we could do is add some explanations to this field. Other than that I really dont know.
How would you improve things?
was (Author: adietish):
[~mmalina] i see your point, but to me a text field "image registry URL" without any explanation nor facilities to look it up somehow is even worse. How would a user know what to do if he has this field presented as it as before? He would have 0 clue and keep wondering.
To me the updating mechanism is also a kind of black magic, how would a user know when the value came in?
How would you improve things?
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM3
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24491 at 10/4/17 12:06 PM:
--------------------------------------------------------------------
[~mmalina] i see your point, but to me a text field "image registry URL" without any explanation nor facilities to look it up somehow is even worse. How would a user know what to do if he has this field presented as it as before? He would have 0 clue and keep wondering.
To me the updating mechanism is also a kind of black magic, how would a user know when the value came in?
How would you improve things?
was (Author: adietish):
[~mmalina] i see your point, but to me a text field "image registry URL" without any explanation nor facilities to look it up somehow is even worse. How would a user know what to do if he has this field presented as it as before? He would have 0 clue and keep wondering.
To me the updating mechanism is also a kind of black magic, how would a user know when the value came in?
How would you improve things then?
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM3
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24491:
------------------------------------------
[~mmalina] i see your point, but to me a text field "image registry URL" without any explanation nor facilities to look it up somehow is even worse. How would a user know what to do if he has this field presented as it as before? He would have 0 clue and keep wondering.
To me the updating mechanism is also a kind of black magic, how would a user know when the value came in?
How would you improve things then?
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM3
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24491:
-------------------------------------
If you don't have any CDK adapter, then there's really no way at all we can possibly discover your registry. It's just that simple.
I can work to clean up the stacktrace when starting an ill-formed server with missing information, but, that won't help the discovery button.
I believe the usecase is that you have a connection, and create your cdk adapter AFTER you ALREADY had a connection.
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM3
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24528) Remove extremely old "server manager" toolbar icons
by Fabi Yo (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24528?page=com.atlassian.jira.plugi... ]
Fabi Yo commented on JBIDE-24528:
---------------------------------
You can use it to start/stop a server, but no wtp integration... Meaning you need to hotdeploy/deploy yourself... So, it is even worse =)
> Remove extremely old "server manager" toolbar icons
> ---------------------------------------------------
>
> Key: JBIDE-24528
> URL: https://issues.jboss.org/browse/JBIDE-24528
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: affects_documentation
> Fix For: 4.5.0.AM2
>
> Attachments: JBIDE-24528.png
>
>
> A set of actions in the toolbar for setting a default server and starting / debugging / etc a server are old, poorly integrated, bypass the official wtp API, and provide limited to no value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25095) WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25095?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-25095:
-------------------------------------
I'm merging this PR despite it being kinda iffy.
We should be using the client-all jar really... but I'm not prepared to upend our historical decisions at this moment.
> WildFly 11 runtime should add "wildfly-elytron-1.1.1.Final.jar" to build path
> -----------------------------------------------------------------------------
>
> Key: JBIDE-25095
> URL: https://issues.jboss.org/browse/JBIDE-25095
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.5.0.Final
> Reporter: Wolfgang Knauf
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.1.AM3
>
>
> When a client app (e.g. a JavaEE application client) wants to perform a login to a WildFly 11 server, it has to either use a "wildfly-config.xml" file or add some code to setup security (see e.g. [Client authentication with Elytron client|https://docs.jboss.org/author/display/WFLY/Client+Authentication+w...] for a code snippet).
> To make this code compile, two jar files are required:
> %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\security\elytron-private\main\wildfly-elytron-1.1.1.Final.jar
> %WILDFLY11_HOME%\modules\system\layers\base\org\wildfly\common\main\wildfly-common-1.2.0.Final.jar
> I think the runtime should add them by default.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months