December 2015 - jbosstools-issues

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-21145 at 12/9/15 3:21 PM: ---------------------------------------------------------------- In current state even if we just stop doing checks if upload required (which I think is fine, lets do this) and start aggregating latest the greatest *aggregation build result* is not going to be reliable. Or better say it is not going to be reliable all the time without attention from involved parties. Composite install job would not be reliable by transition, because with all the JBT components built without synchronization aggregation build picks up random combination of JBossTools components from nightly p2 repositories. I would stop discussing build improvements in this issue and fix actual problem stated in summary by disabling check "if upload required" and started aggregating when it is triggered by downstream trigger. p2diff IMO can be used until we have .qualifier generated every build based on time stamp. Then we can see what we can do to make actual aggreagted build results reliable. was (Author: dgolovin): I current state even if we just stop doing checks if upload required (which I think is fine, lets do this) and start aggregating latest the greatest *aggregation build result* is not going to be reliable. Or better say it is not going to be reliable all the time without attention from involved parties. Composite install job would not be reliable by transition, because with all the JBT components built without synchronization aggregation build picks up random combination of JBossTools components from nightly p2 repositories. I would stop discussing build improvements in this issue and fix actual problem stated in summary by disabling check "if upload required" and started aggregating when it is triggered by downstream trigger. p2diff IMO can be used until we have .qualifier generated every build based on time stamp. Then we can see what we can do to make actual aggreagted build results reliable. > Composite 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 > > Attachments: jbide21145-conflict-between-tp-and-central.png > > > 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] (JBTIS-537) Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-537?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-537: ----------------------------- Attachment: fuse6.png fuse5.png fuse3.png fuse2.png fuse1.png > Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-537 > URL: https://issues.jboss.org/browse/JBTIS-537 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Assignee: Paul Leacu > Priority: Critical > Attachments: fuse1.png, fuse2.png, fuse3.png, fuse5.png, fuse6.png > > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21226) [RHMAP] CordovaApp/ .. feedhenry.js has errors after import into IDE

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21226?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21226: ----------------------------------- Fix Version/s: 4.3.x 4.4.0.Alpha1 (was: 4.3.1.Beta1) > [RHMAP] CordovaApp/ .. feedhenry.js has errors after import into IDE > -------------------------------------------------------------------- > > Key: JBIDE-21226 > URL: https://issues.jboss.org/browse/JBIDE-21226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.1.Beta1 > Environment: 4.3.x nightly from 2015-12-04 > Reporter: Pavol Srna > Assignee: Victor Rubezhny > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: Screen Shot 2015-12-09 at 16.21.21.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21226) [RHMAP] CordovaApp/ .. feedhenry.js has errors after import into IDE

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21226?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21226: ----------------------------------- Component/s: upstream (was: aerogear-hybrid) > [RHMAP] CordovaApp/ .. feedhenry.js has errors after import into IDE > -------------------------------------------------------------------- > > Key: JBIDE-21226 > URL: https://issues.jboss.org/browse/JBIDE-21226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, upstream > Affects Versions: 4.3.1.Beta1 > Environment: 4.3.x nightly from 2015-12-04 > Reporter: Pavol Srna > Assignee: Victor Rubezhny > Fix For: 4.3.1.Beta1 > > Attachments: Screen Shot 2015-12-09 at 16.21.21.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3276) JBDS-IS Installer support

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3276: --------------------------------- Fix Version/s: 9.1.0.Beta2 (was: 9.1.0.Beta1) > JBDS-IS Installer support > ------------------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Fix For: 9.1.0.Beta2 > > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png, EA.png, jbds-is-about.png, JBDSIS_installer_9.png, JBDSIS_installer_space.png, mirroringlog.txt, sai1.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21226) [RHMAP] CordovaApp/ .. feedhenry.js has errors after import into IDE

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21226?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21226: -------------------------------------- Assignee: Victor Rubezhny > [RHMAP] CordovaApp/ .. feedhenry.js has errors after import into IDE > -------------------------------------------------------------------- > > Key: JBIDE-21226 > URL: https://issues.jboss.org/browse/JBIDE-21226 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, javascript > Affects Versions: 4.3.1.Beta1 > Environment: 4.3.x nightly from 2015-12-04 > Reporter: Pavol Srna > Assignee: Victor Rubezhny > Fix For: 4.3.1.Beta1 > > Attachments: Screen Shot 2015-12-09 at 16.21.21.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-21145: --------------------------------------- I current state even if we just stop doing checks if upload required (which I think is fine, lets do this) and start aggregating latest the greatest *aggregation build result* is not going to be reliable. Or better say it is not going to be reliable all the time without attention from involved parties. Composite install job would not be reliable by transition, because with all the JBT components built without synchronization aggregation build picks up random combination of JBossTools components from nightly p2 repositories. I would stop discussing build improvements in this issue and fix actual problem stated in summary by disabling check "if upload required" and started aggregating when it is triggered by downstream trigger. p2diff IMO can be used until we have .qualifier generated every build based on time stamp. Then we can see what we can do to make actual aggreagted build results reliable. > Composite 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 > > Attachments: jbide21145-conflict-between-tp-and-central.png > > > 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] (JBTIS-537) Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-537?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-537: ----------------------------- Project: JBoss Tools Integration Stack (was: Tools (JBoss Tools)) Key: JBTIS-537 (was: JBIDE-20936) Component/s: distribution Fuse IDE (was: central) Affects Version/s: 4.3.0.Final (was: 4.3.0.Final) Fix Version/s: (was: 4.4.0.Alpha1) (was: 4.3.1.Beta1) > Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-537 > URL: https://issues.jboss.org/browse/JBTIS-537 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Critical > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-537) Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-537?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBTIS-537: -------------------------------- Assignee: Paul Leacu (was: Nick Boldt) > Unable to import Fuse Integration Project from Central when Fuse tooling isn't already installed (can't auto-install Fuse connector) > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-537 > URL: https://issues.jboss.org/browse/JBTIS-537 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0 > Reporter: Radim Hopp > Assignee: Paul Leacu > Priority: Critical > > I'm unable to import Fuse Integration Project from Central, when Fuse tooling isn't installed (but is available in EA). > This might be split to two issues: > 1) EA is disabled -> Fuse Integration Project should not appear in Central or at least it should tell user to enable EA to be able to install needed fuse tooling. > 2) EA is enabled -> After clicking on "Fuse Integration Project" user is prompted to install necessary connectors (The required features to use this wizard need to be installed."). After clicking on "Yes", error occurs: > {noformat} > Problems occurred while performing installation: There are no connectors to install > There are no connectors to install > {noformat} > {noformat} > java.lang.IllegalArgumentException: There are no connectors to install > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:109) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > Note: When Fuse tooling is already installed, everything is ok . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20747: ------------------------------------ Slip to 4.3.1.Beta2. Mickael, can you take a look at this? > install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20747 > URL: https://issues.jboss.org/browse/JBIDE-20747 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.1.Beta2 > > Attachments: features.txt, plugins.txt > > > This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > {code} > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120] > Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0" > -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true" > org.jboss.tools.browsersim.ui [1122] > Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)" > -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730" > org.eclipse.jetty.websocket.server [555] > Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)" > Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)" > -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13" > org.eclipse.jetty.websocket.servlet [556] > Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple" > -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory" > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Similar problems for other IUs: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163] > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166] > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221] > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222] > {code} > But the job was successful! > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- 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