August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4661) JDK9 Certification - forge

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4661?page=com.atlassian.jira.plugin.... ] Josef Kopriva closed JBDS-4661. ------------------------------- I have run several ITests and it was looking good, so closing. > JDK9 Certification - forge > -------------------------- > > Key: JBDS-4661 > URL: https://issues.jboss.org/browse/JBDS-4661 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: forge > Reporter: Pavol Srna > Assignee: Josef Kopriva > Fix For: 12.9.0.AM1 > > -- 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 Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4721?page=com.atlassian.jira.plugin.... ] Josef Kopriva updated JBDS-4721: -------------------------------- Component/s: build > 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 > > 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

[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: ------------------------------------ According to https://github.com/eclipse/tycho/blob/master/tycho-artifactcomparator/src... both Build-Jdk and Eclipse-SourceReferences are ignored > 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26283: ------------------------------------ {quote}can we get the file in the JAR were the diff has been detected ?{quote} I gave you an example of a jar that fails the comparison test here: https://issues.jboss.org/browse/JBIDE-26283?focusedCommentId=13614123&pag... And the explanation is ... the manifest.mf differ because the Eclipse-SourceReferences is different, as the baseline was build BEFORE we moved to parent pom 4.9.0.AM1, and the latest builds are built AFTER that change. So the single line in the manifest differs. See the screenshots above. > 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-26214) Fuse Tools New and Noteworthy for 4.9.0.AM1

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26214?page=com.atlassian.jira.plugi... ] Tomáš Sedmík closed JBIDE-26214. -------------------------------- verified with master branch > Fuse Tools New and Noteworthy for 4.9.0.AM1 > --------------------------------------------------- > > Key: JBIDE-26214 > URL: https://issues.jboss.org/browse/JBIDE-26214 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Reporter: Jeff MAURY > Assignee: Aurélien Pupier > Priority: Critical > Labels: task > Fix For: 4.9.0.AM1 > > > Lars Heinemann, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Fuse Tools JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Fuse Tools by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26206 #comment Create N&N for Fuse Tools 4.9.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Fuse Tools for this milestone, please *reject* and *close* this issue. -- 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: ------------------------------------ To be honest I don't know how the comparison is done but I noticed that manifest has an header called Build-Jdk that stores the version of the JDK used to build the JAR. Or can we get the file in the JAR were the diff has been detected ? > 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-26098) Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26098?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26098: --------------------------------------- I do not think in any way that this could be a "show stopper". :) Except, I am suggesting to just remove test pom dependency that causes test app to crash while this will bring stacks tests back. Besides, we do not have to upversion all the components as I thought, I just saw all the artifacts from old ages and hoped to make better use of newer versions. Are there resources for verification of going up with httpcomponents in like 5 minor releases, no? Then do not do that, I had no specific reason for that except what I already wrote. > Update dependencies in org.jboss.tools.stacks and repair test failures in jbosstools_base-master job > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26098 > URL: https://issues.jboss.org/browse/JBIDE-26098 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: qa > Affects Versions: 4.6.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.0.AM1 > > > 1. Have stacks tests to be run on jenkins jbt-base master and pull request job and have them green (not just omitting stacks tests results). > 2. Update versions of maven plugins used as libraries in org.jboss.tools.stacks plugin: > * org.jboss.jdf.stacks-client; 1.0.3.Final -> no change > * org.yaml.snakeyaml; 1.10 -> 1.18 > * org.apache.httpcomponents.httpclient; 4.0.1 -> 4.5.5 > * org.apache.httpcomponents.httpcore; 4.0.1 -> 4.4.9 > * org.jboss.logging.jboss-logging; 3.1.2.GA -> 3.3.2.Final > 3. Run all stacks.tests available (only one test class was run) > 4. Check on dependencies and usages in org.jboss.jdf.stacks-client and org.jboss.tools.stacks (what needs to be update, does it broke something, what else is using it) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1229) Cannot install Teiid Designer into Devstudio 12.0.0

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1229?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1229: ------------------------------------------ Hi [~pleacu] as I mentioned before, a user will not hit this issue. I was able to successfully install the following features {code} com.jboss.devstudio.integration-stack.ds.feature.feature.group com.jboss.devstudio.integration-stack.bpr.feature.feature.group {code} in offline mode. > Cannot install Teiid Designer into Devstudio 12.0.0 > --------------------------------------------------- > > Key: JBTIS-1229 > URL: https://issues.jboss.org/browse/JBTIS-1229 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: teiid > Affects Versions: 4.6.0.CR1 > Environment: Red Hat Developer Studio > Version: 12.0.0.AM3 > Build id: AM3-v20180605-1618-B2654 > OS: Linux, v.3.10.0-693.21.1.el7.x86_64, x86_64 / gtk 2.24.31 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > > Cannot install Teiid Designer into Devstudio 12.0.0.AM3 from > https://devstudio.redhat.com/12/staging/updates/integration-stack/ > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457) > Missing requirement: Teiid DataTools Connectivity 11.1.3.v20180409-1740 (org.teiid.datatools.connectivity.feature.feature.group 11.1.3.v20180409-1740) requires 'org.eclipse.equinox.p2.iu; org.eclipse.datatools.sqltools.parsers.sql [1.0.2,2.0.0)' but it could not be found > Cannot satisfy dependency: > From: Teiid Designer 11.1.3.v20180502-1457 (org.teiid.designer.feature.feature.group 11.1.3.v20180502-1457) > To: org.eclipse.equinox.p2.iu; org.teiid.datatools.connectivity.feature.feature.group [11.1.3.v20180409-1740,11.1.3.v20180409-1740] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1236) Cannot install Devstudio IS 12.0.0.CR1 in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1236?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1236: ------------------------------------------ My test scenario is 1. Get the full list of features from the zip file 2. Install all of them from the zip file in offline mode The above scenario checks if all dependencies are correctly resolved. But it may happen that a user will not catch this, e.g. if org.eclipse.datatools.connectivity.oda.designer.feature.feature is not required by any main features such as teiid, drools etc. > Cannot install Devstudio IS 12.0.0.CR1 in offline mode > ------------------------------------------------------ > > Key: JBTIS-1236 > URL: https://issues.jboss.org/browse/JBTIS-1236 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 12.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 12.0.0.GA > > > {code} > !ENTRY org.eclipse.equinox.p2.director 4 10053 2018-08-02 15:44:43.462 > !MESSAGE Cannot complete the install because one or more required items could not be found. > !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2018-08-02 15:44:43.464 > !MESSAGE Software being installed: Data Tools Platform Open Data Access Designer 1.14.100.201806252017 (org.eclipse.datatools.connectivity.oda.designer.feature.feature.group 1.14.100.201806252017) > !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2018-08-02 15:44:43.465 > !MESSAGE Missing requirement: Data Tools Platform Open Data Access Designer 1.14.100.201806252017 (org.eclipse.datatools.connectivity.oda.designer.feature.feature.group 1.14.100.201806252017) requires 'org.eclipse.equinox.p2.iu; org.eclipse.pde.feature.group 3.4.0' but it could not be found > !ENTRY org.jboss.tools.usage 4 0 2018-08-02 15:44:43.549 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1236) Cannot install Devstudio IS 12.0.0.CR1 in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1236?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1236: ------------------------------------------ Please notice that the feature *org.eclipse.datatools.connectivity.oda.designer.feature.feature.group 1.14.100.201806252017* is located in https://devstudio.redhat.com/12/staging/updates/integration-stack/12.0.0.... or devstudio-integration-stack-12.0.0.CR1-updatesite.zip/targetplatform/features/ > Cannot install Devstudio IS 12.0.0.CR1 in offline mode > ------------------------------------------------------ > > Key: JBTIS-1236 > URL: https://issues.jboss.org/browse/JBTIS-1236 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 12.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 12.0.0.GA > > > {code} > !ENTRY org.eclipse.equinox.p2.director 4 10053 2018-08-02 15:44:43.462 > !MESSAGE Cannot complete the install because one or more required items could not be found. > !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2018-08-02 15:44:43.464 > !MESSAGE Software being installed: Data Tools Platform Open Data Access Designer 1.14.100.201806252017 (org.eclipse.datatools.connectivity.oda.designer.feature.feature.group 1.14.100.201806252017) > !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2018-08-02 15:44:43.465 > !MESSAGE Missing requirement: Data Tools Platform Open Data Access Designer 1.14.100.201806252017 (org.eclipse.datatools.connectivity.oda.designer.feature.feature.group 1.14.100.201806252017) requires 'org.eclipse.equinox.p2.iu; org.eclipse.pde.feature.group 3.4.0' but it could not be found > !ENTRY org.jboss.tools.usage 4 0 2018-08-02 15:44:43.549 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > {code} -- 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