July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17684) missing linked editor / linked console that we had in forge 1

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17684?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-17684: ----------------------------------------- I think this is already implemented, can anyone confirm it? > missing linked editor / linked console that we had in forge 1 > ------------------------------------------------------------- > > Key: JBIDE-17684 > URL: https://issues.jboss.org/browse/JBIDE-17684 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17693) Forge addon classifier extension should be included in Forge Tools by default

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17693?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-17693. ------------------------------------- Resolution: Done > Forge addon classifier extension should be included in Forge Tools by default > ----------------------------------------------------------------------------- > > Key: JBIDE-17693 > URL: https://issues.jboss.org/browse/JBIDE-17693 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Affects Versions: 4.2.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.2.0.CR1 > > Attachments: Screen Shot 2014-06-25 at 7.06.28 PM.png > > > The current JBoss Tools Forge does not include the forge classifier support, which means that anyone doing forge addon development will suffer from the problem where m2 Eclipse does not properly resolve classifiers for forge-addon projects. > This needs to be included in JBT Beta3: See screenshot. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[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 commented on JBIDE-17676: ------------------------------------- This is written in N&N {noformat} For such projects, JBoss Tools HTML editor now provides AngularJS specific code assist, navigation, etc. {noformat} And bellow this text is screenshot with code assist for {{phone.name}} Angular expression. If it is not saying we support code assist for Angular expressions it's at least very confusing to put such screeenshot bellow that text. I assumed that we support it and I think many other users will do. I do not have rights to access link you posted https://issues.jboss.org/secure/EditComment!default.jspa?id=12544745&comm... > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-17941) stop relying on snapshot for plugins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17941?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17941: ---------------------------------------- So our plugins were updated to build against Tycho 0.21.0, and versioned as 0.21.0-SNAPSHOT. I'll run a few component jobs, aggregate, product... and if within the end of the week no regression was noticed, I'll release this 0.21.0-SNAPSHOT as 0.21.0. > stop relying on snapshot for plugins > ------------------------------------ > > Key: JBIDE-17941 > URL: https://issues.jboss.org/browse/JBIDE-17941 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > while investigating why 0.19-snapshot is missing from http://repository.jboss.org/nexus/content/repositories/snapshots/org/jbos... I found that we seem to always use snapshot in our jbosstools parent pom for these plugins. > And we are now at 0.19 but there is only a 0.16 release. > these plugins should be released and we should depend on the released ones instead of snapshot. Snapshot version is fine for early development, but not for ever. > the only thing that we haven't found a way to make a real release of is the parent pom because of tycho/p2 limitations. But the rest should be releases. > Its worth nothing that any snapshot gets deleted after 90 days (https://community.jboss.org/wiki/MavenSnapshotRepository) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-17676: ----------------------------------------- There is NO information here (http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta2.html...) on that we (JBoss Tools HTML Editor) support content assist in Angular Expressions. There IS information on content assist in Angular Tag Attribute Values. Please, re-read carefully. Also see my comment on correct set up and difference between AngularJS Editor and JBoss Tools HTML Editor: https://issues.jboss.org/secure/EditComment!default.jspa?id=12544745&comm... > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-17018) TP validation seems to miss some error cases

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17018?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-17018. ------------------------------------ Resolution: Done The checkDependencies parameter was set on TP 4.40.x branch, which were by the way upgraded to use Tycho 0.21.0. On Discovery target-platforms, it doesn't make sense to enable it, since dependencies are managed through composite files (that don't exist when building TPs). > TP validation seems to miss some error cases > -------------------------------------------- > > Key: JBIDE-17018 > URL: https://issues.jboss.org/browse/JBIDE-17018 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > Using commit e7d0d56a481a239f3873f688da2dac14dafc2f15 of JBoss Tools target-platforms, it seems like we get in an unperfect state where some dependencies are missing and TP validation misses it. Cf JBIDE-16910 for details about failure that can happen with this commit. > So TP validation needs to be fixed to spot such issues. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[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 commented on JBIDE-17971: ------------------------------------------ merged and pushed to upstream/master > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-3078) 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3078?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3078: -------------------------------------- {quote}So we need to create a single ico file with all these sizes/params? {quote} I think so. > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-17985) Create Domain wizard: should be able to edit domain members

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17985?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-17985: ------------------------------------------ For this to happen we need the openshift-java-client to be able to add/remove/list domain members. The client library is currently not able to do that. > Create Domain wizard: should be able to edit domain members > ----------------------------------------------------------- > > Key: JBIDE-17985 > URL: https://issues.jboss.org/browse/JBIDE-17985 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Andre Dietisheim > Labels: domain_wizard, uxtest > Fix For: 4.3.x > > Attachments: OpenshiftDomainCreation_Step1.png, OpenshiftDomainCreation_Step2.png > > > 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 ) > !OpenshiftDomainCreation_Step1.png! > 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) > !OpenshiftDomainCreation_Step2.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17693) Forge addon classifier extension should be included in Forge Tools by default

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17693?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-17693: --------------------------------------- Assignee: George Gastaldi (was: Max Rydahl Andersen) > Forge addon classifier extension should be included in Forge Tools by default > ----------------------------------------------------------------------------- > > Key: JBIDE-17693 > URL: https://issues.jboss.org/browse/JBIDE-17693 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Affects Versions: 4.2.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.2.0.CR1 > > Attachments: Screen Shot 2014-06-25 at 7.06.28 PM.png > > > The current JBoss Tools Forge does not include the forge classifier support, which means that anyone doing forge addon development will suffer from the problem where m2 Eclipse does not properly resolve classifiers for forge-addon projects. > This needs to be included in JBT Beta3: See screenshot. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014