[JBoss JIRA] (JBDS-3078) 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3078?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3078:
----------------------------------
{quote}
(2014-07-28 12:09:18) mistria: 256x256, 32 bit (RGB / Alpha Channel)
(2014-07-28 12:09:20) mistria: 48x48, 32 bit (RGB / Alpha Channel)
(2014-07-28 12:09:22) mistria: 32x32, 32 bit (RGB / Alpha Channel)
(2014-07-28 12:09:24) mistria: 16x16, 32 bit (RGB / Alpha Channel)
(2014-07-28 12:09:26) mistria: 48x48, 8 bit (256 colors)
(2014-07-28 12:09:28) mistria: 32x32, 8 bit (256 colors)
(2014-07-28 12:09:30) mistria: 16x16, 8 bit (256 colors){quote}
https://github.com/jbdevstudio/jbdevstudio-product/tree/master/plugins/co... contains a variety of icons in different sizes / formats. I don't see an .ico, though, just .png and .icns, from 16x16 up to 128x128
So we need to create a single ico file with all these sizes/params?
> 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)
11 years, 8 months
[JBoss JIRA] (JBDS-3078) 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3078?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3078:
-------------------------------------------
This was done in past by [~dgolovin]
> 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)
11 years, 8 months
[JBoss JIRA] (JBIDE-17971) Domain wizard: should not be able to edit domain members as long as we did not create the domain
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17971:
-------------------------------------
Summary: Domain wizard: should not be able to edit domain members as long as we did not create the domain (was: New Domain wizard: should not be able to edit domain members as long as we did not create the domain)
> Domain wizard: should not be able to edit domain members as long as we did not create the domain
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17971
> URL: https://issues.jboss.org/browse/JBIDE-17971
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Labels: domain_wizard, uxtest
> Fix For: 4.2.0.CR1
>
> Attachments: null-link.png, OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png
>
>
> When creating a new OpenShift domain, if I click "Edit domain members" with the domain name left blank, I get the following error:
> https://www.evernote.com/shard/s230/sh/ce9003cb-7988-4cdd-a4bc-52b04b9123...
> !null-link.png!
> This error is not helpful - and it appears the real problem is that to edit domain members I must create the domain first.
> Suggest that we change the create domain dialog to do the following:
> 1. Enter domain name (this is all that is shown on the dialog. (Mockup attached )
> 2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached)
> Not sure if there was a reason we didn't add ability to edit the domain members directly here rather than kicking the user back into the openshift web console.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17971) Domain wizard: should not be able to edit domain members as long as we did not create the domain
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17971:
-------------------------------------
Issue Type: Bug (was: Enhancement)
> Domain wizard: should not be able to edit domain members as long as we did not create the domain
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17971
> URL: https://issues.jboss.org/browse/JBIDE-17971
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Labels: domain_wizard, uxtest
> Fix For: 4.2.0.CR1
>
> Attachments: null-link.png, OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png
>
>
> When creating a new OpenShift domain, if I click "Edit domain members" with the domain name left blank, I get the following error:
> https://www.evernote.com/shard/s230/sh/ce9003cb-7988-4cdd-a4bc-52b04b9123...
> !null-link.png!
> This error is not helpful - and it appears the real problem is that to edit domain members I must create the domain first.
> Suggest that we change the create domain dialog to do the following:
> 1. Enter domain name (this is all that is shown on the dialog. (Mockup attached )
> 2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached)
> Not sure if there was a reason we didn't add ability to edit the domain members directly here rather than kicking the user back into the openshift web console.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17971) Create Domain wizard: should not be able to edit domain members as long as we did not create the domain
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-17971:
------------------------------------------
I'm going for the simplest fix that's possible right now:
I wont show the link if we're creating a new domain, I only show it if we're editing an existing domain.
Your suggestion to have the domain-name getting uneditable once the domain is created and then showing the link is a good suggestion. It would spare me from closing the wizard and reopen it to edit the domain members. But the problem here is that it breaks the current workflow: the domain is created once you hit "Finish" which closes the dialog (that's the default in Eclipse unless something goes wrong). To be able implement your suggestion we need to redesign this wizard which I filed to JBIDE-17985
> Create Domain wizard: should not be able to edit domain members as long as we did not create the domain
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17971
> URL: https://issues.jboss.org/browse/JBIDE-17971
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Labels: domain_wizard, uxtest
> Fix For: 4.2.0.CR1
>
> Attachments: null-link.png, OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png
>
>
> When creating a new OpenShift domain, if I click "Edit domain members" with the domain name left blank, I get the following error:
> https://www.evernote.com/shard/s230/sh/ce9003cb-7988-4cdd-a4bc-52b04b9123...
> !null-link.png!
> This error is not helpful - and it appears the real problem is that to edit domain members I must create the domain first.
> Suggest that we change the create domain dialog to do the following:
> 1. Enter domain name (this is all that is shown on the dialog. (Mockup attached )
> 2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached)
> Not sure if there was a reason we didn't add ability to edit the domain members directly here rather than kicking the user back into the openshift web console.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17971) New Domain wizard: should not be able to edit domain members as long as we did not create the domain
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17971?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17971:
-------------------------------------
Summary: New Domain wizard: should not be able to edit domain members as long as we did not create the domain (was: Create Domain wizard: should not be able to edit domain members as long as we did not create the domain)
> New Domain wizard: should not be able to edit domain members as long as we did not create the domain
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17971
> URL: https://issues.jboss.org/browse/JBIDE-17971
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta2
> Reporter: Catherine Robson
> Assignee: Max Rydahl Andersen
> Labels: domain_wizard, uxtest
> Fix For: 4.2.0.CR1
>
> Attachments: null-link.png, OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png
>
>
> When creating a new OpenShift domain, if I click "Edit domain members" with the domain name left blank, I get the following error:
> https://www.evernote.com/shard/s230/sh/ce9003cb-7988-4cdd-a4bc-52b04b9123...
> !null-link.png!
> This error is not helpful - and it appears the real problem is that to edit domain members I must create the domain first.
> Suggest that we change the create domain dialog to do the following:
> 1. Enter domain name (this is all that is shown on the dialog. (Mockup attached )
> 2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached)
> Not sure if there was a reason we didn't add ability to edit the domain members directly here rather than kicking the user back into the openshift web console.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17964:
------------------------------------
[~maxandersen] good point, we've gone off topic here:
{quote}
Things to consider:
Add solutions entry for Integration stack that links to jbds (avoids adding yet another install scenario){quote} -- https://issues.jboss.org/browse/JBIDE-17964?focusedCommentId=12987743&pag...
Should we move that discussion to another JIRA such as JBTIS-288?
{quote}providing an entry for the IS content separate from the JBT or JBDS entry, which would be backed by a URL which contains BOTH JBT/JBTIS or JBDS/JBDSIS content, so that the IS features can be installed into a vanilla Eclipse{quote} --https://issues.jboss.org/browse/JBTIS-288
> add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-17964
> URL: https://issues.jboss.org/browse/JBIDE-17964
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: marketplace
> Affects Versions: 4.1.2.Final
> Reporter: Lars Heinemann
> Assignee: Nick Boldt
> Fix For: 4.1.2.Final
>
>
> Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17985) Create Domain wizard: should not be able to edit domain members as long as we did not create the domain
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-17985:
----------------------------------------
Summary: Create Domain wizard: should not be able to edit domain members as long as we did not create the domain
Key: JBIDE-17985
URL: https://issues.jboss.org/browse/JBIDE-17985
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Max Rydahl Andersen
Fix For: 4.2.0.CR1
Attachments: null-link.png, OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png
When creating a new OpenShift domain, if I click "Edit domain members" with the domain name left blank, I get the following error:
https://www.evernote.com/shard/s230/sh/ce9003cb-7988-4cdd-a4bc-52b04b9123...
!null-link.png!
This error is not helpful - and it appears the real problem is that to edit domain members I must create the domain first.
Suggest that we change the create domain dialog to do the following:
1. Enter domain name (this is all that is shown on the dialog. (Mockup attached )
2. Domain is created. Validation message shown on dialog header. The screen changes to show non-editable name and the ability to edit domain members. (Mockup attached)
Not sure if there was a reason we didn't add ability to edit the domain members directly here rather than kicking the user back into the openshift web console.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-17676 at 7/28/14 11:22 AM:
---------------------------------------------------------------
Thanks. Does it mean that we do not support content assist for AngularJS expressions in JBoss HTML editor (point 3. of previous comment)? So information written here is not correct http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta2.html... am I right?
was (Author: vpakan):
Thanks. Does it mean that we do not support content assist for AngularJS expressions? So information written here is not correct http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta2.html... am I right?
> 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)
11 years, 8 months