August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18136) iBeacon plugin problem, can´t compile app

by eduardo de souza (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18136?page=com.atlassian.jira.plugi... ] eduardo de souza updated JBIDE-18136: ------------------------------------- Issue Type: Bug (was: Feature Request) > iBeacon plugin problem, can´t compile app > ----------------------------------------- > > Key: JBIDE-18136 > URL: https://issues.jboss.org/browse/JBIDE-18136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: eduardo de souza > Assignee: Gorkem Ercan > Priority: Critical > > I have created a Hybrid Mobile App, then added an iBeacon plugin: > https://github.com/petermetz/cordova-plugin-ibeacon.git > Then I tried to compile to see if there was any problem. I got this message: > An internal error occurred during: "Launching TesteApp4 (Android Device)". > java.lang.NullPointerException -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3115) Include Ionic Palette in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3115?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3115 at 8/27/14 10:41 AM: ------------------------------------------------------------ After applying your PR I see that the AngularJS connector in JBT vs. JBDS is different in Early Access: in Tools the included feature is *org.jboss.tools.jst.feature* whereas in Studio the included feature is *org.jboss.tools.jst.jsdt.feature* !3115-jbds-vs-jbt-connector.differences.png! In the Central discovery, I see that the org.jboss.tools.aerogear.hybrid connector contains *org.jboss.tools.jst.jsdt.feature* in Tools but not in Studio. !!3115-jbds-vs-jbt-connector.differences.central.png! Is this intentional, [~dgolovin], [~maxandersen] ? was (Author: nickboldt): After applying your PR I see that the AngularJS connector in JBT vs. JBDS is different: in Tools the included feature is *org.jboss.tools.jst.feature* whereas in Studio the included feature is *org.jboss.tools.jst.jsdt.feature* Is this intentional, [~dgolovin] ? > Include Ionic Palette in Central > -------------------------------- > > Key: JBDS-3115 > URL: https://issues.jboss.org/browse/JBDS-3115 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: p2-product > Affects Versions: 8.0.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 8.0.0.CR1 > > Attachments: 3115-jbds-vs-jbt-connector.differences.central.png, 3115-jbds-vs-jbt-connector.differences.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3115) Include Ionic Palette in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3115?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3115 at 8/27/14 10:41 AM: ------------------------------------------------------------ After applying your PR I see that the AngularJS connector in JBT vs. JBDS is different in Early Access: in Tools the included feature is *org.jboss.tools.jst.feature* whereas in Studio the included feature is *org.jboss.tools.jst.jsdt.feature* [^3115-jbds-vs-jbt-connector.differences.png] In the Central discovery, I see that the org.jboss.tools.aerogear.hybrid connector contains *org.jboss.tools.jst.jsdt.feature* in Tools but not in Studio. [^3115-jbds-vs-jbt-connector.differences.central.png] Is this intentional, [~dgolovin], [~maxandersen] ? was (Author: nickboldt): After applying your PR I see that the AngularJS connector in JBT vs. JBDS is different in Early Access: in Tools the included feature is *org.jboss.tools.jst.feature* whereas in Studio the included feature is *org.jboss.tools.jst.jsdt.feature* !3115-jbds-vs-jbt-connector.differences.png! In the Central discovery, I see that the org.jboss.tools.aerogear.hybrid connector contains *org.jboss.tools.jst.jsdt.feature* in Tools but not in Studio. !!3115-jbds-vs-jbt-connector.differences.central.png! Is this intentional, [~dgolovin], [~maxandersen] ? > Include Ionic Palette in Central > -------------------------------- > > Key: JBDS-3115 > URL: https://issues.jboss.org/browse/JBDS-3115 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: p2-product > Affects Versions: 8.0.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 8.0.0.CR1 > > Attachments: 3115-jbds-vs-jbt-connector.differences.central.png, 3115-jbds-vs-jbt-connector.differences.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3115) Include Ionic Palette in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3115?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3115: ----------------------------- Attachment: 3115-jbds-vs-jbt-connector.differences.central.png > Include Ionic Palette in Central > -------------------------------- > > Key: JBDS-3115 > URL: https://issues.jboss.org/browse/JBDS-3115 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: p2-product > Affects Versions: 8.0.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 8.0.0.CR1 > > Attachments: 3115-jbds-vs-jbt-connector.differences.central.png, 3115-jbds-vs-jbt-connector.differences.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3115) Include Ionic Palette in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3115?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3115: ----------------------------- Attachment: 3115-jbds-vs-jbt-connector.differences.png After applying your PR I see that the AngularJS connector in JBT vs. JBDS is different: in Tools the included feature is *org.jboss.tools.jst.feature* whereas in Studio the included feature is *org.jboss.tools.jst.jsdt.feature* Is this intentional, [~dgolovin] ? > Include Ionic Palette in Central > -------------------------------- > > Key: JBDS-3115 > URL: https://issues.jboss.org/browse/JBDS-3115 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: p2-product > Affects Versions: 8.0.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 8.0.0.CR1 > > Attachments: 3115-jbds-vs-jbt-connector.differences.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18105) generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18105: ------------------------------------ As discussed today, sounds like the best approach here is to XSLT from plugin.xml -> a properties file like https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent... because the discovery plugin.xml already contains the explicit list of features which we consider EA. Using p2 would pull in all the dependent features too, which is more than we want tagged as EA in the UI (JBIDE-17808). > generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target > ---------------------------------------------------------------------- > > Key: JBIDE-18105 > URL: https://issues.jboss.org/browse/JBIDE-18105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. > Currently the properties file looks like this: > https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17808: ------------------------------------ To read properties from http://download.jboss.org/jbosstools/configuration/ide-config.properties see https://github.com/jbosstools/jbosstools-central/blob/master/examples/plu... or https://github.com/jbosstools/jbosstools-central/blob/master/examples/plu... > Identify which installed IUs are from Early Access vs. supported/tested versions > -------------------------------------------------------------------------------- > > Key: JBIDE-17808 > URL: https://issues.jboss.org/browse/JBIDE-17808 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: documentation > Fix For: 4.2.0.CR1 > > Attachments: JBIDE17808.jpeg > > > [~maxandersen] brought up a good point on a call today: > we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location. > Thus we need some sort of UI to list installed IUs that are "Early Access". > This could be... (brainstorming now): > * a text file with the list of things installed from Early Access (features and plugins) > * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins > * a way to filter the plugin view (Help > About) to show only EA content (or exclude it) > * ... ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17233) Add usage tracking for the WS Tester

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17233?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-17233: ------------------------------------- Assignee: Alexey Kazakov (was: Xavier Coulon) [~akazakov], Can you review this PR and let me know if the way I count the events (when a JAX-WS or JAX-RS request is submitted) is correct ? Thanks ! > Add usage tracking for the WS Tester > ------------------------------------ > > Key: JBIDE-17233 > URL: https://issues.jboss.org/browse/JBIDE-17233 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.2.0.Beta1 > Reporter: Xavier Coulon > Assignee: Alexey Kazakov > Fix For: 4.2.0.CR1 > > > Add usage tracking when the WS Tester is opened and when a request is submitted, so we can see how many people use it (or not) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3125) JBDS shouldn't link to download.jboss.org

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3125?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3125: ------------------------------------------- I believe so. The culprit is http://devstudio.jboss.com/updates/7.0/extras/compositeContent.xml > JBDS shouldn't link to download.jboss.org > ----------------------------------------- > > Key: JBDS-3125 > URL: https://issues.jboss.org/browse/JBDS-3125 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Mickael Istria > Priority: Critical > Fix For: 8.0.0.GA > > > JBoss Developer Studio links to download.jboss.org to link to the target-platform. > Instead, the JBDS target-platform should be published on devstudio.jboss.com and JBDS should link to this repository. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18136) iBeacon plugin problem, can´t compile app

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18136?page=com.atlassian.jira.plugi... ] Gorkem Ercan reassigned JBIDE-18136: ------------------------------------ Assignee: Gorkem Ercan > iBeacon plugin problem, can´t compile app > ----------------------------------------- > > Key: JBIDE-18136 > URL: https://issues.jboss.org/browse/JBIDE-18136 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: eduardo de souza > Assignee: Gorkem Ercan > Priority: Critical > > I have created a Hybrid Mobile App, then added an iBeacon plugin: > https://github.com/petermetz/cordova-plugin-ibeacon.git > Then I tried to compile to see if there was any problem. I got this message: > An internal error occurred during: "Launching TesteApp4 (Android Device)". > java.lang.NullPointerException -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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 August 2014