[JBoss JIRA] (JBIDE-21376) Application wizard: should allow to create an app from an image (currently only from template)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21376 at 1/6/16 1:37 PM:
------------------------------------------------------------------
We discussed how to provide this given the timely constraint we currently have. We currently also cannot provide a way for the user to create an app based on wildfly given we dont support app creation via images currently.
We saw 5 different options:
{quote}
# Use server side template
Pros:
* Works today
Cons:
* requires server side setup of templates
** (e.g. pushing builder image up, possibly pushing template up)
* We (jbossteam?) need to write and maintain template
# Use server side image (conceptually create a template based on builder image + github info)
(mimicking webconsole)
Pros:
* Will not require custom template setup on server side
Cons:
* needs new UI/workflow in New App to mimic webconsole
*
# Use eclipse side template
Pros:
* will work without server side setup
* faster to implement
Cons:
* fragile (requires specific builder images we rely on)
* add custom logic for UI/workflow in "create from source"
* Won't be (immediatly) visibile in eclipse
# Create eclipse side templates based on server side builder images
Pros:
* will not require custom additional UX flow (or will it?)
Cons:
* will have to hardcode services/routes
# rely on serverside new-app feature
Pros: no custom logic (we think)
Cons: don't know when
{quote}
We decided to go for now for eclipse side templates in a 1st step (*3*) since this is the option with the least effort.
was (Author: adietish):
We discussed how to provide this given the timely constraint we currently have. We currently also cannot provide a way for the user to create an app based on wildfly given we dont support app creation via images currently.
We saw 5 different options:
{quote}
1) Use server side template
Pros:
* Works today
Cons:
* requires server side setup of templates
** (e.g. pushing builder image up, possibly pushing template up)
* We (jbossteam?) need to write and maintain template
2) Use server side image (conceptually create a template based on builder image + github info)
(mimicking webconsole)
Pros:
* Will not require custom template setup on server side
Cons:
* needs new UI/workflow in New App to mimic webconsole
*
3) Use eclipse side template
Pros:
* will work without server side setup
* faster to implement
Cons:
* fragile (requires specific builder images we rely on)
* add custom logic for UI/workflow in "create from source"
* Won't be (immediatly) visibile in eclipse
4) Create eclipse side templates based on server side builder images
Pros:
* will not require custom additional UX flow (or will it?)
Cons:
* will have to hardcode services/routes
5) rely on serverside new-app feature
Pros: no custom logic (we think)
Cons: don't know when
{quote}
We decided to go for now for eclipse side templates in a 1st step (*3*) since this is the option with the least effort.
> Application wizard: should allow to create an app from an image (currently only from template)
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-21376
> URL: https://issues.jboss.org/browse/JBIDE-21376
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png
>
>
> The application wizard in the Eclipse tooling currently only allows to create application from templates. The web console additionally allows creating from images and git source.
> One can see the difference when comparing the listing of options in Eclipse vs the listing in the web console (which also includes images):
> {quote}
> Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling.
> See attached screenshots.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21376) Application wizard: should allow to create an app from an image (currently only from template)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21376:
------------------------------------------
We discussed how to provide this given the timely constraint we currently have. We currently also cannot provide a way for the user to create an app based on wildfly given we dont support app creation via images currently.
We saw 5 different options:
{quote}
1) Use server side template
Pros:
* Works today
Cons:
* requires server side setup of templates
** (e.g. pushing builder image up, possibly pushing template up)
* We (jbossteam?) need to write and maintain template
2) Use server side image (conceptually create a template based on builder image + github info)
(mimicking webconsole)
Pros:
* Will not require custom template setup on server side
Cons:
* needs new UI/workflow in New App to mimic webconsole
*
3) Use eclipse side template
Pros:
* will work without server side setup
* faster to implement
Cons:
* fragile (requires specific builder images we rely on)
* add custom logic for UI/workflow in "create from source"
* Won't be (immediatly) visibile in eclipse
4) Create eclipse side templates based on server side builder images
Pros:
* will not require custom additional UX flow (or will it?)
Cons:
* will have to hardcode services/routes
5) rely on serverside new-app feature
Pros: no custom logic (we think)
Cons: don't know when
{quote}
We decided to go for now for eclipse side templates in a 1st step (*3*) since this is the option with the least effort.
> Application wizard: should allow to create an app from an image (currently only from template)
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-21376
> URL: https://issues.jboss.org/browse/JBIDE-21376
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha1
>
> Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png
>
>
> The application wizard in the Eclipse tooling currently only allows to create application from templates. The web console additionally allows creating from images and git source.
> One can see the difference when comparing the listing of options in Eclipse vs the listing in the web console (which also includes images):
> {quote}
> Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling.
> See attached screenshots.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21412) Allow for any adaptable to IServerModule to be opened via LiveReload
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-21412:
-------------------------------------
Summary: Allow for any adaptable to IServerModule to be opened via LiveReload
Key: JBIDE-21412
URL: https://issues.jboss.org/browse/JBIDE-21412
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: livereload
Affects Versions: 4.3.1.Beta1
Reporter: Xavier Coulon
The "Open in Web Browser via LiveReload" is only available if the selection is an `IServerModule` but this could be extended to any type of element that can be adapted to an `IServerModule, to provide more flexibility to other tools such as OpenShift where the server adapter is used as the target (ie, there is no server module for the deployed application)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21233.
------------------------------
With Max's lengthy statement of agreement, I'm closing this.
> remove need for a targetplatforms/jbosstoolstarget/neon site
> ------------------------------------------------------------
>
> Key: JBIDE-21233
> URL: https://issues.jboss.org/browse/JBIDE-21233
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: jbt-creeping-update-sites.png
>
>
> For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/
> But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain.
> Therefore I propose we stop linking to this site.
> We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21384) Syntax errors reported on feedhenry.js file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21384?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21384:
----------------------------------------
[~vrubezhny] will point to the corresponding bugzilla/jira but in general we are going to fix such problems upstream in Eclipse JSDT for the next major release - Eclipse Neon.
> Syntax errors reported on feedhenry.js file
> -------------------------------------------
>
> Key: JBIDE-21384
> URL: https://issues.jboss.org/browse/JBIDE-21384
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Affects Versions: 4.2.3.Final
> Environment: JBDS 9.0.0
> FeedHenry Cordova Light App with Ionic
> Mac OS X 10.11
> Reporter: Karel Piwko
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha1
>
> Attachments: feedhenry.js, Screen Shot 2015-12-23 at 19.00.36.png
>
>
> When a FeedHenry Cordova project is imported into JBDS, it reports 89 errors in JBDS in feedhenry.js file.
> {code}
> Description Resource Path Location Type
> Syntax error on token ":", = expected feedhenry.js /HelloCordova/www line 4099 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3475 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3499 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3512 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3694 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3752 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3906 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3916 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 3958 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4030 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4042 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4063 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4076 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4213 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4274 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 4777 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 8647 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10325 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10352 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10430 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10439 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10454 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10545 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10556 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10564 JavaScript Problem
> Syntax error on token "}", ; expected feedhenry.js /HelloCordova/www line 10590 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3471 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3608 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3625 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3667 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3680 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3733 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3772 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3833 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3843 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 3866 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4017 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4038 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4050 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4058 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4210 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4211 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4217 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4260 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4266 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4702 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4709 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4752 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 4765 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6007 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6014 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6024 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 6353 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10220 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10272 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10345 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10381 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10390 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10397 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10404 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10419 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10428 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10437 JavaScript Problem
> Syntax error on token(s), misplaced construct(s) feedhenry.js /HelloCordova/www line 10449 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3697 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3907 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3907 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 3960 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4108 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4110 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4261 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4780 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4783 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4783 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 4783 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 6354 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 8649 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10586 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "}" to complete MethodBody feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> Syntax error, insert "else BlockStatement" to complete IfStatement feedhenry.js /HelloCordova/www line 10602 JavaScript Problem
> The left-hand side of an assignment must be a variable feedhenry.js /HelloCordova/www line 1 JavaScript Problem
> The left-hand side of an assignment must be a variable feedhenry.js /HelloCordova/www line 3400 JavaScript Problem
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19975) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19975?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-19975:
----------------------------------------
Assignee: Viacheslav Kabanovich
Resolution: Done
> v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19975
> URL: https://issues.jboss.org/browse/JBIDE-19975
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: edit-template-parameter-value.png, required-value-decoration.png
>
>
> # ASSERT: make sure that you have a connection to a v3 OpenShift server
> # EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection
> # ASSERT: new application wizard pops up, listing your project
> # EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next"
> # EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit"
> # ASSERT: editing dialog pops up
> Result:
> !edit-template-parameter-value.png!
> "OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value?
> # EXEC: provide some value and back in the wizard page hit "Next"
> # ASSERT: "Resource Labels" page shows up.
> # EXEC: Hit "Add"
> # ASSERT: dialog pops up so that I can create a new label
> Result:
> !required-value-decoration.png!
> The dialog decorates missing values with a red error marker.
> In OpenShift tooling we usually use "*" when required values are missing, not the error icon.
> Notice also the 2 additional error-decorations that are shown (there are 4 error decorations while we should have 2 only)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19975) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19975?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19975:
------------------------------------------
thanks!
cherry-picked to jbosstools-4.3.x
> v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19975
> URL: https://issues.jboss.org/browse/JBIDE-19975
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: edit-template-parameter-value.png, required-value-decoration.png
>
>
> # ASSERT: make sure that you have a connection to a v3 OpenShift server
> # EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection
> # ASSERT: new application wizard pops up, listing your project
> # EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next"
> # EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit"
> # ASSERT: editing dialog pops up
> Result:
> !edit-template-parameter-value.png!
> "OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value?
> # EXEC: provide some value and back in the wizard page hit "Next"
> # ASSERT: "Resource Labels" page shows up.
> # EXEC: Hit "Add"
> # ASSERT: dialog pops up so that I can create a new label
> Result:
> !required-value-decoration.png!
> The dialog decorates missing values with a red error marker.
> In OpenShift tooling we usually use "*" when required values are missing, not the error icon.
> Notice also the 2 additional error-decorations that are shown (there are 4 error decorations while we should have 2 only)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21411) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21411:
----------------------------------------
Summary: v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
Key: JBIDE-21411
URL: https://issues.jboss.org/browse/JBIDE-21411
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Reporter: Andre Dietisheim
Fix For: 4.3.1.Beta2
# ASSERT: make sure that you have a connection to a v3 OpenShift server
# EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection
# ASSERT: new application wizard pops up, listing your project
# EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next"
# EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit"
# ASSERT: editing dialog pops up
Result:
!edit-template-parameter-value.png!
"OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value?
# EXEC: provide some value and back in the wizard page hit "Next"
# ASSERT: "Resource Labels" page shows up.
# EXEC: Hit "Add"
# ASSERT: dialog pops up so that I can create a new label
Result:
!required-value-decoration.png!
The dialog decorates missing values with a red error marker.
In OpenShift tooling we usually use "*" when required values are missing, not the error icon.
Notice also the 2 additional error-decorations that are shown (there are 4 error decorations while we should have 2 only)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months