November 2016 - jbosstools-issues

[JBoss JIRA] (ERT-432) provide a right-click menu to "enable connection" in Docker Explorer view [EBZ#504073]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-432?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-432: ------------------------------ Sprint: devex #122 October 2016 > provide a right-click menu to "enable connection" in Docker Explorer view [EBZ#504073] > -------------------------------------------------------------------------------------- > > Key: ERT-432 > URL: https://issues.jboss.org/browse/ERT-432 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Priority: Trivial > Labels: Docker, bzira > > I was wondering why i didn't have the tree anymore during at least 15 minutes :'( I even restarted my instance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20683) Remove unnecessary lines in ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20683?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20683: ------------------------------------ If we fix JBIDE-23475 then we probably won't have this problem anymore. > Remove unnecessary lines in ide-config.properties > ------------------------------------------------- > > Key: JBIDE-20683 > URL: https://issues.jboss.org/browse/JBIDE-20683 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, website > Affects Versions: 4.3.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Trivial > Fix For: LATER > > > Currently, the properties file at > http://download.jboss.org/jbosstools/configuration/ide-config.properties > contains lots of lines which are commented out. I suggest to remove all unnecessary lines to improve the readability. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2044) .eclipseproduct file no longer refers to JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2044?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2044. ---------------------------- Fix Version/s: 10.2.0.AM3 (was: LATER) Resolution: Won't Fix > .eclipseproduct file no longer refers to JBDS > --------------------------------------------- > > Key: JBDS-2044 > URL: https://issues.jboss.org/browse/JBDS-2044 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 5.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Labels: discuss > Fix For: 10.2.0.AM3 > > > Before, with the linux x64 installer (jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201202271832M-H79-Beta1.jar) the .eclipseproduct file read: > {code} > name=JBoss Developer Studio > id=com.jboss.jbds.all > version=5.0.0.v201202271832M-H79-Beta1 > {code} > Now, with the universal installer (jbdevstudio-product-universal-5.0.0.v201202271832M-H79-Beta1.jar), it reads: > {code} > name=Eclipse Platform > id=org.eclipse.platform > version=3.7.0 > {code} > Latest code in equinox.runtime master branch is located http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/or... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22966: ------------------------------- Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 July 2016, devex #119 August 2016, devex #123 November 2016) > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.2.Final > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RHECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23384) Include integration-tests in staging and stable update sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23384?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23384: ------------------------------- Sprint: devex #123 November 2016 (was: devex #122 October 2016) > Include integration-tests in staging and stable update sites > ------------------------------------------------------------ > > Key: JBIDE-23384 > URL: https://issues.jboss.org/browse/JBIDE-23384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > This will allow us the use case of running integration tests against the latest release of devstudio. This use case is required by EAP QE running our tests against their EAP development builds. > Currently we have this repo: > http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t... > We're referencing it from our root pom: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > And set up a repository definition for it. > This allows us to run an individual test bundle. > This is mostly useful to satisfy test dependencies - tests depend on RedDeer as a whole which is in the target platform. But most tests also have a RedDeer extension in the plugins directory: > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > With that, let's move on to why it would be useful to have a stable repo for this, e.g. http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests/ > Imagine you want to run integration tests against the latest stable build. If you just checkout the integration tests and run a test plugin (using mvn verify), it will use everything from the latest nightly repos. > So to use latest stable release (jbt 4.4.1.Final / devstudio 10.1.0.GA), you need a couple of things: > 1. Checkout the corresponding branch of the integration tests - jbosstools-4.4.1.x in this case > 2. Make sure the proper devstudio is used to test against: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > -Ddevstudio.repository=https://devstudio.redhat.com/10.0/stable/updates > This also includes the TP, so RedDeer should be the correct version > 3. Make sure the proper integration-tests repo is used for dependencies > Now this is what we currently don't have. Our root pom will set up the snapshots repo: > https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... > So that's why I would like to have a stable repo of this which I could use. > There is a workaround - run "mvn install" on the whole integration-tests repo before you run your test. This will install the correct version in your local repo and that may be then used by your test. But maven will probably still prefer the newer versions from the snapshots repo that is set up in the pom. > To give you an example what can break when you use the newest org.jboss.ide.eclipse.as.reddeer plugin, but run the EAP tests against devstudio 10.1.0.GA: > The EAP 7 server adapter had 7.0 in the type name in 10.1.0.GA, but in current master it's 7.x (to accommodate for the upcoming EAP 7.1). So if you want to test EAP 7.0.1 CP candidate build against devstudio 10.1.0.GA it will fail on this. > Sorry for the lengthy explanation, but I hope it's now clear why I'm requesting this. > Also, I'd be happy to hear if you have some suggestions how to do it differently. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4077: ----------------------------- Sprint: devex #123 November 2016 (was: devex #122 October 2016) > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Rastislav Wagner > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22966: ------------------------------- Sprint: devex #118 July 2016, devex #119 August 2016, devex #123 November 2016 (was: devex #118 July 2016, devex #119 August 2016) > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.2.Final > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RHECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Sprint: devex #115 May 2016, devex #116 June 2016 (was: devex #115 May 2016, devex #116 June 2016, devex #122 October 2016) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.2.AM3 > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4118) JBDS update site builds produces update site zip TWICE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4118?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4118: ----------------------------- Sprint: (was: devex #122 October 2016) > JBDS update site builds produces update site zip TWICE > ------------------------------------------------------ > > Key: JBDS-4118 > URL: https://issues.jboss.org/browse/JBDS-4118 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.x > > > JBDS build creates the update site zip TWICE: > {code} > [INFO] --- tycho-p2-repository-plugin:0.23.1:archive-repository (default-archive-repository) @ com.jboss.devstudio.core.site --- > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.23.1:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/repository/web/site.css found; using default. > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23021) script checking if all the latest SHAs have been built

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23021?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23021: ------------------------------- Sprint: devex #119 August 2016, devex #123 November 2016 (was: devex #119 August 2016, devex #122 October 2016) > script checking if all the latest SHAs have been built > ------------------------------------------------------ > > Key: JBIDE-23021 > URL: https://issues.jboss.org/browse/JBIDE-23021 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > Need a tool that can compare the latest SHA for a github project on a given branch against a published buildinfo.json. > Should be able to check either jbosstools-base vs. CI build, or jbosstools-base vs. jbt aggregate build's buildinfo.json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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