November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23184) Add Capability to Watch Projects

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23184: --------------------------------------- Well, I checked docs. It looks like it is supported since kubernetes 1.3. And there is an API for retrieving project list https://docs.openshift.org/latest/rest_api/openshift_v1.html#v1-projectlist Do you think it is possible to do it now? For version < 1.3 it can fail safe, there is not much to do in that case. And we should have it documented. > Add Capability to Watch Projects > -------------------------------- > > Key: JBIDE-23184 > URL: https://issues.jboss.org/browse/JBIDE-23184 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM3 > > > Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch > $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion= > {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}} > {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}} > openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with TP and PDE Source Lookup)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23481 at 11/20/16 5:20 PM: -------------------------------------------------------------- {quote}We could only add the sources to the JBoss Tools TP site, not to the JBDS one. So the installer remains slimmer but devs can easily access sources (I imagine they mostly use the JBT TP site).{quote} Excellent point. The JBT one also includes test bundles (eg.. mock, reddeer) which we exclude from the devstudio one. So... +1 to add sources to the JBT TP site and zip (but not to the devstudio ones). So say we all? PR to apply in both 4.60.x and 4.61.x branches: https://github.com/jbosstools/jbosstools-target-platforms/pull/246 [~pleacu] will this cause any problem when you're building your TPs based on the JBT one? was (Author: nickboldt): {quote}We could only add the sources to the JBoss Tools TP site, not to the JBDS one. So the installer remains slimmer but devs can easily access sources (I imagine they mostly use the JBT TP site).{quote} Excellent point. The JBT one also includes test bundles (eg.. mock, reddeer) which we exclude from the devstudio one. So... +1 to add sources to the JBT TP site and zip (but not to the devstudio ones). So say we all? > build target platform sources site (for use with TP and PDE Source Lookup) > -------------------------------------------------------------------------- > > Key: JBIDE-23481 > URL: https://issues.jboss.org/browse/JBIDE-23481 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to: > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > * build a targetplatform with all the sources > * split that repo into two pieces: all the .source files, and everything else > * regen the metadata (featureandbundlepublisher) in each new repo so that all the features/plugins are uncategorized > OR... > * build a targetplatform without the sources > * transform the .target file so that each IU ends with .source > * build the target platform repo from the new .target file > * verify that sources repo includes the sources of nested features, and those features' plugins' sources too > ---- > Then once we have the targetplatform.source repo, publish that and verify it works with the PDE Source Lookup plugin: > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve soources > ---- > Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central + central tp) as a 5th child site. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with TP and PDE Source Lookup)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23481 at 11/20/16 2:16 PM: -------------------------------------------------------------- {quote}We could only add the sources to the JBoss Tools TP site, not to the JBDS one. So the installer remains slimmer but devs can easily access sources (I imagine they mostly use the JBT TP site).{quote} Excellent point. The JBT one also includes test bundles (eg.. mock, reddeer) which we exclude from the devstudio one. So... +1 to add sources to the JBT TP site and zip (but not to the devstudio ones). So say we all? was (Author: nickboldt): {quote}We could only add the sources to the JBoss Tools TP site, not to the JBDS one. So the installer remains slimmer but devs can easily access sources (I imagine they mostly use the JBT TP site).{quote} Excellent point. The JBT one also includes test bundles (eg.. mock, reddeer) which we exclude from the devstudio one. So... +1 to add sources to the JBT TP site and zip. So say we all? > build target platform sources site (for use with TP and PDE Source Lookup) > -------------------------------------------------------------------------- > > Key: JBIDE-23481 > URL: https://issues.jboss.org/browse/JBIDE-23481 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to: > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > * build a targetplatform with all the sources > * split that repo into two pieces: all the .source files, and everything else > * regen the metadata (featureandbundlepublisher) in each new repo so that all the features/plugins are uncategorized > OR... > * build a targetplatform without the sources > * transform the .target file so that each IU ends with .source > * build the target platform repo from the new .target file > * verify that sources repo includes the sources of nested features, and those features' plugins' sources too > ---- > Then once we have the targetplatform.source repo, publish that and verify it works with the PDE Source Lookup plugin: > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve soources > ---- > Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central + central tp) as a 5th child site. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with TP and PDE Source Lookup)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23481: ------------------------------------ {quote}We could only add the sources to the JBoss Tools TP site, not to the JBDS one. So the installer remains slimmer but devs can easily access sources (I imagine they mostly use the JBT TP site).{quote} Excellent point. The JBT one also includes test bundles (eg.. mock, reddeer) which we exclude from the devstudio one. So... +1 to add sources to the JBT TP site and zip. So say we all? > build target platform sources site (for use with TP and PDE Source Lookup) > -------------------------------------------------------------------------- > > Key: JBIDE-23481 > URL: https://issues.jboss.org/browse/JBIDE-23481 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to: > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > * build a targetplatform with all the sources > * split that repo into two pieces: all the .source files, and everything else > * regen the metadata (featureandbundlepublisher) in each new repo so that all the features/plugins are uncategorized > OR... > * build a targetplatform without the sources > * transform the .target file so that each IU ends with .source > * build the target platform repo from the new .target file > * verify that sources repo includes the sources of nested features, and those features' plugins' sources too > ---- > Then once we have the targetplatform.source repo, publish that and verify it works with the PDE Source Lookup plugin: > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve soources > ---- > Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central + central tp) as a 5th child site. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with TP and PDE Source Lookup)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23481 at 11/20/16 2:14 PM: -------------------------------------------------------------- We could only add the sources to the JBoss Tools TP site, not to the JBDS one. So the installer remains slimmer but devs can easily access sources (I imagine they mostly use the JBT TP site). was (Author: mickael_istria): We could only add the sources to the JBoss Tools TP site, not to the JBDS one. So the installer remains slimer but devs can easily access sources (I imagine they mostly use the JBT TP site_. > build target platform sources site (for use with TP and PDE Source Lookup) > -------------------------------------------------------------------------- > > Key: JBIDE-23481 > URL: https://issues.jboss.org/browse/JBIDE-23481 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to: > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > * build a targetplatform with all the sources > * split that repo into two pieces: all the .source files, and everything else > * regen the metadata (featureandbundlepublisher) in each new repo so that all the features/plugins are uncategorized > OR... > * build a targetplatform without the sources > * transform the .target file so that each IU ends with .source > * build the target platform repo from the new .target file > * verify that sources repo includes the sources of nested features, and those features' plugins' sources too > ---- > Then once we have the targetplatform.source repo, publish that and verify it works with the PDE Source Lookup plugin: > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve soources > ---- > Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central + central tp) as a 5th child site. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4122) Persist environment variables on Mac OS X

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4122?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4122: -------------------------------- Sprint: (was: devex #123 November 2016) > Persist environment variables on Mac OS X > ----------------------------------------- > > Key: JBDS-4122 > URL: https://issues.jboss.org/browse/JBDS-4122 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > > Installer add location for oc cli to PATH env variable. Installer should have util to make persistent changes to any required env variable on Mac OS X. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-870) Summarize all features which will be installed in the installer wizard

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-870?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-870: ---------------------------------- [~apodhrad] - could you test this out - especially on Windows? Thanks! http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > Summarize all features which will be installed in the installer wizard > ---------------------------------------------------------------------- > > Key: JBTIS-870 > URL: https://issues.jboss.org/browse/JBTIS-870 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 4.0.0 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.1.0.GA > > Attachments: inst1.png, inst1.png, jbdsis_installer_summary.png > > > I suggest to summarize all features which will be installed in Summary page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4193) Build Bundle Installer for macOS

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4193: ----------------------------------- Summary: Build Bundle Installer for macOS Key: JBDS-4193 URL: https://issues.jboss.org/browse/JBDS-4193 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.GA Environment: macOS Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.2.0.GA Current configuration supports only build for online installer. Build should be migrated from building using cli build command and configuration defined in package.json to electron-builder API. That would let to build online and then bundled installer just by calling builder with dynamic configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4193) Build Bundle Installer for macOS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4193?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4193: -------------------------------- Sprint: devex #123 November 2016 > Build Bundle Installer for macOS > -------------------------------- > > Key: JBDS-4193 > URL: https://issues.jboss.org/browse/JBDS-4193 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.GA > Environment: macOS > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.GA > > > Current configuration supports only build for online installer. Build should be migrated from building using cli build command and configuration defined in package.json to electron-builder API. That would let to build online and then bundled installer just by calling builder with dynamic configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23499) Integration tests: ConnectionWizardLinkTest isnt working and has wrong class name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23499?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23499: ------------------------------------- Fix Version/s: 4.4.2.Final > Integration tests: ConnectionWizardLinkTest isnt working and has wrong class name > --------------------------------------------------------------------------------- > > Key: JBIDE-23499 > URL: https://issues.jboss.org/browse/JBIDE-23499 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.2.Final > > > ConnectionWizardLinkTest isnt working. It tries to login into openshift 3 online (preview) with an account that was disabled. The class furthermore has a bad name: it does not reflect what it really tests. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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