January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21602) Sonar build for openshift is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21602?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21602: ---------------------------------------- Assignee: Mickael Istria (was: Andre Dietisheim) > Sonar build for openshift is failing > ------------------------------------ > > Key: JBIDE-21602 > URL: https://issues.jboss.org/browse/JBIDE-21602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Mickael Istria > Attachments: sonar-build-output.txt > > > Sonar for openshift is currently failing in our jenkins at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > I see it complaining in the build about an incompatible bytecode version: > {code} > Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/tycho/core/p2/P2ArtifactRepositoryLayout : Unsupported major.minor version 51.0 > {code} > The full build output is attached [^sonar-build-output.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21602) Sonar build for openshift is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21602?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21602: ------------------------------------- Attachment: sonar-build-output.txt > Sonar build for openshift is failing > ------------------------------------ > > Key: JBIDE-21602 > URL: https://issues.jboss.org/browse/JBIDE-21602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Attachments: sonar-build-output.txt > > > Sonar for openshift is currently failing in our jenkins at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > I see it complaining in the build about an incompatible bytecode version: > {code} > Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/tycho/core/p2/P2ArtifactRepositoryLayout : Unsupported major.minor version 51.0 > {code} > The full build output is attached [^sonar-build-output.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21602) Sonar build for openshift is failing

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21602: ---------------------------------------- Summary: Sonar build for openshift is failing Key: JBIDE-21602 URL: https://issues.jboss.org/browse/JBIDE-21602 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.1.Beta2 Reporter: Andre Dietisheim Sonar for openshift is currently failing in our jenkins at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... I see it complaining in the build about an incompatible bytecode version: {code} Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/tycho/core/p2/P2ArtifactRepositoryLayout : Unsupported major.minor version 51.0 {code} The full build output is attached [^sonar-build-output.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21373) Eclipse files are missing from .gitignore

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21373?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-21373. ------------------------------------ > Eclipse files are missing from .gitignore > ----------------------------------------- > > Key: JBIDE-21373 > URL: https://issues.jboss.org/browse/JBIDE-21373 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Reporter: Daniel Dekany > Priority: Trivial > > The Eclipse generated files aren't git ignored, making staging, resets, etc. more difficult. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21363: ------------------------------------ ERT JIRAs are now live: known issues: * not working: BZ closed duplicate -> JIRA closed dupe; workaround: close JIRA manually for now * fixversions don't include .y versions, eg., should have 4.5.2 instead of 4.5: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... * need component leads for Platform and WTP Incubator: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... > create bugzilla importer for JIRA > --------------------------------- > > Key: JBIDE-21363 > URL: https://issues.jboss.org/browse/JBIDE-21363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Looking to create some kind of jiralint-like scraper tool to facilitate JIRA-like scrum/dashboard tracking of upstream projects, not located in JBoss JIRA. > This scraper would: > * [REQ1] find all bugzillas associated with a particular query, such as https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT (18 issues) > * [REQ2] generate a JIRA for each one found (no dupes should be created) > * [REQ3] scrape several fields: product, component, version, target milestone, comment #0, summary, bug # > * [REQ4] need a mapping table for Eclipse-prod:proj:component:fixversion-or-target-milestone to Neon milestone so we can set default values for affectsversion/fixversion/targetrelease in created JIRAs. > * [REQ5] need a mapping table for Eclipse-prod:proj:component to ERT:component, eg., WTP:JSDT -> javascript > * [REQ6] created test issues here: https://issues.stage.jboss.org/browse/ERT > * [REQ7] run as a Jenkins job every 3 hours > Generated JIRA example: > {code} > title: (scraped from summary) Support for smart Import Mechanism [Eclipse BZ 464535] > issue link: (scraped from BZ ID#) https://bugs.eclipse.org/464535 > description: (scraped from BZ comment #0) > affectsversion: (scraped from BZ version 1.6.0) > fixversion: (scraped from BZ target milestone ---) > component: (scraped from product:component = m2e:ui) > labels: RHT, ERT > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21363 at 1/28/16 2:15 AM: ------------------------------------------------------------- ERT JIRAs are now live: https://issues.stage.jboss.org/browse/ERT Known issues: * not working: BZ closed duplicate -> JIRA closed dupe; workaround: close JIRA manually for now * fixversions don't include .y versions, eg., should have 4.5.2 instead of 4.5: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... * need component leads for Platform and WTP Incubator: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... was (Author: nickboldt): ERT JIRAs are now live: known issues: * not working: BZ closed duplicate -> JIRA closed dupe; workaround: close JIRA manually for now * fixversions don't include .y versions, eg., should have 4.5.2 instead of 4.5: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... * need component leads for Platform and WTP Incubator: https://issues.jboss.org/projects/ERT?selectedItem=com.atlassian.jira.jir... > create bugzilla importer for JIRA > --------------------------------- > > Key: JBIDE-21363 > URL: https://issues.jboss.org/browse/JBIDE-21363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Looking to create some kind of jiralint-like scraper tool to facilitate JIRA-like scrum/dashboard tracking of upstream projects, not located in JBoss JIRA. > This scraper would: > * [REQ1] find all bugzillas associated with a particular query, such as https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT (18 issues) > * [REQ2] generate a JIRA for each one found (no dupes should be created) > * [REQ3] scrape several fields: product, component, version, target milestone, comment #0, summary, bug # > * [REQ4] need a mapping table for Eclipse-prod:proj:component:fixversion-or-target-milestone to Neon milestone so we can set default values for affectsversion/fixversion/targetrelease in created JIRAs. > * [REQ5] need a mapping table for Eclipse-prod:proj:component to ERT:component, eg., WTP:JSDT -> javascript > * [REQ6] created test issues here: https://issues.stage.jboss.org/browse/ERT > * [REQ7] run as a Jenkins job every 3 hours > Generated JIRA example: > {code} > title: (scraped from summary) Support for smart Import Mechanism [Eclipse BZ 464535] > issue link: (scraped from BZ ID#) https://bugs.eclipse.org/464535 > description: (scraped from BZ comment #0) > affectsversion: (scraped from BZ version 1.6.0) > fixversion: (scraped from BZ target milestone ---) > component: (scraped from product:component = m2e:ui) > labels: RHT, ERT > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21601) p2director install should support excluding IUs like platform fragments and executables

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21601: ---------------------------------- Summary: p2director install should support excluding IUs like platform fragments and executables Key: JBIDE-21601 URL: https://issues.jboss.org/browse/JBIDE-21601 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Nick Boldt p2director install test should exclude things like executable.feature.group and org.eclipse.equinox.launcher.* {code} 01:27:34 [p2.dir] Cannot complete the install because of a conflicting dependency. 01:27:34 [p2.dir] Software being installed: Eclipse Platform Launcher Executables 3.6.200.v20151113-1733 (org.eclipse.equinox.executable.feature.group 3.6.200.v20151113-1733) 01:27:34 [p2.dir] Software currently installed: Eclipse IDE for Java EE Developers 4.6.0.20151218-1543 (epp.package.jee 4.6.0.20151218-1543) 01:27:34 [p2.dir] Only one of the following can be installed at once: 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20151013-1129 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20151013-1129) 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20160105-0945 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20160105-0945) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21601) p2director install should support excluding IUs like platform fragments and executables

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21601?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21601: ---------------------------------- Assignee: Nick Boldt > p2director install should support excluding IUs like platform fragments and executables > --------------------------------------------------------------------------------------- > > Key: JBIDE-21601 > URL: https://issues.jboss.org/browse/JBIDE-21601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Nick Boldt > Assignee: Nick Boldt > > p2director install test should exclude things like executable.feature.group and org.eclipse.equinox.launcher.* > {code} > 01:27:34 [p2.dir] Cannot complete the install because of a conflicting dependency. > 01:27:34 [p2.dir] Software being installed: Eclipse Platform Launcher Executables 3.6.200.v20151113-1733 (org.eclipse.equinox.executable.feature.group 3.6.200.v20151113-1733) > 01:27:34 [p2.dir] Software currently installed: Eclipse IDE for Java EE Developers 4.6.0.20151218-1543 (epp.package.jee 4.6.0.20151218-1543) > 01:27:34 [p2.dir] Only one of the following can be installed at once: > 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20151013-1129 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20151013-1129) > 01:27:34 [p2.dir] Equinox Launcher Linux X86 Fragment 1.1.300.v20160105-0945 (org.eclipse.equinox.launcher.gtk.linux.x86 1.1.300.v20160105-0945) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-706) JBDS 9.1 Beta2: Edit New and Noteworthy

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-706?page=com.atlassian.jira.plug... ] Alexey Kazakov commented on TOOLSDOC-706: ----------------------------------------- [~mhusnain] yeah.. We still waiting for Open Shift ([~fbricon]) and Forge ([~gastaldi]) - https://issues.jboss.org/browse/JBIDE-21533 We are expecting them to be ready this week. > JBDS 9.1 Beta2: Edit New and Noteworthy > --------------------------------------- > > Key: TOOLSDOC-706 > URL: https://issues.jboss.org/browse/TOOLSDOC-706 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > N&N info will be available two days before release. Edit and update the content and then use it in the Release Notes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21536) Forge New and Noteworthy for 4.3.1.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21536?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21536: ---------------------------------------- [~gastaldi] just a reminder. We need all N&N to be ready this week :) > Forge New and Noteworthy for 4.3.1.Beta2 > ---------------------------------------- > > Key: JBIDE-21536 > URL: https://issues.jboss.org/browse/JBIDE-21536 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Alexey Kazakov > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.3.1.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 January 2016