December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20584) CordovaSim doesn't talk to remote FH cloud app

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20584?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20584: ---------------------------------- Sprint: Sprint #10 September 2015 > CordovaSim doesn't talk to remote FH cloud app > ---------------------------------------------- > > Key: JBIDE-20584 > URL: https://issues.jboss.org/browse/JBIDE-20584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim, upstream > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.x > > Attachments: remote.png > > > I found several issue connected with CordovaSim FH & cordova.js >= 4.0.0: > -1) Running against *local* FH cloud app fails with disabled proxy (need to use local by default)- (UPD: reported as a separated issue - JBIDE-20590) > 2) Running against *remote* FH cloud app does not work with cordovasim at all (for remote proxy the error is the following): > {code} > XMLHttpRequest cannot load https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippo.... Cannot use wildcard in Access-Control-Allow-Origin when credentials flag is true. > {code} > -Literally, this cordova hello world app does not work against FH app preview (It used to work before)- (UPD: not a bug the app must be deployed firstly - JBIDE-20606)!remote.png|thumbnail!*strong text* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20387: ---------------------------------- Sprint: (was: Sprint #9 September 2016) > Use column number when navigating to errors, and more > ----------------------------------------------------- > > Key: JBIDE-20387 > URL: https://issues.jboss.org/browse/JBIDE-20387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.3.0.Beta2 > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.x > > > The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): > * {{getColumnNumber()}}, {{getEndColumnNumber()}} > * {{getEndLineNumber()}} > * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20387) Use column number when navigating to errors, and more

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20387?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20387: ---------------------------------- Sprint: Sprint #10 September 2015 > Use column number when navigating to errors, and more > ----------------------------------------------------- > > Key: JBIDE-20387 > URL: https://issues.jboss.org/browse/JBIDE-20387 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: freemarker > Affects Versions: 4.3.0.Beta2 > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.x > > > The plugin doesn't utilize some tooling-centric information available in {{freemarker.core.ParseException}}, most importantly, the column number that Eclipse could utilize to jump at the error start inside the line. The information that's not used is (see {{plugins/org.jboss.ide.eclipse.freemarker/src/org/jboss/ide/eclipse/freemarker/editor/Editor.java}}): > * {{getColumnNumber()}}, {{getEndColumnNumber()}} > * {{getEndLineNumber()}} > * {{getEditorMessage()}}: This should be used instead of {{getMessage()}} (though apparently the output of `getMessage()` is identical, it's actually because FM detects that it was called from JBoss Tools and then creates a message customized for that). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21171) Need to remove bower / npm from jboss.tools.jsdt

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21171?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-21171: --------------------------------------- Don't forget to create PR to remove it form # https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... # https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > Need to remove bower / npm from jboss.tools.jsdt > ------------------------------------------------ > > Key: JBIDE-21171 > URL: https://issues.jboss.org/browse/JBIDE-21171 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, nodejs > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Assuming that bower / npm were moved to eclipse jsdt - https://git.eclipse.org/r/#/c/61336/ > Need to perform a cleanup in jboss.tools.jst.jsdt repo and remove related plugins / tests / features > Bower is in eclipse upstream and we probably will need reflect it in new & noteworthy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21180) Update tern.java and angular-eclipse to 1.1.0 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21180?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-21180: ---------------------------------- Fix Version/s: 4.3.1.Beta1 > Update tern.java and angular-eclipse to 1.1.0 release > ----------------------------------------------------- > > Key: JBIDE-21180 > URL: https://issues.jboss.org/browse/JBIDE-21180 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript > Affects Versions: 4.3.1.Beta1 > Reporter: Denis Golovin > Fix For: 4.3.1.Beta1 > > > We should update version of tern.java and Angular.js to the latest released version which is 1.1.0 and let loose version restrictions for tern to let manual install for latest nightly releases. > Mirrors are available under: > http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.1.0... > http://download.jboss.org/jbosstools/updates/requirements/tern/1.1.0.2015... > New features description can be found here: > https://github.com/angelozerr/tern.java/wiki/New-and-Noteworthy-1.1.0 > https://github.com/angelozerr/angularjs-eclipse/wiki/New-and-Noteworthy-1... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21180) Update tern.java and angular-eclipse to 1.1.0 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21180?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-21180: ------------------------------------- Assignee: Denis Golovin > Update tern.java and angular-eclipse to 1.1.0 release > ----------------------------------------------------- > > Key: JBIDE-21180 > URL: https://issues.jboss.org/browse/JBIDE-21180 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript > Affects Versions: 4.3.1.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.1.Beta1 > > > We should update version of tern.java and Angular.js to the latest released version which is 1.1.0 and let loose version restrictions for tern to let manual install for latest nightly releases. > Mirrors are available under: > http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.1.0... > http://download.jboss.org/jbosstools/updates/requirements/tern/1.1.0.2015... > New features description can be found here: > https://github.com/angelozerr/tern.java/wiki/New-and-Noteworthy-1.1.0 > https://github.com/angelozerr/angularjs-eclipse/wiki/New-and-Noteworthy-1... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21180) Update tern.java and angular-eclipse to 1.1.0 release

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-21180: ------------------------------------- Summary: Update tern.java and angular-eclipse to 1.1.0 release Key: JBIDE-21180 URL: https://issues.jboss.org/browse/JBIDE-21180 Project: Tools (JBoss Tools) Issue Type: Task Components: javascript Affects Versions: 4.3.1.Beta1 Reporter: Denis Golovin We should update version of tern.java and Angular.js to the latest released version which is 1.1.0 and let loose version restrictions for tern to let manual install for latest nightly releases. Mirrors are available under: http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.1.0... http://download.jboss.org/jbosstools/updates/requirements/tern/1.1.0.2015... New features description can be found here: https://github.com/angelozerr/tern.java/wiki/New-and-Noteworthy-1.1.0 https://github.com/angelozerr/angularjs-eclipse/wiki/New-and-Noteworthy-1... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.x) > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18743: ------------------------------------ Seems Max wants more than just that... an example is that there's a couple of old orphan composite sites: * http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.3.... * http://download.jboss.org/jbosstools/builds/staging/_composite_/core/master/ which are no longer valid because we moved things around a year ago in support of JBDS-3208 (moving to the new /mars/snapshots/ structure instead of /builds/staging/). If you point p2browser at the first site, you get: {code} Problems loading repository No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_4.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-arquillian.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-birt_4.3.m.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-browsersim.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-central_4..... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_4.3..... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-hibernate_.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-javaee_4.3.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-jst_4.3.ma.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-livereload.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-server_4.3.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-vpe_4.3.ma.... No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-webservice.... {code} Or, if you run it with the -consolelog flag, you get console log details like: {code} !ENTRY org.eclipse.equinox.p2.core 4 0 2015-12-03 13:05:19.958 !MESSAGE Provisioning exception !STACK 1 org.eclipse.equinox.p2.core.ProvisionException: No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_4.... at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:393) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:675) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:165) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:105) at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:758) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:651) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) at com.ifedorenko.p2browser.views.MetadataRepositoryView.loadRepository(MetadataRepositoryView.java:614) at com.ifedorenko.p2browser.views.MetadataRepositoryView.access$13(MetadataRepositoryView.java:599) at com.ifedorenko.p2browser.views.MetadataRepositoryView$12.run(MetadataRepositoryView.java:524) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 org.eclipse.equinox.p2.metadata.repository 4 1000 2015-12-03 13:05:19.960 !MESSAGE No repository found at http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_4.... {code} So we could potentially run this in Jenkins to read sites and check their contents, then parse the console log for "No repository found at ..." messages. > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Fix For: 4.3.x > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21176) [CDK] installing cdk feature should install docker feature

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21176?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21176: ------------------------------------- > avoid unexpected nastiness should the o.e.lt.docker.feature change API unexpectedly I add manifest.mf plugin deps when I have an API requirement on the plugin. When I just want the entire feature added, I use feature requirements. > or start including things that conflict w/ the rest of JBT. Well, that's interesting. I guess that's something to be aware of. > [CDK] installing cdk feature should install docker feature > ---------------------------------------------------------- > > Key: JBIDE-21176 > URL: https://issues.jboss.org/browse/JBIDE-21176 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.Beta1 > > > CDK Feature should also install docker feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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