July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3490) Include capabilities preference page into target-platform

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3490: -------------------------------- Fix Version/s: 9.0.0.CR1 > Include capabilities preference page into target-platform > --------------------------------------------------------- > > Key: JBDS-3490 > URL: https://issues.jboss.org/browse/JBDS-3490 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: javascript, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 9.0.0.CR1 > > > Currently there is no way to enable/disable capabilities to see hidden nodes in preferences/properties dialogs. It might be needed as a backup to be able to debug tern related issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3490) Include capabilities preference page into target-platform

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3490: -------------------------------- Priority: Critical (was: Major) > Include capabilities preference page into target-platform > --------------------------------------------------------- > > Key: JBDS-3490 > URL: https://issues.jboss.org/browse/JBDS-3490 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: javascript, target-platform > Affects Versions: 9.0.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 9.0.0.CR1 > > > Currently there is no way to enable/disable capabilities to see hidden nodes in preferences/properties dialogs. It might be needed as a backup to be able to debug tern related issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3490) Include capabilities preference page into target-platform

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3490: ----------------------------------- Summary: Include capabilities preference page into target-platform Key: JBDS-3490 URL: https://issues.jboss.org/browse/JBDS-3490 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Components: javascript, target-platform Affects Versions: 9.0.0.Beta2 Reporter: Denis Golovin Assignee: Denis Golovin Currently there is no way to enable/disable capabilities to see hidden nodes in preferences/properties dialogs. It might be needed as a backup to be able to debug tern related issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-646) Add info about installing Android SDK in Create Mobile Hybrid

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-646?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-646: ------------------------------------ PR with changes merged. > Add info about installing Android SDK in Create Mobile Hybrid > -------------------------------------------------------------- > > Key: TOOLSDOC-646 > URL: https://issues.jboss.org/browse/TOOLSDOC-646 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: General documentation issues > Affects Versions: 4.2.3.Final > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Priority: Minor > Fix For: 4.2.3.Final > > > Add data about installing Android SDK as a pre-requisite in the article (https://access.redhat.com/articles/1295913) > Also, add steps to add another emulator/change skin of existing one. > Discuss with [~mhusnain] where exactly to add these in the doc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19694) Angular Explorer doesn't show anything

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19694?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19694: --------------------------------------- Now I can replicate this: 1. Create ionic project using {code}ionic start myApp1 tabs{code} 2. Import it into JBDS Beta2 build 3. Open index.html 4. open Angular Explorer 5. Expand root node of Angular explorer !empty-modules.png! it is empty and the reason behind it is https://github.com/angelozerr/angularjs-eclipse/issues/155. I see this exception when tern tracing is enabled. After looking trough history I noticed several updates for tern+acorn and ternjs and one right before tagging the release. !tern-java-revisions.png! So I created dev environment with all sources in my workspace and switched to 113f1a17e0c40755a688368aee9a6d9f15909c05 revision selected on picture above. I get modules back and no exceptions in tern tracing. !filled-modules.png! > Angular Explorer doesn't show anything > -------------------------------------- > > Key: JBIDE-19694 > URL: https://issues.jboss.org/browse/JBIDE-19694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Alpha2 > Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64bit, Oracle Java 1.7 > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.0.CR1 > > Attachments: empty-modules.png, filled-modules.png, tern-java-revisions.png > > > # Import https://github.com/angular/angular-phonecat as New JavaScript project from existing source > # Checkout step-12 branch of imported project > # Open Angular Explorer > # Open index.html file of angular-phonecat project > ERROR: Angular Explorer is empty. It should contain angular controllers and modules > Was working fine with JBDS 8.1.0.GA and the same project configuration -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19694) Angular Explorer doesn't show anything

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19694?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19694: ---------------------------------- Attachment: empty-modules.png filled-modules.png tern-java-revisions.png > Angular Explorer doesn't show anything > -------------------------------------- > > Key: JBIDE-19694 > URL: https://issues.jboss.org/browse/JBIDE-19694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Alpha2 > Environment: JBDS 9.0.0.Alpha2-v20150421-1151-B25, Linux 64bit, Oracle Java 1.7 > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.0.CR1 > > Attachments: empty-modules.png, filled-modules.png, tern-java-revisions.png > > > # Import https://github.com/angular/angular-phonecat as New JavaScript project from existing source > # Checkout step-12 branch of imported project > # Open Angular Explorer > # Open index.html file of angular-phonecat project > ERROR: Angular Explorer is empty. It should contain angular controllers and modules > Was working fine with JBDS 8.1.0.GA and the same project configuration -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19949) Application wizard: Should automatically import once the resources are created

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19949?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19949: --------------------------------------- Why would we not import projects of all buildconfigs that are present? > Application wizard: Should automatically import once the resources are created > ------------------------------------------------------------------------------ > > Key: JBIDE-19949 > URL: https://issues.jboss.org/browse/JBIDE-19949 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Jeff Cantrill > Assignee: Andre Dietisheim > Labels: application_wizard, import_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > Run the new app from template wizard and import the app as an eclipse project when its complete > # EXEC: create new application for a v3 connection using some template > Result: > There's no Eclipse project imported once the wizard created the resources. I have to manually import the project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20372) Selecting Openshift v3 lists http://openshift.redhat.com

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20372?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20372: -------------------------------- Labels: application_wizard openshift_v3 (was: ) > Selecting Openshift v3 lists http://openshift.redhat.com > -------------------------------------------------------- > > Key: JBIDE-20372 > URL: https://issues.jboss.org/browse/JBIDE-20372 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Labels: application_wizard, openshift_v3 > > When creating a new OpenShift Application, if you select OpenShift 3, https://openshift.redhat.com is selected, but it's not a valid default url (yet) > The default value for v3 should be empty, until Openshift 3 gets a public url. > A default property could be set in https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j..., then updated asynchronously without rebuilding the openshift plugin -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20372) Selecting Openshift v3 lists http://openshift.redhat.com

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-20372: ----------------------------------- Summary: Selecting Openshift v3 lists http://openshift.redhat.com Key: JBIDE-20372 URL: https://issues.jboss.org/browse/JBIDE-20372 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Fred Bricon When creating a new OpenShift Application, if you select OpenShift 3, https://openshift.redhat.com is selected, but it's not a valid default url (yet) The default value for v3 should be empty, until Openshift 3 gets a public url. A default property could be set in https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j..., then updated asynchronously without rebuilding the openshift plugin -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20371) Need a link to download/install oc binary

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20371?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20371: -------------------------------- Labels: openshift_v3 port_forwarding_wizard (was: openshift_v3) > Need a link to download/install oc binary > ----------------------------------------- > > Key: JBIDE-20371 > URL: https://issues.jboss.org/browse/JBIDE-20371 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.3.0.CR1 > > > Currently there's no indication on how to get access and install the oc binary, required for at least using the port forwarding feature. We can not expect users to manually build it. > Best case scenario, eclipse provides a way to install it > Worst case scenario, it links to https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc#downloa... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 2015