February 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4273) Problem installing Teiid from IS discovery site - possible use constraint violation from slf4j / slf4j-api

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4273?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4273: ----------------------------- Summary: Problem installing Teiid from IS discovery site - possible use constraint violation from slf4j / slf4j-api (was: Problem installing Teidd form IS discovery site - possible use constraint violation from slf4j / slf4j-api) > Problem installing Teiid from IS discovery site - possible use constraint violation from slf4j / slf4j-api > ---------------------------------------------------------------------------------------------------------- > > Key: JBDS-4273 > URL: https://issues.jboss.org/browse/JBDS-4273 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm > Affects Versions: 10.3.0.GA > Environment: RHEL7, RHSCL 2.4 Alpha 1.1, rh-eclipse46-devstudio.x86_64 10.3-0.20170206.0203.el7 > Integration Stack Discovery site: http://download.jboss.org/jbosstools/neon/integration/updates/integration... > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.3.0.GA > > Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt > > > [~lvalach] said: {quote} > Hi Nick, > I tested installation of stuff from central as you described. I am not finished yet, but here is what I found. > -install latest integration stack bits from IS > -JBoss Fule Development - OK > -JBoss Business P. and Rules D. - OK > -JBoss Integration and SOA D. - OK > -JBoss Data Virtualization D. (IS early acess) > -there is problem with slf4j > -IS contains Teiid 11.0.1.CR1-v20170117-222 which should be fixed > -there are error like this: > {code} > !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences". > !STACK 0 > java.lang.LinkageError: loader constraint violation: when resolving method > "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader > (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, > org/slf4j/LoggerFactory, and the class loader > (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, > org/slf4j/impl/StaticLoggerBinder, have different > Class objects for the type org/slf4j/ILoggerFactory > used in the signature{code} > -install everything from Central (including PMD and Findbugs, and early access stuff. NOTE: newer versions of the Integration Stack connectors should already be installed from the step above) > -I installed everything using Central-Software/update, *no remediation action* was needed. > -Eclipse started but with many errors. So I have to find out which feature causes the problem.{quote} > [~nickboldt] said: > {quote} > loader constraint violation == two different versions of slf4j in the installed plugins > check in :~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 vs. in /opt/rh/ > Problem appears to be in *org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory*. {quote} > [~lvalach] said: > {quote} > {code} > cd ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64 > find . -iname *slf4j* > ./configuration/org.eclipse.osgi/1293/0/.cp/lib/slf4j-api-1.6.1.jar > {code} > The output for /opt/rh/ is quite long but I can say that it contains slf4j.api_1.7.4.jar > {quote} > [~nickboldt] said: > {quote} > So, we may have a conflict between slf4j and slf4j-api, which both use the same bundle names, but expose packages differently. > Unclear which IS project is causing this problem as I thought we'd fixed both SY and TD already. > * https://issues.jboss.org/browse/SWITCHYARD-2976 > * https://issues.jboss.org/browse/TEIIDDES-2999 > {quote} > [~lvalach] said: > {quote} > I tried to install Jboss Data Virtualization Developement from [IS discovery site|http://download.jboss.org/jbosstools/neon/integration/updates/integr...] again. > Whole log: > [^rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt] > Slf4j files in ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/ > [^home_eclipse.txt] > Slf4j files in /opt/rh/ > [^opt_rh.txt] > The problem is caused by Teiid Designer and Teiid Designer Runtime. > Teiid DataTools Connectivity and Teiid Runtime Clients don't cause problem. > IS repository contains SwitchYard 2.3.0.CR1-v20170120-1347-B20 which works properly. > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23623. ------------------------------ Resolution: Done > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.Final > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23623: ------------------------------------ The above problem was fixed in the last run... however, the JIRA numbers were not passed to downstream scripts because it was run as jiralint instead of Jeff's userid. See JBIDE-23536. > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.Final > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-398) Deselected connection after deleted tag [EBZ#499919]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-398?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-398. ------------------------------- Fix Version/s: Neon.3 (4.6) Resolution: Done > Deselected connection after deleted tag [EBZ#499919] > ---------------------------------------------------- > > Key: ERT-398 > URL: https://issues.jboss.org/browse/ERT-398 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Priority: Minor > Labels: Docker, bzira > Fix For: Neon.3 (4.6) > > > Steps to reproduce: > 1. Pull any image. > 2. Add tag to this image. > 3. Click on added tag in Docker Explorer. > 4. Delete in Docker Images tab this newly created tag. > 5. Tag is deleted, but connection is deselected, so the Docker Images tab is empty. > I suggest in this case to select connection or images in Docker explorer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23713) Implement tests for aeri connector

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23713?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-23713: ---------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > Implement tests for aeri connector > ---------------------------------- > > Key: JBIDE-23713 > URL: https://issues.jboss.org/browse/JBIDE-23713 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aeri, integration-tests > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > > *check if connector is present > *check if connector can be enabled/disabled -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4237: -------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 10.x > > Attachments: Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23715) RedDeer: Eclipse wizard dialogs should handle open perspective shell

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23715?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-23715: ---------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > RedDeer: Eclipse wizard dialogs should handle open perspective shell > -------------------------------------------------------------------- > > Key: JBIDE-23715 > URL: https://issues.jboss.org/browse/JBIDE-23715 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > > https://github.com/jboss-reddeer/reddeer/issues/1565 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23729) Implement integration ui tests for validation of job.xml file in design view tab

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23729?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-23729: ---------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > Implement integration ui tests for validation of job.xml file in design view tab > --------------------------------------------------------------------------------- > > Key: JBIDE-23729 > URL: https://issues.jboss.org/browse/JBIDE-23729 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration_tests > Fix For: 4.4.3.Final > > > Implement ui int. tests for batch job.xml validation that is used in design view tab. It is a subset of features referenced in [jira|https://issues.jboss.org/browse/JBIDE-23728]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23734) dedupe vpe unit test jobs / migrate vpe builds to CCI

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23734?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-23734: ---------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > dedupe vpe unit test jobs / migrate vpe builds to CCI > ----------------------------------------------------- > > Key: JBIDE-23734 > URL: https://issues.jboss.org/browse/JBIDE-23734 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > > There are four VPE unit test jobs. We probably only need 2 of those. > These both run on multiple OSes: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > These probably run the same unit tests, but against master or 4.4.x branches, and are called from the VPE build jobs [1], [2] on Boston MW Jenkins (because the tests were failing to run in Boston): > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master/ > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_4.4.neon/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-23623: ---------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.Final > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017