February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23883) Client: release and use openshift-restclient-java 5.5.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23883?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23883: ---------------------------------------- Story Points: 1 Sprint: devex #127 February 2017 Assignee: Andre Dietisheim > Client: release and use openshift-restclient-java 5.5.0.Final > ------------------------------------------------------------- > > Key: JBIDE-23883 > URL: https://issues.jboss.org/browse/JBIDE-23883 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: client > Fix For: 4.4.3.Final > > > In JBIDE-23862 we started using the latest openshift-restclient-java 5.5.0-SNAPSHOT. > In order to be able to identify clients that are being used in our tooling we should refer to identifiable dependencies, which SNAPSHOTS are not. We should therefore switch JBT to use 5.5.0.Final. > In JBIDE-23862 we also started [skipping the enforcer|https://github.com/jbosstools/jbosstools-openshift/pull/1407/fil...] for openshift so that using the snapshot client would not break our builds. We have to remove this before we go final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23883) Client: release and use openshift-restclient-java 5.5.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23883?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23883: ------------------------------------- Labels: client (was: ) > Client: release and use openshift-restclient-java 5.5.0.Final > ------------------------------------------------------------- > > Key: JBIDE-23883 > URL: https://issues.jboss.org/browse/JBIDE-23883 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Priority: Blocker > Labels: client > Fix For: 4.4.3.Final > > > In JBIDE-23862 we started using the latest openshift-restclient-java 5.5.0-SNAPSHOT. > In order to be able to identify clients that are being used in our tooling we should refer to identifiable dependencies, which SNAPSHOTS are not. We should therefore switch JBT to use 5.5.0.Final. > In JBIDE-23862 we also started [skipping the enforcer|https://github.com/jbosstools/jbosstools-openshift/pull/1407/fil...] for openshift so that using the snapshot client would not break our builds. We have to remove this before we go final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23883) Client: release and use openshift-restclient-java 5.5.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23883?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23883: ------------------------------------- Fix Version/s: 4.4.3.Final > Client: release and use openshift-restclient-java 5.5.0.Final > ------------------------------------------------------------- > > Key: JBIDE-23883 > URL: https://issues.jboss.org/browse/JBIDE-23883 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Priority: Blocker > Labels: client > Fix For: 4.4.3.Final > > > In JBIDE-23862 we started using the latest openshift-restclient-java 5.5.0-SNAPSHOT. > In order to be able to identify clients that are being used in our tooling we should refer to identifiable dependencies, which SNAPSHOTS are not. We should therefore switch JBT to use 5.5.0.Final. > In JBIDE-23862 we also started [skipping the enforcer|https://github.com/jbosstools/jbosstools-openshift/pull/1407/fil...] for openshift so that using the snapshot client would not break our builds. We have to remove this before we go final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23883) Client: release and use openshift-restclient-java 5.5.0.Final

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23883: ---------------------------------------- Summary: Client: release and use openshift-restclient-java 5.5.0.Final Key: JBIDE-23883 URL: https://issues.jboss.org/browse/JBIDE-23883 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.4.3.AM2 Reporter: Andre Dietisheim Priority: Blocker In JBIDE-23862 we started using the latest openshift-restclient-java 5.5.0-SNAPSHOT. In order to be able to identify clients that are being used in our tooling we should refer to identifiable dependencies, which SNAPSHOTS are not. We should therefore switch JBT to use 5.5.0.Final. In JBIDE-23862 we also started [skipping the enforcer|https://github.com/jbosstools/jbosstools-openshift/pull/1407/fil...] for openshift so that using the snapshot client would not break our builds. We have to remove this before we go final. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23862) Server adapter: if "oc" in preferences is set to path with a " " syncing fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23862?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23862: ------------------------------------- Git Pull Request: https://github.com/openshift/openshift-restclient-java/pull/255, https://github.com/jbosstools/jbosstools-openshift/pull/1407 (was: https://github.com/openshift/openshift-restclient-java/pull/255) > Server adapter: if "oc" in preferences is set to path with a " " syncing fails > ------------------------------------------------------------------------------ > > Key: JBIDE-23862 > URL: https://issues.jboss.org/browse/JBIDE-23862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4273?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4273: ------------------------------------ This file causes the problem: ~/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/plugins/org.apache.directory.studio.slf4j-eclipselog_2.0.0.v20161101-M12.jar When I removed it, eclipse started without errors and I was able to create Teiid project. > Problem installing Teidd form 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] (JBDS-4272) Check user permission before creating symlinks in /usr/local/bin on mac OS

by Boleslaw Dawidowicz (JIRA)

[ https://issues.jboss.org/browse/JBDS-4272?page=com.atlassian.jira.plugin.... ] Boleslaw Dawidowicz updated JBDS-4272: -------------------------------------- Attachment: install.log > Check user permission before creating symlinks in /usr/local/bin on mac OS > -------------------------------------------------------------------------- > > Key: JBDS-4272 > URL: https://issues.jboss.org/browse/JBDS-4272 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Story > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Attachments: install.log > > > Installer fails if current user has no access to /usr/local/bin on mac OS -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-23882: --------------------------------- Description: We need to catch problems like in JBDS-4263. [~lvalach] said: {quote} I think I should automate test of installation from Central, because this procedure is quite time consuming. {quote} [~nickboldt] said: {quote} before you do that might want to look at the existing automated tests we have: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally so ... partial automation {quote} was:We need to catch problems like in JBDS-4263 > Automate test of installation of software from Red Hat Central into devstudio RPM > --------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.3.Final > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-23882: ------------------------------------ Summary: Automate test of installation of software from Red Hat Central into devstudio RPM Key: JBIDE-23882 URL: https://issues.jboss.org/browse/JBIDE-23882 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Environment: RHEL7, devstudio RPM Reporter: Lukáš Valach Assignee: Lukáš Valach Fix For: 4.4.3.Final We need to catch problems like in JBDS-4263 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23872) Tools clear war deployed files

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23872?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23872: ------------------------------- Component/s: server > Tools clear war deployed files > ------------------------------ > > Key: JBIDE-23872 > URL: https://issues.jboss.org/browse/JBIDE-23872 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.Final > Environment: Windows 7 64 > JDK 8 > Eclipse Neon 1 > JBoss Tools 4.4 > WildFly 10.1 > Reporter: Claudio Weiler > Priority: Minor > Fix For: 4.5.0.AM1 > > > After an Eclipse start war deployed files are deleted and not republished. > I have created a system lock to one of the html resources to try to dig more infos, but the exception shown refers to another resource: > "Error renaming D:\Aplic\wildfly-10.1.0\standalone\tmp\tmp7250132485298982117.MF to D:\Aplic\wildfly-10.1.0\standalone\deployments\testing-ear.ear\META-INF\MANIFEST.MF." -- 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