December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21179) Upgrade Forge Runtime to 3.0.0.Alpha2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21179?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-21179. ------------------------------------- Resolution: Done Labels: new_and_noteworthy (was: ) > Upgrade Forge Runtime to 3.0.0.Alpha2 > ------------------------------------- > > Key: JBIDE-21179 > URL: https://issues.jboss.org/browse/JBIDE-21179 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21179) Upgrade Forge Runtime to 3.0.0.Alpha2

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-21179: --------------------------------------- Summary: Upgrade Forge Runtime to 3.0.0.Alpha2 Key: JBIDE-21179 URL: https://issues.jboss.org/browse/JBIDE-21179 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.3.0.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.4.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21145) Component-install job does not reliably install all JBT IUs and so does not see changes between CI builds

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21145: --------------------------------------------- real agile test driven does the tests *before* putting code into master. I don't think anyone suggested to move to install-grinder; just that doing the aggregation and *then* run the p2 director install on the result once p2diff have declared it is relevant to check would be just as fast if not faster. > Component-install job does not reliably install all JBT IUs and so does not see changes between CI builds > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21145 > URL: https://issues.jboss.org/browse/JBIDE-21145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > We have often seen old artifacts on nightly sites (mars and neon too). > It seems that the composite-install job [0], [1] is not reliable. So, the downstream JBT aggregate builds [2], [3] are not triggered automatically to pick up all new changes in the upstream JBT component site builds. > [0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-... > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 6:15 AM NOT PUBLISHED: UNCHANGED") > [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 3:43 AM NOT PUBLISHED: UNCHANGED") > Please investigate. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16970) create mechanism to verify that nightly build is different from previous milestone

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16970: --------------------------------------------- I was not aware that local builds of repositories contained a buildinfo.json - I can see they do; then it is of less an concern. > create mechanism to verify that nightly build is different from previous milestone > ---------------------------------------------------------------------------------- > > Key: JBIDE-16970 > URL: https://issues.jboss.org/browse/JBIDE-16970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.x > > > After the discovery site build job is done, we should: > * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case) > * for respins, use *job param* label = "respin-a" or "respin-b" in jira query > * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 > * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet... > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder) > * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/ > * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... > * run p2diff on the two repos - see https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21171) Need to remove bower / npm from jboss.tools.jsdt

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21171?page=com.atlassian.jira.plugi... ] Victor Rubezhny commented on JBIDE-21171: ----------------------------------------- [~ibuziuk] it's not available yet. Could you wait for Tuesday or Wednesday, there is the smoke test request is sent for build I-3.8.0-20151203010029, so next week this build is supposed to be declared and, if successful, will be available through downloads. > Need to remove bower / npm from jboss.tools.jsdt > ------------------------------------------------ > > Key: JBIDE-21171 > URL: https://issues.jboss.org/browse/JBIDE-21171 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, nodejs > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Assuming that bower / npm were moved to eclipse jsdt - https://git.eclipse.org/r/#/c/61336/ > Need to perform a cleanup in jboss.tools.jst.jsdt repo and remove related plugins / tests / features > Bower is in eclipse upstream and we probably will need reflect it in new & noteworthy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3567) Offline install instructions are very unclear

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBDS-3567: ------------------------------------ Summary: Offline install instructions are very unclear Key: JBDS-3567 URL: https://issues.jboss.org/browse/JBDS-3567 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: documentation Affects Versions: 9.0.0.GA Reporter: Mustafa Musaji Assignee: Misha Ali I came across this - https://access.redhat.com/articles/1367643. I'm puzzled by the instructions on here and what this page is meant to do. Firstly there's no mention at all of downloading the ZIP from the CSP. https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?produ... I don't know what the groovy stuff is meant to do, installing and setting up a local maven repo is not in the scope of a JBDS set up but I believe either way it's wrong for this page. Part 2 talks about "You can install the JBoss and third-party plug-ins listed in JBoss Central in offline mode using the JBoss Central Site .zip file" but then doesn't mention where to download these zips (CSP). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3565) Include Target Platform Zip with JBDS for offline install on CSP

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-3565?page=com.atlassian.jira.plugin.... ] Mustafa Musaji commented on JBDS-3565: -------------------------------------- Sounds like a plan, anything that makes installation simpler with less things to download would be a plus. This will need to be tested [~ldimaggio] and documented [~mhusnain] will need changes to. Mus > Include Target Platform Zip with JBDS for offline install on CSP > ---------------------------------------------------------------- > > Key: JBDS-3565 > URL: https://issues.jboss.org/browse/JBDS-3565 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.1.0.Beta1 > Environment: Customer Support Portal > Reporter: Mustafa Musaji > Assignee: Nick Boldt > > Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip. > This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3565) Include Target Platform Zip with JBDS for offline install on CSP

