December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19730) Build Improvement

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19730: ---------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #7 July 2015, Sprint #8 August 2015, Sprint #10 September 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #7 July 2015, Sprint #8 August 2015) > Build Improvement > ----------------- > > Key: JBIDE-19730 > URL: https://issues.jboss.org/browse/JBIDE-19730 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > > Epic to track issues related to improving how we release software. > This may include tools & workflows to improve how we build, what we build, how we release, process automation, Jenkins, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19730) Build Improvement

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19730?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19730: ---------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #7 July 2015, Sprint #8 August 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #7 July 2015, Sprint #8 August 2015, Sprint #9 September 2016) > Build Improvement > ----------------- > > Key: JBIDE-19730 > URL: https://issues.jboss.org/browse/JBIDE-19730 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > > Epic to track issues related to improving how we release software. > This may include tools & workflows to improve how we build, what we build, how we release, process automation, Jenkins, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19259) JSF or HTML5 support choosing issues

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19259?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19259: ---------------------------------- Sprint: Sprint #1 April 2015, Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015 (was: Sprint #1 April 2015, Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, Sprint #9 September 2016) > JSF or HTML5 support choosing issues > ------------------------------------ > > Key: JBIDE-19259 > URL: https://issues.jboss.org/browse/JBIDE-19259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.3.0.Alpha1 > Environment: Fedora 20 GNOME 64 bit, Open JDK 7, Alpha2-v20150212-0919-B9496 > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.3.x > > > # -GKT2 + xulrunner loaded + JSF support enabled: HTML5 page not rendered - visual part of VPE should contain similar message as in case HTML5 support is enabled for XHTML page informing users about possibility to enable HTML5 suppport-(won't fix) > # -VPE Preference page should contain checkbox with choice: "Always ask" otherwise user will never be able to get dialog asking to choose between JSF and HTML5 support once he will check check box "Do not show this message again"-(fixed) > # When support is changed page is opened and then Eclipse is restarted it would look better if page won't be opened before Eclipse is restarted. Page should be opened after restart > # -With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden it would be more user friendly just disable it and add some label why it's disabled?.The same way as selecting of GTK for BrowserSim/CordovaSim works.-(fixed) > # Confusing scenario #1: > ## Set HTML5 support > ## Open .xhtml page and say "Stay with HTML5" > ## Open .html page > ## Restart Eclipse > ## Close .html page > ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed. It's confusing to ask this when page is closed. > # Confusing scenario #2: > ## Set HTML5 support > ## Open .xhtml page and say "Stay with HTML5" > ## Restart Eclipse > ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19721) look at fixing quickaccess resizing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19721?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19721: ---------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, Sprint #10 September 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015) > look at fixing quickaccess resizing > ----------------------------------- > > Key: JBIDE-19721 > URL: https://issues.jboss.org/browse/JBIDE-19721 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.3.x > > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=432688 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3191: -------------------------------- Sprint: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, Sprint #9 September 2016) > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 9.x > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3191: -------------------------------- Sprint: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, Sprint #10 September 2015 (was: Sprint #2 April 2015, Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015) > Improve the way we switch between development and GA > ---------------------------------------------------- > > Key: JBDS-3191 > URL: https://issues.jboss.org/browse/JBDS-3191 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 9.x > > > JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream. > We need to improve that. > Changes are necessary in: > * features/com.jboss.devstudio.core/feature/p2.inf > * site/associate.properties > * results/pom.xml > As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there. > Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA. > The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties). > CC [~nickboldt] [~maxandersen] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20442: ---------------------------------- Sprint: (was: Sprint #9 September 2016) > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20442: ---------------------------------- Sprint: Sprint #10 September 2015 > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.x > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19721) look at fixing quickaccess resizing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19721?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19721: ---------------------------------- Sprint: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015 (was: Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015, Sprint #8 August 2015, Sprint #9 September 2016) > look at fixing quickaccess resizing > ----------------------------------- > > Key: JBIDE-19721 > URL: https://issues.jboss.org/browse/JBIDE-19721 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Fix For: 4.3.x > > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=432688 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[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: (was: Sprint #9 September 2016) > 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

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