November 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4153) Cannot install Fuse Runtime on Windows using the installer

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBDS-4153: ------------------------------------- Summary: Cannot install Fuse Runtime on Windows using the installer Key: JBDS-4153 URL: https://issues.jboss.org/browse/JBDS-4153 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: installer Affects Versions: 10.1.0.GA Reporter: Aurélien Pupier Priority: Blocker On Windows, if using the installer with the Fuse Runtime and keeping it checked, the installation fails. i used https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.0.... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4153) Cannot install Fuse Runtime on Windows using the installer

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4153?page=com.atlassian.jira.plugin.... ] Aurélien Pupier updated JBDS-4153: ---------------------------------- Attachment: screenshot-1.png > Cannot install Fuse Runtime on Windows using the installer > ---------------------------------------------------------- > > Key: JBDS-4153 > URL: https://issues.jboss.org/browse/JBDS-4153 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Priority: Blocker > Attachments: screenshot-1.png > > > On Windows, if using the installer with the Fuse Runtime and keeping it checked, the installation fails. > i used https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.0.... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4149) Could not use Maven - NoClassDefFoundError: org/slf4j/Logger

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4149: ---------------------------------- New log shows constraint violations caused by javax.servlet-api 3.1.0 and javax.servlet 3.1.0.v201410161800, then this: {code}org.osgi.framework.BundleException: Unable to acquire the state change lock for the module: osgi.identity; type="osgi.bundle"; version:Version="1.7.1.20161026-1743"; osgi.identity="org.eclipse.m2e.jdt"; singleton:="true" [id=635] STARTED [STARTED] {code} So... this is no longer anything to do with slf4j or lucene. Lukas, please log to a separate file for each startup of Eclipse -- it will make separating your errors based on what you are doing in Eclipse easier. Here's how I run devstudio from rpm, in a unique workspace each time and logging to a different log file each time: {code} rm -fr ~/.eclipse scl enable rh-eclipse46 bash cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/ ./eclipse -consolelog -console -debug -data /tmp/wksp-`date +%Y%m%d-%H%M`| tee /tmp/rh-eclipse46-devstudio10.2.log.`date +%Y%m%d-%H%M`.txt {code} > Could not use Maven - NoClassDefFoundError: org/slf4j/Logger > ------------------------------------------------------------ > > Key: JBDS-4149 > URL: https://issues.jboss.org/browse/JBDS-4149 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: maven, rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Assignee: Fred Bricon > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: ClassNotFoundEx_20161102_095940.png, eclipse.log, eclipse_10.2-0.20161101.1258.log, rh-eclipse46-devstudio-snapshots-10_2.repo, rh-eclipse46.repo > > > I am not able to use embedded Maven. When I try to run Maven clean (or whatever else) I get following error message: > {code} > Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/Logger > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) > at java.lang.Class.privateGetMethodRecursive(Class.java:3048) > at java.lang.Class.getMethod0(Class.java:3018) > at java.lang.Class.getMethod(Class.java:1784) > at org.codehaus.plexus.classworlds.launcher.Launcher.getEnhancedMainMethod(Launcher.java:172) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:268) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: java.lang.ClassNotFoundException: org.slf4j.Logger > at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) > ... 10 more > {code} > Standalone maven installation works fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4152) On Windows, list of checkbox is unreadable if you try to select or unselect a line

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4152?page=com.atlassian.jira.plugin.... ] Aurélien Pupier updated JBDS-4152: ---------------------------------- Attachment: unreadable.png > On Windows, list of checkbox is unreadable if you try to select or unselect a line > ---------------------------------------------------------------------------------- > > Key: JBDS-4152 > URL: https://issues.jboss.org/browse/JBDS-4152 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Attachments: unreadable.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4152) On Windows, list of checkbox is unreadable if you try to select or unselect a line

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBDS-4152: ------------------------------------- Summary: On Windows, list of checkbox is unreadable if you try to select or unselect a line Key: JBDS-4152 URL: https://issues.jboss.org/browse/JBDS-4152 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: installer Affects Versions: 10.1.0.GA Reporter: Aurélien Pupier -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4151) Failed to start eclipse 10.2-0.20161101.1258 installed from RPM

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4151?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4151: ---------------------------------- According to [~rgrunber] the -clean is probably needed to deal with leftover metadata in ~/.eclipse > Failed to start eclipse 10.2-0.20161101.1258 installed from RPM > --------------------------------------------------------------- > > Key: JBDS-4151 > URL: https://issues.jboss.org/browse/JBDS-4151 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: eclipse.log, failed_to_start_eclipse_10.2-0.20161101.1258.png, rh-eclipse46-devstudio-snapshots-10_2.repo, rh-eclipse46.repo > > > I installed rh-eclipse46-devstudio-10.2-0.20161101.1258.el7.x86_64.rpm, then I started eclipse and choose workspace location (new folder). Then I got this error window !failed_to_start_eclipse_10.2-0.20161101.1258.png|thumbnail! > See also the log [^eclipse.log] . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23030: ------------------------------------------ I have the erroneous scaling info coming up even with my patch in place. Trying to fix this and update my PR. > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP > (copied from JBIDE-23412) > The following steps can be seen in the following screencast: > [^scale-to-shows-old-rc.ogv] > # ASSERT: have an app running (ex. nodejs-example) > # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently > # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. > # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) > # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" > # ASSERT: in Properties view: "Deployments" now shows 2 Deployments > # ASSERT: in OpenShift Explorer you now see 2 children/pods > # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service > Result: > The current number of pods is shown as 0. > !replicas-0.png! > But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: > !rc2-replicas-1.png! > The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. > !rc-1-replicas-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-975) SY - Avoid waiting for the job 'Synchronizing EMF resources'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-975?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-975: ------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/838 (was: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/837) > SY - Avoid waiting for the job 'Synchronizing EMF resources' > ------------------------------------------------------------ > > Key: JBTIS-975 > URL: https://issues.jboss.org/browse/JBTIS-975 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final > > > Sometimes It happens that some jobs take more than one minute and that's why my tests fail > {code} > org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running > Refreshing SwitchYard project configuration. > Synchronizing EMF resources > Updating Maven Project > {code} > Usually the test 'SwitchYardIntegrationDroolsTest' fails due to the above exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-974) SY - Use the logic for autobuilding from RedDeer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-974?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-974. ----------------------------------- pushed to master > SY - Use the logic for autobuilding from RedDeer > ------------------------------------------------ > > Key: JBTIS-974 > URL: https://issues.jboss.org/browse/JBTIS-974 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-975) SY - Avoid waiting for the job 'Synchronizing EMF resources'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-975?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-975: ------------------------------------ Summary: SY - Avoid waiting for the job 'Synchronizing EMF resources' (was: SY - Avoid waiting for the 'Synchronizing EMF resources') > SY - Avoid waiting for the job 'Synchronizing EMF resources' > ------------------------------------------------------------ > > Key: JBTIS-975 > URL: https://issues.jboss.org/browse/JBTIS-975 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.4.0.Final > > > Sometimes It happens that some jobs take more than one minute and that's why my tests fail > {code} > org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running > Refreshing SwitchYard project configuration. > Synchronizing EMF resources > Updating Maven Project > {code} > Usually the test 'SwitchYardIntegrationDroolsTest' fails due to the above exception. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 November 2016