May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3909) rebrand dev platform installer as Red Hat Development Suite

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3909?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3909: -------------------------------- Priority: Blocker (was: Major) > rebrand dev platform installer as Red Hat Development Suite > ----------------------------------------------------------- > > Key: JBDS-3909 > URL: https://issues.jboss.org/browse/JBDS-3909 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > Per decision made last week in https://trello.com/c/Cbo0q8TT/99-rebrand-jbds-as-rhds-using-rhd-logo and https://docs.google.com/presentation/d/1Ub-egAS7nbzFijKCTnUk7GJP8WPCQC28q... we need to refactor the platform installer to be the Development Suite installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22460) Test classes should be in the same package as the class(es) under test

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22460?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22460: ------------------------------------- the only reason why we're not using fragments is because then we'd need 1 test plugin per main plugin. I have no strong objections against adding more test plugins. It's just more work and is definitely not something planned for this release. > Test classes should be in the same package as the class(es) under test > ----------------------------------------------------------------------- > > Key: JBIDE-22460 > URL: https://issues.jboss.org/browse/JBIDE-22460 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Priority: Minor > Labels: test > Fix For: 4.4.x > > > Test classes should be in the same package as the class(es) under test as it is a generally admitted pattern and as it allows to use package protected classes/methods -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3894) Refactor discovery plugins/TPs from jbds/jbdevstudio to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3894?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3894: ----------------------------- Sprint: (was: devex #115 May 2016) > Refactor discovery plugins/TPs from jbds/jbdevstudio to devstudio > ----------------------------------------------------------------- > > Key: JBDS-3894 > URL: https://issues.jboss.org/browse/JBDS-3894 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: central-update, target-platform, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > In https://github.com/jbosstools/jbosstools-discovery/ we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio and jbds. > Affected: publishing/staging/release scripts, discovery sites, jenkins jobs, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3893) Refactor target platforms from jbdevstudio to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3893?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3893: ----------------------------- Sprint: (was: devex #115 May 2016) > Refactor target platforms from jbdevstudio to devstudio > ------------------------------------------------------- > > Key: JBDS-3893 > URL: https://issues.jboss.org/browse/JBDS-3893 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: target-platform, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > In https://github.com/jbosstools/jbosstools-target-platforms/commits/4.60.x we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio. > Affected: publishing/staging/release scripts, jenkins jobs, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3909) rebrand dev platform installer as Red Hat Development Suite

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3909?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3909: ----------------------------- Fix Version/s: 10.0.0.Alpha3 > rebrand dev platform installer as Red Hat Development Suite > ----------------------------------------------------------- > > Key: JBDS-3909 > URL: https://issues.jboss.org/browse/JBDS-3909 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha3 > > > Per decision made last week in https://trello.com/c/Cbo0q8TT/99-rebrand-jbds-as-rhds-using-rhd-logo and https://docs.google.com/presentation/d/1Ub-egAS7nbzFijKCTnUk7GJP8WPCQC28q... we need to refactor the platform installer to be the Development Suite installer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22460) Test classes should be in the same package as the class(es) under test

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22460?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22460: ------------------------------------ I agree, I tested it with fragments but for a yet unknown reasons, fragments are not welcome > Test classes should be in the same package as the class(es) under test > ----------------------------------------------------------------------- > > Key: JBIDE-22460 > URL: https://issues.jboss.org/browse/JBIDE-22460 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Priority: Minor > Labels: test > Fix For: 4.4.x > > > Test classes should be in the same package as the class(es) under test as it is a generally admitted pattern and as it allows to use package protected classes/methods -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22459: ------------------------------------- Pasting notes from http://etherpad.corp.redhat.com/dcpmultiversion {quote} A) DCP1 vs DCP2 * DCP1 hard to maintain, DCP2 things can be changed. Used in two places: Eclipse Help Search (low priority) JBoss Central (higher priority) Options: 1) keep dcp1 alive for 3+ years 2) make dcp2 output dcp1 format for 3+ years output has changed because of upgrade of elasticsearch. limited resources since Lukas Vlcek. left, dcp in maintenance mode so far. Idea: could we have a "transforming" proxy that converts dcp2 json to dcp1 json. should be trivial. 3) we "fake" dcp1 by having a static page somewhere that gets updated once in a while. Suggest: we just make devstudio 9.1 use a static output - do changes in devstudio 10. B) EAP 7 quickstarts multiversion have been downprioritized: not on Ray and Harry's radar. Paul - look into how hard it can be done ? let us known Wednesday lunch time. Paul's Observations: Realistically we will not have multi-version support in JBD and thus DCP1 data. Also, we will need to update the JBD EAP Quickstarts to v7 (and thus the DCP1 data). Therefore, I don't see an outcome where JBDS 9 isn't showing only v7 quickstarts for EAP. Fred's Idea: Cache the results for EAP 6 and redirect the JBDS 9 code to get that. Potentially, we could cache the EAP 6 results prior to the DCP1 data being changed to have EAP 7 quickstarts. After this change, take another snapshot of the data. Merging these two snapshots results in a multi-version snapshot to provide to JBDS 9. Only give JBDS 9 multi-version support if JBDS 10 also gets this support. Otherwise a regression is created. {quote} > Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22459 > URL: https://issues.jboss.org/browse/JBIDE-22459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats. > In the context of EAP 7 coming out there are new quickstarts. > In a perfect world the following have happend: > EAP 7 Quickstarts added to DCP > Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts > What seem to have happened instead is: > if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available > DCP has changed its format/approach and not sure what the impact of this is > (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?) > This bug is to gather the facts and figure out what we do about them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22463) Update CDK code after API change in Docker tooling

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22463?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-22463: ------------------------------------- Assignee: Xavier Coulon > Update CDK code after API change in Docker tooling > -------------------------------------------------- > > Key: JBIDE-22463 > URL: https://issues.jboss.org/browse/JBIDE-22463 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, server > Affects Versions: 4.4.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > > The APi to create a connection changed in the latest version of Docker tooling. This impacts the {{CDKDockerUtility}} class in the {{org.jboss.tools.openshift.cdk.server}} bundle. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21441) Consume m2e Easymport integration from upstream

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21441?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-21441. --------------------------------- Verified in: Version: 10.0.0.Alpha1 Build id: Alpha1-v20160520-1027-B5398 Build date: 20160520-1027 > Consume m2e Easymport integration from upstream > ----------------------------------------------- > > Key: JBIDE-21441 > URL: https://issues.jboss.org/browse/JBIDE-21441 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: maven, playground, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha2 > > > *Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport. > That would require to get a recent version of m2e in TP. > *Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import > *Version:* 1.7.0 > *License and owner:* EPL, m2e project (Eclipse.org > *Original p2 repo:* http://download.eclipse.org/technology/m2e/snapshots/1.7.0/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e/1.7.0.20160... > *Include Sources:* No > *Affected JBoss Tools components:* playground, maven > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > + org.eclipse.m2e.importer > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22463) Update CDK code after API change in Docker tooling

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-22463: ------------------------------------- Summary: Update CDK code after API change in Docker tooling Key: JBIDE-22463 URL: https://issues.jboss.org/browse/JBIDE-22463 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift, server Affects Versions: 4.4.0.Alpha2 Reporter: Xavier Coulon The APi to create a connection changed in the latest version of Docker tooling. This impacts the {{CDKDockerUtility}} class in the {{org.jboss.tools.openshift.cdk.server}} bundle. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 May 2016