[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-21290:
----------------------------------
Component/s: runtime-detection
> CDK 2 is detected as version 1.0
> --------------------------------
>
> Key: JBIDE-21290
> URL: https://issues.jboss.org/browse/JBIDE-21290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, runtime-detection
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
> Attachments: cdk-runtime-detection.png
>
>
> When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0.
> !cdk-runtime-detection.png!
> Could we change it to version 2?
> I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20584) CordovaSim doesn't talk to remote FH cloud app
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20584?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-20584:
--------------------------------
Labels: upstream (was: )
> CordovaSim doesn't talk to remote FH cloud app
> ----------------------------------------------
>
> Key: JBIDE-20584
> URL: https://issues.jboss.org/browse/JBIDE-20584
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim, upstream
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: upstream
> Fix For: 4.4.x
>
> Attachments: remote.png
>
>
> I found several issue connected with CordovaSim FH & cordova.js >= 4.0.0:
> -1) Running against *local* FH cloud app fails with disabled proxy (need to use local by default)- (UPD: reported as a separated issue - JBIDE-20590)
> 2) Running against *remote* FH cloud app does not work with cordovasim at all (for remote proxy the error is the following):
> {code}
> XMLHttpRequest cannot load https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippo.... Cannot use wildcard in Access-Control-Allow-Origin when credentials flag is true.
> {code}
> -Literally, this cordova hello world app does not work against FH app preview (It used to work before)- (UPD: not a bug the app must be deployed firstly - JBIDE-20606)!remote.png|thumbnail!*strong text*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21323) EL Knowledge Base Problem with enums
by Andrei Ivanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21323?page=com.atlassian.jira.plugi... ]
Andrei Ivanov commented on JBIDE-21323:
---------------------------------------
Indeed, {{getStatuses()}} was returning an array, as it's trivial to return the result of {{SignOffStatus.values()}} built-in method :)
Did you manage to create a ticket for this case?
Thank you :)
> EL Knowledge Base Problem with enums
> ------------------------------------
>
> Key: JBIDE-21323
> URL: https://issues.jboss.org/browse/JBIDE-21323
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x
> Reporter: Andrei Ivanov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.x
>
>
> Enum properties and method are not recognized:
> In this case, {{label}} is recognized and shows up in the completion suggestions, but {{name()}} is not and marked as unrecognized.
> {code:xml}
> <p:dataTable value="#{page.dataModel}" var="managerData" lazy="true"
> rowStyleClass="#{managerData.status.label} labor-protection-#{managerData.status.name().replace('_', '-').toLowerCase()}">
> ...
> </p:dataTable>
> {code}
> {code:java}
> public enum SignOffStatus {
> VALID("Valid"),
> ALMOST_EXPIRED("Almost expired"),
> EXPIRED("Expired");
> private final String label;
> private SignOffStatus(String label) {
> this.label = label;
> }
> public String getLabel() {
> return label;
> }
> }
> {code}
> In a different page:
> {code:xml}
> <p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
> <f:selectItem itemLabel="--select--" itemValue="#{null}" />
> <f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
> </p:selectOneMenu>
> {code}
> The enum has a {{getLabel()}} as the one above, but in this context it's not recognized ({{"label" cannot be resolved}}).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (TOOLSDOC-696) Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-696?page=com.atlassian.jira.plug... ]
Martin Malina commented on TOOLSDOC-696:
----------------------------------------
Traditionally we haven't had screenshots in the Release Notes. But there are screenshots in the New & Noteworthy section at tools.jboss.org.
I agree that it doesn't make much sense to highlight it, especially since there not anything out there in the public that users can actually use to try CDK.
> Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
> -----------------------------------------------------------------------------------
>
> Key: TOOLSDOC-696
> URL: https://issues.jboss.org/browse/TOOLSDOC-696
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Environment: Build Name: 23115, 9.1 Beta1 Release Notes-9.1-Beta1
> Build Date: 18-12-2015 22:13:00
> Topic ID: 44506-773485 [Latest]
> Reporter: Len DiMaggio
> Assignee: Misha Ali
>
> Title: New Features
> Describe the issue:
> The text describing the new support fo rthe CDK in JBDS 9.1 is correct in the draft release notes:
> '...Integration with Red Hat Container Development Kit: A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile. Once started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new OpenShift application and begin developing their AwesomeApp in a highly-replicatable environment...'
> But - I'd suggest that this moved to a more prominent location in the release notes as it is a major reason for the creation of the beta1 release.
> Can we also add a screenshot?
> Suggestions for improvement:
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months