July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1143) Fuse: Fix all automated tests for DevStudio 11.0.0

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1143?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1143: ------------------------------------- Fix Version/s: 4.5.0.CR1 (was: 4.5.0.Final) > Fuse: Fix all automated tests for DevStudio 11.0.0 > -------------------------------------------------- > > Key: JBTIS-1143 > URL: https://issues.jboss.org/browse/JBTIS-1143 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.5.0.AM1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > Fix For: 4.5.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1143) Fuse: Fix all automated tests for DevStudio 11.0.0

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1143?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1143. ------------------------------------ pushed to master > Fuse: Fix all automated tests for DevStudio 11.0.0 > -------------------------------------------------- > > Key: JBTIS-1143 > URL: https://issues.jboss.org/browse/JBTIS-1143 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.5.0.AM1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > Fix For: 4.5.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24548) Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24548?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24548: ------------------------------------- Priority: Major (was: Critical) > Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly > -------------------------------------------------------------------------------- > > Key: JBIDE-24548 > URL: https://issues.jboss.org/browse/JBIDE-24548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Environment: Running on Mac 10.12.4 > JBDS > Version: 10.3.0.GA > Build id: GA-v20170218-1636-B94 > Build date: 20170218-1636 > Installed minishift v1.0.1 > Reporter: Veer Muchandi > Assignee: Dmitrii Bocharov > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > * Created a Wildfly application on openshift web-ui > * Setup a server adapter > * Imported application to JBDS > * Made code changes and saved. > Result: > While the data seems to be exchanged, the changes are not synced with the pod and the application is not updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24670) Some versions of N&N don't contain other versions in the left-hand side menu

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24670?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24670. --------------------------------- I like it now. Thanks, [~nickboldt]. Closing. > Some versions of N&N don't contain other versions in the left-hand side menu > ---------------------------------------------------------------------------- > > Key: JBIDE-24670 > URL: https://issues.jboss.org/browse/JBIDE-24670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > This is a followup of JBIDE-24529. > Notice that this page contains all the versions in the left-hand side menu: > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.5.0.AM2.html > Then try different versions: > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.5.0.AM1.html > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.4.Final.html > Those are still ok. > But then try this: > https://tools.jboss.org/documentation/whatsnew/jbosstools/4.4.3.Final.html > Suddenly you only see one version in the menu. Why is that? > It seems that all the versions with a label (Coming Soon, Development or Stable) work correctly, whereas those without a label will only show their version when clicked and all other versions will disappear. > It seems like a bug. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24675) install-grinder test is broken due to Could not find shell matching: with text 'Installing Software'

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24675?page=com.atlassian.jira.plugi... ] Radim Hopp reassigned JBIDE-24675: ---------------------------------- Assignee: Lukáš Valach (was: Nick Boldt) > install-grinder test is broken due to Could not find shell matching: with text 'Installing Software' > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-24675 > URL: https://issues.jboss.org/browse/JBIDE-24675 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: install-tests > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Lukáš Valach > Fix For: 4.5.0.Final > > > {code} > 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install ) > 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. > 15:51:37 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0040f (Add Reposi) > 15:51:37 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. > 15:51:38 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa00367 (Install ) > 15:51:38 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. > 15:51:56 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0008e (workspace ) > 15:51:56 Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. > 15:52:02 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.816 sec > 15:52:02 > 15:52:02 Testcase: testInstall took 26.254 sec > 15:52:02 Caused an ERROR > 15:52:02 Internal error > 15:52:02 java.lang.RuntimeException: Internal error > 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:213) > 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:147) > 15:52:02 at org.jboss.tools.tests.installation.InstallTest.installFromSite(InstallTest.java:133) > 15:52:02 at org.jboss.tools.tests.installation.InstallTest.testInstall(InstallTest.java:78) > 15:52:02 at org.eclipse.swtbot.swt.finder.junit.internal.CapturingFrameworkMethod.invokeExplosively(CapturingFrameworkMethod.java:47) > 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBothttps://dev-platform-jenkins.rh... > 15:52:02 at org.eclipse.swtbot.swt.finder.junit.SWTBotJunit4ClassRunner.run(SWTBotJunit4ClassRunner.java:60) > 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:350) > 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.EclipseTestRunner.run(EclipseTestRunner.java:208) > 15:52:02 at org.eclipse.swtbot.eclipse.junit.headless.UITestApplication.runTests(UITestApplication.java:120) > 15:52:02 at org.eclipse.e4.ui.internal.workbench.swt.E4Testable.lambda$0(E4Testable.java:73) > 15:52:02 at java.lang.Thread.run(Thread.java:748) > 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException: Could not find shell matching: with text 'Installing Software' > 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:472) > 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntilWidgetAppears(SWTWorkbenchBot.java:1) > 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shells(SWTBotFactory.java:116) > 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shells(SWTWorkbenchBot.java:1) > 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:106) > 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1) > 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.shell(SWTBotFactory.java:97) > 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.shell(SWTWorkbenchBot.java:1) > 15:52:02 at org.jboss.tools.tests.installation.InstallTest.continueInstall(InstallTest.java:156) > 15:52:02 Caused by: org.eclipse.swtbot.swt.finder.widgets.TimeoutException: Timeout after: 5000 ms.: Could not find shell matching: with text 'Installing Software' > 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:522) > 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1) > 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:496) > 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1) > 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntil(SWTBotFactory.java:484) > 15:52:02 at org.eclipse.swtbot.eclipse.finder.SWTWorkbenchBot.waitUntil(SWTWorkbenchBot.java:1) > 15:52:02 at org.eclipse.swtbot.swt.finder.SWTBotFactory.waitUntilWidgetAppears(SWTBotFactory.java:466){code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1150) Incorrect version of Drools plugins

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1150?page=com.atlassian.jira.plugin... ] Paul Leacu reassigned JBTIS-1150: --------------------------------- Assignee: Paul Leacu > Incorrect version of Drools plugins > ----------------------------------- > > Key: JBTIS-1150 > URL: https://issues.jboss.org/browse/JBTIS-1150 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, drools/ jBPM > Affects Versions: 4.5.0.CR2, 11.0.0.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Drools plugins are in the following version > {code} > 7.0.1.Final > {code} > which doesn't follow our rules for versions (JBTIS-471) > {code} > x.y.z.BUILD_ALIAS-vYYYYMMDD-hhmm-B### > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4454) Path to JDK needs to be updated after every update of JDK

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4454?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4454: ---------------------------------- {code} $➔ alternatives --display java java - status is auto. link currently points to /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/bin/java /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/bin/java - family java-1.8.0-openjdk.x86_64 priority 1800121 ... Current `best' version is /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/bin/java. {code} But... {code}$➔ for j in $(whereis java); do if [[ -d ${j} ]]; then continue; elif [[ -x ${j} ]]; then echo ${j}; ls -la ${j}; ${j} -version; echo ""; fi; done /usr/bin/java lrwxrwxrwx 1 root root 22 Apr 3 09:59 /usr/bin/java -> /etc/alternatives/java openjdk version "1.8.0_121" OpenJDK Runtime Environment (build 1.8.0_121-b14) OpenJDK 64-Bit Server VM (build 25.121-b14, mixed mode) /opt/jdk1.8.0_102/bin/java -rwxr-xr-x. 1 root root 7734 Jun 22 2016 /opt/jdk1.8.0_102/bin/java java version "1.8.0_102" Java(TM) SE Runtime Environment (build 1.8.0_102-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode) /opt/jdk-9-ea+140/bin/java -rwxr-xr-x 1 10 143 8512 Oct 12 2016 /opt/jdk-9-ea+140/bin/java java version "9-ea" Java(TM) SE Runtime Environment (build 9-ea+140) Java HotSpot(TM) 64-Bit Server VM (build 9-ea+140, mixed mode) $➔ ls -la /etc/alternatives/java lrwxrwxrwx 1 root root 72 Apr 3 09:59 /etc/alternatives/java -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64/jre/bin/java {code} So the bottom line is that the default JDK found on my system is the one referenced by */etc/alternatives/java*. So rather than fetching the system value, we can search for one of these paths: * /etc/alternatives/java_sdk/bin/java * /etc/alternatives/java_sdk/jre/bin/java * /etc/alternatives/jre/bin/java ----- Also found another bug: If you select a Specific Java VM, then click back to Default Java VM, then Specific Java VM again, then click back to Default Java VM a second time, here's what ends up in your devstudio.ini file: {code} $➔ cat studio/devstudio.ini -vm /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64//usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-8.b14.fc24.x86_64 ... {code} > Path to JDK needs to be updated after every update of JDK > --------------------------------------------------------- > > Key: JBDS-4454 > URL: https://issues.jboss.org/browse/JBDS-4454 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build, installer > Affects Versions: 11.0.0.AM1 > Environment: Fedora 26 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 11.0.0.GA > > Attachments: image-2017-06-30-11-01-40-783.png, screenshot-1.png > > > After every update of JDK, path to JDK in file devstudio.ini needs to be updated. This does not happening in Eclipse. > !image-2017-06-30-11-01-40-783.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1150) Incorrect version of Drools plugins

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1150?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1150: ------------------------------------- Description: Drools plugins are in the following version {code} 7.0.1.Final {code} which doesn't follow our rules for versions (JBTIS-471) {code} x.y.z.BUILD_ALIAS-vYYYYMMDD-hhmm-B### {code} was: Drools plugins are in the following version {code} 7.0.1.Final {code} which doesn't follow our rules for versions, see JBTIS-471 > Incorrect version of Drools plugins > ----------------------------------- > > Key: JBTIS-1150 > URL: https://issues.jboss.org/browse/JBTIS-1150 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, drools/ jBPM > Affects Versions: 4.5.0.CR2, 11.0.0.CR2 > Reporter: Andrej Podhradsky > > Drools plugins are in the following version > {code} > 7.0.1.Final > {code} > which doesn't follow our rules for versions (JBTIS-471) > {code} > x.y.z.BUILD_ALIAS-vYYYYMMDD-hhmm-B### > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1150) Incorrect version of Drools plugins

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-1150: ---------------------------------------- Summary: Incorrect version of Drools plugins Key: JBTIS-1150 URL: https://issues.jboss.org/browse/JBTIS-1150 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution, drools/ jBPM Affects Versions: 4.5.0.CR2, 11.0.0.CR2 Reporter: Andrej Podhradsky Drools plugins are in the following version {code} 7.0.1.Final {code} which doesn't follow our rules for versions, see JBTIS-471 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24592) Study Foreman documentation

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24592?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24592: ---------------------------------- Sprint: devex #135 July 2017 > Study Foreman documentation > --------------------------- > > Key: JBIDE-24592 > URL: https://issues.jboss.org/browse/JBIDE-24592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci > Fix For: 4.5.0.Final > > > This issue consists of going through foreman documentation, tutorials and manuals. > Afterwards, it could be possible to address another steps in this process. > Docs: > https://www.theforeman.org/manuals/1.15/index.html > https://beryju.org/en/blog/getting-started-foreman-part-1#install_os > http://projects.theforeman.org/issues/432 > https://groups.google.com/forum/#!topic/foreman-users/FP9uTb8TAFY -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 July 2017