September 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3511) Remove OpenShift 3 Tooling from JBDS installer/BYOE

by Fred Bricon (JIRA)

Fred Bricon created JBDS-3511: --------------------------------- Summary: Remove OpenShift 3 Tooling from JBDS installer/BYOE Key: JBDS-3511 URL: https://issues.jboss.org/browse/JBDS-3511 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: build, marketplace Affects Versions: 9.0.0.CR1 Reporter: Fred Bricon Priority: Blocker Fix For: 9.0.0.CR1 For JBT 4.3 _and_ JBDS 9, OpenShift 3 will be available as TechPreview from JBoss Central. As a consequence, it needs to be removed from the JBDS installer, the BYOE marketplace installation and the default JBT update site -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20555) Create OpenShift 3 tooling connector for JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20555?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20555: ----------------------------------- Assignee: Nick Boldt > Create OpenShift 3 tooling connector for JBoss Central > ------------------------------------------------------ > > Key: JBIDE-20555 > URL: https://issues.jboss.org/browse/JBIDE-20555 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, central, openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.CR1 > > > For JBT 4.3 _and_ JBDS 9, OpenShift 3 will be available as TechPreview from JBoss Central. The Central discovery catalog needs to list it as a new connector. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20555) Create OpenShift 3 tooling connector for JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20555?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20555: -------------------------------- Fix Version/s: 4.3.0.CR1 > Create OpenShift 3 tooling connector for JBoss Central > ------------------------------------------------------ > > Key: JBIDE-20555 > URL: https://issues.jboss.org/browse/JBIDE-20555 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, central, openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.CR1 > > > For JBT 4.3 _and_ JBDS 9, OpenShift 3 will be available as TechPreview from JBoss Central. The Central discovery catalog needs to list it as a new connector. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20555) Create OpenShift 3 tooling connector for JBoss Central

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-20555: ----------------------------------- Summary: Create OpenShift 3 tooling connector for JBoss Central Key: JBIDE-20555 URL: https://issues.jboss.org/browse/JBIDE-20555 Project: Tools (JBoss Tools) Issue Type: Task Components: build, central, openshift Affects Versions: 4.3.0.CR1 Reporter: Fred Bricon Priority: Blocker For JBT 4.3 _and_ JBDS 9, OpenShift 3 will be available as TechPreview from JBoss Central. The Central discovery catalog needs to list it as a new connector. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20545) Migrate to tern-java and angularjs-eclipse 1.0.0 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20545?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-20545: --------------------------------------- Release mirrors are ready and available from: * http://download.jboss.org/jbosstools/updates/requirements/angularjs/1.0.0... * http://download.jboss.org/jbosstools/updates/requirements/tern/1.0.0.2015... > Migrate to tern-java and angularjs-eclipse 1.0.0 release > -------------------------------------------------------- > > Key: JBIDE-20545 > URL: https://issues.jboss.org/browse/JBIDE-20545 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.CR1 > > > We should test manually latest tern-java and angularjs-eclipse release 1.0.0 until Reddeer tests arrived and see if it is good enough to include into CR1. > Major improvements in tern are: > 1. Support include/exclude from JavaScript projects > 2. tern server update > 3. Issues caused problems last release asre fixed -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 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 commented on JBIDE-20442: --------------------------------------- Test cases looks good to start with, I am going to run them manually to see if I have something to add. [~vpakan] do you have time to implement them as Reddeer UI tests till code freeze? > 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.0.CR1 > > > 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.3.15#6346)

10 years, 7 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 edited comment on JBIDE-20442 at 9/2/15 9:02 PM: --------------------------------------------------------------- I guess this is more for [~vpakan] than for [~psrna]. [~vpakan] tests Tern/Angular, doesn't he? was (Author: akazakov): I guess this is more for [~vpakan] than for [~psrna]. [~vpakan] tests Tern/Anfular, doesn't he? > 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.0.CR1 > > > 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.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3490) Include capabilities preference page into jbdevstudio product

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3490: ------------------------------------- Working PR attached. > Include capabilities preference page into jbdevstudio product > ------------------------------------------------------------- > > 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: Blocker > Fix For: 9.0.0.CR1 > > Attachments: 3490-error.png, jbds-preferences.png > > > 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 for example tern related issues. > Current approach is using capabilities to hide Tern category from Preferences and Properties dialogs. If something goes wrong there is no way to see preferences and properties in hidden categories, because Capabilities Preference page is not included into ibdevstudio product. Before it was included by default but in Mars release it seems moved to EPP side. For example Committer Package does not provide Capabilities preference page, but Java EE Package does. > In current devstudio product package preferences categories looks like > !jbds-preferences.png! > as you see there is no Capabilities node in categories tree (1) because Capabilities preference page is not defined for jbdevstudio product and Tern node (2) is filtered out by default. It means in case of any problem with tern it is not possible do enable tern console tracing using Tern Preferences or see node.js configuration. > It is probably should be implemented as additional feature/plugin to include it into JBDS product, but it should beexcluded from BYOE feature to avoid preferences categories conflict in case of installation BYOE feature into Java EE EPP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3490) Include capabilities preference page into jbdevstudio product

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3490: -------------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/336 (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/329, https://github.com/jbdevstudio/jbdevstudio-product/pull/332) > Include capabilities preference page into jbdevstudio product > ------------------------------------------------------------- > > 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: Blocker > Fix For: 9.0.0.CR1 > > Attachments: 3490-error.png, jbds-preferences.png > > > 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 for example tern related issues. > Current approach is using capabilities to hide Tern category from Preferences and Properties dialogs. If something goes wrong there is no way to see preferences and properties in hidden categories, because Capabilities Preference page is not included into ibdevstudio product. Before it was included by default but in Mars release it seems moved to EPP side. For example Committer Package does not provide Capabilities preference page, but Java EE Package does. > In current devstudio product package preferences categories looks like > !jbds-preferences.png! > as you see there is no Capabilities node in categories tree (1) because Capabilities preference page is not defined for jbdevstudio product and Tern node (2) is filtered out by default. It means in case of any problem with tern it is not possible do enable tern console tracing using Tern Preferences or see node.js configuration. > It is probably should be implemented as additional feature/plugin to include it into JBDS product, but it should beexcluded from BYOE feature to avoid preferences categories conflict in case of installation BYOE feature into Java EE EPP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19952) v3 Application wizard: Template label decorators don't go away

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19952?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-19952 at 9/2/15 3:47 PM: --------------------------------------------------------------- [~jcantrill] What version of Linux/GTK do you use? I have tested on Ubuntu 14.04 (GTK2, GTK 3.10.8 and GTK 3.14.12). was (Author: snjeza): [~jcantrill] What version of Linux/GTK do you use? I have tested on Ubuntu 14.04 (GTK2, GTK 3.8 and GTK 3.14.12). > v3 Application wizard: Template label decorators don't go away > -------------------------------------------------------------- > > Key: JBIDE-19952 > URL: https://issues.jboss.org/browse/JBIDE-19952 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Snjezana Peco > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > Attachments: additional-error-marker.png, inital_opeon_on_linux.png, Resource Label dialog.png, validators.png > > > While adding a new label when creating a template, the validation decorator persists and sometime the validation message even for valid labels. See attachment. > Also, noticed focusing away from dialog and back makes them go away. Repainting issue? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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