October 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26461) jbosstools-javaee master build is broken since updated tycho to 1.3.0-SNAPSHOT

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26461?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-26461: ------------------------------------- Assignee: Ondrej Dockal > jbosstools-javaee master build is broken since updated tycho to 1.3.0-SNAPSHOT > ------------------------------------------------------------------------------ > > Key: JBIDE-26461 > URL: https://issues.jboss.org/browse/JBIDE-26461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, cdi, jsf > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Blocker > Fix For: 4.10.0.AM1 > > > Jbosstools-javaee master build is broken since TP updated (tycho version moved to 1.3.0-SNAPSHOT). There are compilation errors, probably tycho dropped some dependency. > See the jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26461) jbosstools-javaee master build is broken since updated tycho to 1.3.0-SNAPSHOT

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26461?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26461: --------------------------------------- I am working on patch. > jbosstools-javaee master build is broken since updated tycho to 1.3.0-SNAPSHOT > ------------------------------------------------------------------------------ > > Key: JBIDE-26461 > URL: https://issues.jboss.org/browse/JBIDE-26461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, cdi, jsf > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Blocker > Fix For: 4.10.0.AM1 > > > Jbosstools-javaee master build is broken since TP updated (tycho version moved to 1.3.0-SNAPSHOT). There are compilation errors, probably tycho dropped some dependency. > See the jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26461) jbosstools-javaee master bui8ld is broken since updated tycho to 1.3.0-SNAPSHOT

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26461?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26461: ---------------------------------- Summary: jbosstools-javaee master bui8ld is broken since updated tycho to 1.3.0-SNAPSHOT (was: jbosstools-javaee master bui8ld is broken since updated TP) > jbosstools-javaee master bui8ld is broken since updated tycho to 1.3.0-SNAPSHOT > ------------------------------------------------------------------------------- > > Key: JBIDE-26461 > URL: https://issues.jboss.org/browse/JBIDE-26461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, cdi, jsf > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Priority: Blocker > Fix For: 4.10.0.AM1 > > > Jbosstools-javaee master build is broken since TP updated (tycho version moved to 1.3.0-SNAPSHOT). There are compilation errors, probably tycho dropped some dependency. > See the job: -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26461) jbosstools-javaee master bui8ld is broken since updated tycho to 1.3.0-SNAPSHOT

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26461?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26461: ---------------------------------- Description: Jbosstools-javaee master build is broken since TP updated (tycho version moved to 1.3.0-SNAPSHOT). There are compilation errors, probably tycho dropped some dependency. See the jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... was: Jbosstools-javaee master build is broken since TP updated (tycho version moved to 1.3.0-SNAPSHOT). There are compilation errors, probably tycho dropped some dependency. See the job: > jbosstools-javaee master bui8ld is broken since updated tycho to 1.3.0-SNAPSHOT > ------------------------------------------------------------------------------- > > Key: JBIDE-26461 > URL: https://issues.jboss.org/browse/JBIDE-26461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, cdi, jsf > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Priority: Blocker > Fix For: 4.10.0.AM1 > > > Jbosstools-javaee master build is broken since TP updated (tycho version moved to 1.3.0-SNAPSHOT). There are compilation errors, probably tycho dropped some dependency. > See the jenkins job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26461) jbosstools-javaee master bui8ld is broken since updated TP

by Ondrej Dockal (Jira)

