[JBoss JIRA] (JBIDE-21956) Port mapping validation is not correct
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21956:
-------------------------------------
Summary: Port mapping validation is not correct
Key: JBIDE-21956
URL: https://issues.jboss.org/browse/JBIDE-21956
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Assignee: Xavier Coulon
Fix For: 4.3.1.CR1
In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image.
!validation_msg.png!
There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21956) Port mapping validation is not correct
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21956?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-21956.
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
Resolution: Done
> Port mapping validation is not correct
> --------------------------------------
>
> Key: JBIDE-21956
> URL: https://issues.jboss.org/browse/JBIDE-21956
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: docker, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image.
> !validation_msg.png!
> There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21761) Port mapping validation is not correct
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21761?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21761.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B246.
> Port mapping validation is not correct
> --------------------------------------
>
> Key: JBIDE-21761
> URL: https://issues.jboss.org/browse/JBIDE-21761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: validation_msg.png
>
>
> In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image.
> !validation_msg.png!
> There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3607) Update Suite installer UI/names
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3607?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3607:
--------------------------------------
Yes, we don't have any optional dependencies right now, do we? We may have them in the future. We could allow users not to install/provide already installed dependencies if he/she wants to use only some part of the installation (JBDS only for example) but I'm afraid it will require some refactoring in our code. For example JBDS setup uses CDK and JDK and we can't just ignore CDK and JDK without refactoring JBDS setup code. I don't think we have time to do it for the upcoming release.
> Update Suite installer UI/names
> -------------------------------
>
> Key: JBDS-3607
> URL: https://issues.jboss.org/browse/JBDS-3607
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Reporter: Max Rydahl Andersen
> Assignee: Joshua Wilson
> Priority: Blocker
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: Installer flow.pdf, installer_version.png
>
>
> Suite Installer should use Red Hat Developer style. more details to follow.
> https://patternfly.atlassian.net/browse/RHUAP-26
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3607) Update Suite installer UI/names
by Josephine Qian (JIRA)
[ https://issues.jboss.org/browse/JBDS-3607?page=com.atlassian.jira.plugin.... ]
Josephine Qian commented on JBDS-3607:
--------------------------------------
[~maxandersen] I heard from [~jowilson] what we are going to force users to install everything, unless they have something installed that meets the requirement.
Regarding version, product name and icon, I am still waiting for the final decision about what to use. I will add that once the decision is made. Thanks for pointing it out [~ppitonak]
> Update Suite installer UI/names
> -------------------------------
>
> Key: JBDS-3607
> URL: https://issues.jboss.org/browse/JBDS-3607
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Reporter: Max Rydahl Andersen
> Assignee: Joshua Wilson
> Priority: Blocker
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: Installer flow.pdf, installer_version.png
>
>
> Suite Installer should use Red Hat Developer style. more details to follow.
> https://patternfly.atlassian.net/browse/RHUAP-26
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3607) Update Suite installer UI/names
by Josephine Qian (JIRA)
[ https://issues.jboss.org/browse/JBDS-3607?page=com.atlassian.jira.plugin.... ]
Josephine Qian edited comment on JBDS-3607 at 3/23/16 9:33 AM:
---------------------------------------------------------------
[~maxandersen] I heard from [~jowilson] that we are going to force users to install everything, unless they have something installed that meets the requirement.
Regarding version, product name and icon, I am still waiting for the final decision about what to use. I will add that once the decision is made. Thanks for pointing it out [~ppitonak]
was (Author: joqian):
[~maxandersen] I heard from [~jowilson] what we are going to force users to install everything, unless they have something installed that meets the requirement.
Regarding version, product name and icon, I am still waiting for the final decision about what to use. I will add that once the decision is made. Thanks for pointing it out [~ppitonak]
> Update Suite installer UI/names
> -------------------------------
>
> Key: JBDS-3607
> URL: https://issues.jboss.org/browse/JBDS-3607
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Reporter: Max Rydahl Andersen
> Assignee: Joshua Wilson
> Priority: Blocker
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
> Attachments: Installer flow.pdf, installer_version.png
>
>
> Suite Installer should use Red Hat Developer style. more details to follow.
> https://patternfly.atlassian.net/browse/RHUAP-26
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21905) Server adapter states don't reflect any real state
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21905?page=com.atlassian.jira.plugi... ]
Jan Richter commented on JBIDE-21905:
-------------------------------------
It's starting to look better. One question - is it possible to also stop the adapter automatically when I for example shut down CDK ?
> Server adapter states don't reflect any real state
> --------------------------------------------------
>
> Key: JBIDE-21905
> URL: https://issues.jboss.org/browse/JBIDE-21905
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> Having OS server adapters showing started/stopped states is quite perplexing, because they are completely arbitrary.
> For example, I can click start on a stopped server with no connection, then just cancel the connection dialog - it throws an error, but it proceeds to started state anyway.
> It is meaningless to have different states, when their only function is to predend the server is in some state. Plus it introduces steps like the 'stop server before deleting' dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years