August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26283: ------------------------------------------ [~nickboldt]: referring to your [findings|https://issues.jboss.org/browse/JBIDE-26283?focusedCommentId=136...] I ack that eclipse source references are ignored and thus shouldn't trigger a baseline comparison failure (as found out by [~jeffmaury] in his [comment|https://issues.jboss.org/browse/JBIDE-26283?focusedCommentId=1361...]: https://github.com/eclipse/tycho/blob/master/tycho-artifactcomparator/src... {code} // this is common attribute not supported by Tycho yet ignoredKeys.add(new Name("Eclipse-SourceReferences")); {code} The other change in comments shouldn't trigger a failure in baseline comparison. Comparison is done based on keys and values, where comments should be ignored: https://github.com/eclipse/tycho/blob/master/tycho-artifactcomparator/src... So I still dont get why the baseline checks fails. Thoughts? > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.9.0.AM2 > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26283: ------------------------------------ I checked the forge repo and it seems this is caused by a dependency where aopalliance-1.0.jar has changed (at least in size) don't know why so we need to upversion > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.9.0.AM2 > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26161) Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26161?page=com.atlassian.jira.plugi... ] Martin Malina resolved JBIDE-26161. ----------------------------------- Resolution: Done OK, domek is now updated as well. Resolving. > Update Mac OS machines (deps, os, java, maven, etc.) and verify its usability in jenkins environment > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26161 > URL: https://issues.jboss.org/browse/JBIDE-26161 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Martin Malina > Fix For: 4.9.0.AM2 > > > Take a look and update/repair Mac os machines used in our infra, especially zamek and check out the others: > * domek > * bigmek > * dev-platform-mac1 > * dev-platform-mac2 > Make dev-platform-macX machines capable to run cdk > * add them to mac_xhyve label > Should not be dev-platform-macX upgraded to High Sierra? > cc: [~nickboldt] [~mmalina] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26286) server.it.weekly build errors: baseline and build artifacts have same version but different contents

by Martin Malina (JIRA)

Martin Malina created JBIDE-26286: ------------------------------------- Summary: server.it.weekly build errors: baseline and build artifacts have same version but different contents Key: JBIDE-26286 URL: https://issues.jboss.org/browse/JBIDE-26286 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, server Affects Versions: 4.9.0.AM2 Reporter: Martin Malina Assignee: Nick Boldt [~nickboldt], I need your help. I noticed that all of this job is red: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... For example see here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... {code} 09:39:58 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.archives.scanner.feature: baseline and build artifacts have same version but different contents 09:39:58 [ERROR] no-classifier: different 09:39:58 [ERROR] feature.xml: different {code} Google suggests that it's about <baselineRepositories> and how the content compares to what's actually being built. I didn't even know such thing existed, let alone that we're using it. Do you know what's going on? Or maybe [~rob.stryker] you know? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-632) Migrate StubUtility (and associated classes) into non-UI JDT plugin

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-632?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg commented on ERT-632: ------------------------------------- https://git.eclipse.org/r/124700/ and https://git.eclipse.org/r/c/124790/ are in much better shape now and should be reviewed soon. > Migrate StubUtility (and associated classes) into non-UI JDT plugin > ------------------------------------------------------------------- > > Key: ERT-632 > URL: https://issues.jboss.org/browse/ERT-632 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > This should involve migrating the following classes from within jdt.ui to some other bundle that doesn't depend on UI components. > CodeGeneration > CodeGenerationSettings > GetterSetterUtil > StubUtility > StubUtility2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-646) Generate p2 repository with signed Jetty project artifacts

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-646?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-646. ------------------------------- Resolution: Done https://ci.eclipse.org/jetty/job/jetty-rt-bundles-9/ is now capable of generating signed jetty bundles in a p2 repository and publishing them to the downloads section. http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.4.11.v20180... > Generate p2 repository with signed Jetty project artifacts > ---------------------------------------------------------- > > Key: ERT-646 > URL: https://issues.jboss.org/browse/ERT-646 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > As discussed in https://github.com/eclipse/jetty.project/issues/2639 , there are many approaches to this. The approach I've taken can be seen there. > One such proposal can be found at https://ci.eclipse.org/linuxtools/job/jetty-releng/ . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-647) Resolve remaining issues with Batik 1.9.1

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-647?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-647: -------------------------------- Sprint: devex #152 July 2018, devex #153 August 2018 (was: devex #152 July 2018) > Resolve remaining issues with Batik 1.9.1 > ----------------------------------------- > > Key: ERT-647 > URL: https://issues.jboss.org/browse/ERT-647 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > Batik 1.9.1 had some remaining issues that prevented the full stack from being adopted during the Photon release train by some other projects (eg. Sirius, Papyrus, GMF, BIRT, Graphiti, etc.) > We should resolve the remaining issues, re-include all the bundles in the stack and finally upgrade to Batik 1.10. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-646) Generate p2 repository with signed Jetty project artifacts

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-646?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-646: -------------------------------- Sprint: devex #152 July 2018, devex #153 August 2018 (was: devex #152 July 2018) > Generate p2 repository with signed Jetty project artifacts > ---------------------------------------------------------- > > Key: ERT-646 > URL: https://issues.jboss.org/browse/ERT-646 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > As discussed in https://github.com/eclipse/jetty.project/issues/2639 , there are many approaches to this. The approach I've taken can be seen there. > One such proposal can be found at https://ci.eclipse.org/linuxtools/job/jetty-releng/ . -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-632) Migrate StubUtility (and associated classes) into non-UI JDT plugin

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-632?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-632: -------------------------------- Sprint: devex #148 April 2018, devex #149 May 2018, devex #150 June 2018, devex #152 July 2018, devex #153 August 2018 (was: devex #148 April 2018, devex #149 May 2018, devex #150 June 2018, devex #152 July 2018) > Migrate StubUtility (and associated classes) into non-UI JDT plugin > ------------------------------------------------------------------- > > Key: ERT-632 > URL: https://issues.jboss.org/browse/ERT-632 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > This should involve migrating the following classes from within jdt.ui to some other bundle that doesn't depend on UI components. > CodeGeneration > CodeGenerationSettings > GetterSetterUtil > StubUtility > StubUtility2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4721) JDK11 Issues

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4721?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4721: ----------------------------- Fix Version/s: 12.9.0.AM3 > JDK11 Issues > ------------- > > Key: JBDS-4721 > URL: https://issues.jboss.org/browse/JBDS-4721 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: build > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 12.9.0.AM3 > > > This Jira is created to link JDK11 issues with devstudio. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 August 2018