[JBoss JIRA] (JBDS-3078) 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3078?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3078:
--------------------------------
CDW devel_ack: + (was: ?)
> 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site
> ---------------------------------------------------------------------
>
> Key: JBDS-3078
> URL: https://issues.jboss.org/browse/JBDS-3078
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 8.0.0.Beta3
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 8.0.0.CR1
>
>
> Building locally:
> {code}
> [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site ---
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron9054877340821028927/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron489909634983575622/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico
> {code}
> Building in Jenkins:
> {code}
> [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site ---
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron5040285231221120320/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron8242740933405392439/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico{code}
> Is this a problem?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17913) Users don't notice the software update tab - can we make it more visibile on the front page ?
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17913?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-17913:
-------------------------------------
At this time, I dislike removing TicketMonster - if we had some metrics to see how often users are seeing TiMo in that location it would be beneficial.
For now, simply adding "Camel Project" to Start from scratch and "Integration Applications" to Start from a sample should help tremendously - as clicking on those options will prompt the end-user to first install the integration stack tooling
> Users don't notice the software update tab - can we make it more visibile on the front page ?
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-17913
> URL: https://issues.jboss.org/browse/JBIDE-17913
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Burr Sutter
> Fix For: 4.2.0.CR1
>
>
> We are getting complaints users does not notice that they can install things like integration stack from software update page.
> Could we make this more clear onthe front page ?
> Maybe remove the ticketmonster example image and put "highlights" from central on this page instead ?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17973) Obscure database password
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17973?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-17973:
-------------------------------------
The password in clear text is how the OpenShift web UI handles this as well
http://screencast.com/t/bAhRaXbrJr
I would consider our attempts to obscure the password to be a usability problem - JBDS would be out of sync with the other developer experiences (web and command line). AND having that password is actually very important - if the end-user fails to see it and write it down - then they may have to re-create the app.
> Obscure database password
> -------------------------
>
> Key: JBIDE-17973
> URL: https://issues.jboss.org/browse/JBIDE-17973
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Labels: uxtest
> Fix For: 4.3.x
>
>
> When creating an OpenShift application with a database cartridge, the database password is shown in clear text. This password should be obscured.
> It was noted that OpenShift does show clear text passwords in some locations, the difference here is that the user did not prompt for this information meaning we are displaying a password in clear text at a potential point where the user is not aware they need to be in a 'secure' environment.
> Reproduce steps:
> 1. Open new OpenShift Application wizard
> 2. Sign in & proceed to next screen
> 3. Choose application cartridge (JBoss EAP 6 for instance) & proceed to next screen
> 4. Add embedded cartridge for database (mySQL 5.5 for instance) & proceed to next screen
> 5. Click next on set up project screen
> 6. Click finish on next screen
> 7 -> ISSUE HERE. Once app is created, pop-up is shown with mySQL database password shown in clear text. Screenshot: https://www.evernote.com/shard/s230/sh/cd8123fb-a400-4699-ad08-bcbc06f7b5...
> Expected: Password on this pop-up should be obscured.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17987) Bogus syntax warning for EL 3.0 list literal
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17987?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17987:
-----------------------------------
Fix Version/s: 4.2.0.CR1
> Bogus syntax warning for EL 3.0 list literal
> --------------------------------------------
>
> Key: JBIDE-17987
> URL: https://issues.jboss.org/browse/JBIDE-17987
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta3
> Reporter: Rich DiCroce
> Fix For: 4.2.0.CR1
>
>
> Assume you have an XHTML page that contains a JSF tag, and you want to use the EL 3.0 list literal to set an attribute on that tag, e.g.
> {code:xml}
> <my:tag someListProperty="#{[1, 2, 3]}"/>
> {code}
> The syntax is valid, but JBT reports the warning "EL syntax error: Expecting expression."
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17987) Bogus syntax warning for EL 3.0 list literal
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17987?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-17987:
--------------------------------------
Assignee: Viacheslav Kabanovich
> Bogus syntax warning for EL 3.0 list literal
> --------------------------------------------
>
> Key: JBIDE-17987
> URL: https://issues.jboss.org/browse/JBIDE-17987
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta3
> Reporter: Rich DiCroce
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.CR1
>
>
> Assume you have an XHTML page that contains a JSF tag, and you want to use the EL 3.0 list literal to set an attribute on that tag, e.g.
> {code:xml}
> <my:tag someListProperty="#{[1, 2, 3]}"/>
> {code}
> The syntax is valid, but JBT reports the warning "EL syntax error: Expecting expression."
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17987) Bogus syntax warning for EL 3.0 list literal
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17987?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17987:
-----------------------------------
Component/s: jsf
jsp/jsf/xml/html source editing
> Bogus syntax warning for EL 3.0 list literal
> --------------------------------------------
>
> Key: JBIDE-17987
> URL: https://issues.jboss.org/browse/JBIDE-17987
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta3
> Reporter: Rich DiCroce
>
> Assume you have an XHTML page that contains a JSF tag, and you want to use the EL 3.0 list literal to set an attribute on that tag, e.g.
> {code:xml}
> <my:tag someListProperty="#{[1, 2, 3]}"/>
> {code}
> The syntax is valid, but JBT reports the warning "EL syntax error: Expecting expression."
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17987) Bogus syntax warning for EL 3.0 list literal
by Rich DiCroce (JIRA)
Rich DiCroce created JBIDE-17987:
------------------------------------
Summary: Bogus syntax warning for EL 3.0 list literal
Key: JBIDE-17987
URL: https://issues.jboss.org/browse/JBIDE-17987
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.2.0.Beta3
Reporter: Rich DiCroce
Assume you have an XHTML page that contains a JSF tag, and you want to use the EL 3.0 list literal to set an attribute on that tag, e.g.
{code:xml}
<my:tag someListProperty="#{[1, 2, 3]}"/>
{code}
The syntax is valid, but JBT reports the warning "EL syntax error: Expecting expression."
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-17676:
----------------------------------------
[~vpakan], technically, the N&N is correct. JBT HTML editor does support some AngularJS specific content assist: angularJS attributes values, tags. But the N&N is not clear, I agree. It doesn't mention any limitations, e.g. content assist for {{}} expressions. We should have added more details in that N&N.
{quote}I do not have rights to access link you posted https://issues.jboss.org/secure/EditComment!default.jspa?id=12544745&comm...
https://issues.jboss.org/browse/JBIDE-17676?focusedCommentId=12987912&pag...
Please, let us know if that comment still misses some important information and it's still unclear for you what we do support and what we doesn't.
The main goal for now is to collect information about what we're still missing and our angularJS support comparing to angularJS IDE and what we can improve.
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, angularjs-ca-in-attributes.png, angularjs-ca-in-expressions.png, angularjs-highlighting.png, angularjs-hyperlink.png, jbt-html-ca-in-attributes.png, jbt-html-hyperlink.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month