Ondrej Dockal created JBIDE-26461: ------------------------------------- Summary: jbosstools-javaee master bui8ld is broken since updated TP Key: JBIDE-26461 URL: https://issues.jboss.org/browse/JBIDE-26461 Project: Tools (JBoss Tools) Issue Type: Bug Components: batch, cdi, jsf Affects Versions: 4.10.0.AM1 Reporter: Ondrej Dockal Fix For: 4.10.0.AM1 Jbosstools-javaee master build is broken since TP updated (tycho version moved to 1.3.0-SNAPSHOT). There are compilation errors, probably tycho dropped some dependency. See the job: -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26388) TP: create target platform based on Eclipse 4.10 (Simrel 2018-12)

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26388?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26388: ------------------------------------ Latest TP appears to have this list of duplicate IUs: {code} [WARNING] Found 12 duplicate jbosstools plugins: [WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar [WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar [WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar [WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.10.0.v20180703-1553.jar [WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar [WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.10.0.v20180703-1553.jar [WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.2.0.v20180409-1502.jar [WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar [WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar [WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar [WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.5.0.v20181003-1532.jar [WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.5.0.v20181003-1532.jar [WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20170814-1820.jar [WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar [WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.1.0.v20171214-1510.jar [WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.misc_7.5.0.v20181003-1532.jar [WARNING] [7] jbosstools-multiple.target.repo/plugins/org.apache.lucene.misc_7.1.0.v20180220-1923.jar [WARNING] [8] jbosstools-multiple.target.repo/plugins/org.apache.lucene.queryparser_7.5.0.v20181003-1532.jar [WARNING] [8] jbosstools-multiple.target.repo/plugins/org.apache.lucene.queryparser_6.1.0.v20161115-1612.jar [WARNING] [8] jbosstools-multiple.target.repo/plugins/org.apache.lucene.queryparser_7.1.0.v20180905-1540.jar [WARNING] [9] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.2.200.v20180921-1416.jar [WARNING] [9] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.400.v20180921-1416.jar [WARNING] [10] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar [WARNING] [10] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.2.1.v20180823-1831.jar [WARNING] [11] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar [WARNING] [11] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar [WARNING] [12] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar [WARNING] [12] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar {code} Worst offenders are the 3 and 4 versions of Lucene deps. Have you tried to remove the old ones to see if things Just Work w/ fewer singletons? > TP: create target platform based on Eclipse 4.10 (Simrel 2018-12) > ----------------------------------------------------------------- > > Key: JBIDE-26388 > URL: https://issues.jboss.org/browse/JBIDE-26388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.10.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Major > Labels: releasework > Fix For: 4.10.0.AM1, 4.10.0.Final > > Attachments: jbosstools-multiple-considerversions-4.9.0.Final-4.10.0.AM1.p2diff, jbosstools-multiple-ignoreversions-4.9.0.Final-4.10.0.AM1.p2diff > > > In order to start Eclipse 4.10-based builds, we need an updated target platform. > Note that Eclipse 4.10 drops support for win32 and lin32 platforms, so poms will need to be updated accordingly. 32-bit is dead, long live 64-bit! > For sprint 156 / AM1: simrel M1 > For sprint 157 / AM1: simrel M2 > For sprint 158 / GA: simrel M3/RC1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4642) JDK9 Certification - *running* Devstudio with jdk9

by Pavol Srna (Jira)

[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-4642: ---------------------------------- hi [~odockal], this jira is irrelevant at this time. Let's open new one for jdk 11 - to link issues found at one place. However we will track the complete certification in a polarion test run, because this has not been working well. It was very hard to see why the sub jiras were left open - because it was not done yet?, or becase there was an issue? So to move forward - let's open jdk 11 epic to link new jdk 11 issues that will be found at one place. And let's track the complete jdk 11 certification in a polarion test run. > JDK9 Certification - *running* Devstudio with jdk9 > -------------------------------------------------- > > Key: JBDS-4642 > URL: https://issues.jboss.org/browse/JBDS-4642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: build > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Major > Fix For: 12.x > > > This is an epic for tracking JDK9 Devstudio Certification. > All components need to be retested (run) with JDK9. > Please link issues found here. > Please do only resolve the subtasks, when the component *is* certified running with jdk9. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4642) JDK9 Certification - *running* Devstudio with jdk9

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ] Ondrej Dockal edited comment on JBDS-4642 at 10/29/18 12:27 PM: ---------------------------------------------------------------- [~psrna] [~nickboldt] Shouldn't we create new jira for jdk 11 certification? I tried devstudio with jdk 11 and got some issues: BIDE-26459. Jdk 9 will not be supported if I am not mistaken? was (Author: odockal): [~psrna] [~nickboldt] Shouldn't we create new jira for jdk 11 certification? > JDK9 Certification - *running* Devstudio with jdk9 > -------------------------------------------------- > > Key: JBDS-4642 > URL: https://issues.jboss.org/browse/JBDS-4642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: build > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Major > Fix For: 12.x > > > This is an epic for tracking JDK9 Devstudio Certification. > All components need to be retested (run) with JDK9. > Please link issues found here. > Please do only resolve the subtasks, when the component *is* certified running with jdk9. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4642) JDK9 Certification - *running* Devstudio with jdk9

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ] Ondrej Dockal edited comment on JBDS-4642 at 10/29/18 12:27 PM: ---------------------------------------------------------------- [~psrna] [~nickboldt] Shouldn't we create new jira for jdk 11 certification? I tried devstudio with jdk 11 and got some issues: JBIDE-26459. Jdk 9 will not be supported if I am not mistaken? was (Author: odockal): [~psrna] [~nickboldt] Shouldn't we create new jira for jdk 11 certification? I tried devstudio with jdk 11 and got some issues: BIDE-26459. Jdk 9 will not be supported if I am not mistaken? > JDK9 Certification - *running* Devstudio with jdk9 > -------------------------------------------------- > > Key: JBDS-4642 > URL: https://issues.jboss.org/browse/JBDS-4642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: build > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Major > Fix For: 12.x > > > This is an epic for tracking JDK9 Devstudio Certification. > All components need to be retested (run) with JDK9. > Please link issues found here. > Please do only resolve the subtasks, when the component *is* certified running with jdk9. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4642) JDK9 Certification - *running* Devstudio with jdk9

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ] Ondrej Dockal commented on JBDS-4642: ------------------------------------- [~psrna] [~nickboldt] Shouldn't we create new jira for jdk 11 certification? > JDK9 Certification - *running* Devstudio with jdk9 > -------------------------------------------------- > > Key: JBDS-4642 > URL: https://issues.jboss.org/browse/JBDS-4642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: build > Reporter: Pavol Srna > Assignee: Pavol Srna > Priority: Major > Fix For: 12.x > > > This is an epic for tracking JDK9 Devstudio Certification. > All components need to be retested (run) with JDK9. > Please link issues found here. > Please do only resolve the subtasks, when the component *is* certified running with jdk9. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 October 2018