by Mustafa Musaji (JIRA)

[ https://issues.jboss.org/browse/JBDS-3565?page=com.atlassian.jira.plugin.... ] Mustafa Musaji edited comment on JBDS-3565 at 12/3/15 10:29 AM: ---------------------------------------------------------------- Sounds like a plan, anything that makes installation simpler with less things to download would be a plus. This will need to be tested [~ldimaggio] and documentation around offline install [~mhusnain] will need changes to. Mus was (Author: mmusaji): Sounds like a plan, anything that makes installation simpler with less things to download would be a plus. This will need to be tested [~ldimaggio] and documented [~mhusnain] will need changes to. Mus > Include Target Platform Zip with JBDS for offline install on CSP > ---------------------------------------------------------------- > > Key: JBDS-3565 > URL: https://issues.jboss.org/browse/JBDS-3565 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.1.0.Beta1 > Environment: Customer Support Portal > Reporter: Mustafa Musaji > Assignee: Nick Boldt > > Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip. > This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16970) create mechanism to verify that nightly build is different from previous milestone

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16970?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16970: ------------------------------------ I've uploaded p2diff binaries here: /home/hudson/static_build_env/jbds/p2diff/x86_64/p2diff /home/hudson/static_build_env/jbds/p2diff/x86/p2diff So... I can start playing with running this as part of a build. > create mechanism to verify that nightly build is different from previous milestone > ---------------------------------------------------------------------------------- > > Key: JBIDE-16970 > URL: https://issues.jboss.org/browse/JBIDE-16970 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.x > > > After the discovery site build job is done, we should: > * get a list of JIRAs for a given target fixversion, eg., 4.2.0.Beta1 or 8.0.0.Beta1 *job param* milestone = Beta1, Beta2, CR1, Final/GA (special case) > * for respins, use *job param* label = "respin-a" or "respin-b" in jira query > * filter query to only show the components and map those to actual project names - see https://github.com/jbdevstudio/jbdevstudio-ci/blob/master/bin/createTaskJ... for mappings > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 > * install last milestone from *job param* oldURL = http://download.jboss.org/jbosstools/updates/staging/JBossTools-4.2.0.Bet... > * install Eclipse from *job param* eclipseBundleVersion = luna.M6 (in a different folder) > * install new nightly from *job param* oldURL = http://download.jboss.org/jbosstools/updates/nightlycore/4.2.luna/ > * compare installed footprints - see https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/instal... > * run p2diff on the two repos - see https://github.com/irbull/p2diff -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3565) Include Target Platform Zip with JBDS for offline install on CSP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3565?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3565: ---------------------------------- As an alternative we could look at including the TP inside the JBDS update site zip, so that users don't need a second CSP artifact. This is more closely aligned with how the JBDS IS offline zip is packaged. [~mmusaji] would you be happy with that solution instead? (I could also explore doing the same for the Central and EA zips, so they too are only 1 zip each instead of a zip + a TP zip.) > Include Target Platform Zip with JBDS for offline install on CSP > ---------------------------------------------------------------- > > Key: JBDS-3565 > URL: https://issues.jboss.org/browse/JBDS-3565 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.1.0.Beta1 > Environment: Customer Support Portal > Reporter: Mustafa Musaji > Assignee: Nick Boldt > > Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip. > This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal. -- 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