April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24249) [Experiment] Build wtp + wtp.common.all so we can fix 3.8.2 w/ patches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24249?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24249: ------------------------------------ Got a successful build [1] so now I'm trying to build BOTH the aggregator and the common.all projects [2]. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > [Experiment] Build wtp + wtp.common.all so we can fix 3.8.2 w/ patches > ---------------------------------------------------------------------- > > Key: JBIDE-24249 > URL: https://issues.jboss.org/browse/JBIDE-24249 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM3 > > > Experimenting with how to build webtools so we can patch it to fix problems like JBIDE-24240 ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793 ) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-3866: ---------------------------------- [~rob.stryker] is this still relevant ? > vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server > ---------------------------------------------------------------------------------------- > > Key: JBDS-3866 > URL: https://issues.jboss.org/browse/JBDS-3866 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (previous installs of CDK and dependencies) > Reporter: Robert Terzi > Assignee: Rob Stryker > Fix For: 10.4.0.GA > > > vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse. > The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist. > The CDK server was shown as 'Started, Sychronized'. > The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either. > Synchronized seems misleading here, since no files had been sync'd yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23814) Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23814?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23814: ------------------------------------ [~adietish] can you check it because I think it has been fixed when we change the way we launched the oc client > Server Adaptor for JBoss EAP 7 on OpenShift fails with sync error > ----------------------------------------------------------------- > > Key: JBIDE-23814 > URL: https://issues.jboss.org/browse/JBIDE-23814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Red Hat JBoss Developer Studio > Version: 10.2.0.GA > Build id: GA-v20161125-1418-B55 > Build date: 20161125-1418 > JBoss Openshift UI Plugin > Version: 3.3.1.v20161125-0956 > OpenShift > openshift v3.3.1.3 > Reporter: Siamak Sadeghianfar > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.AM3 > > Attachments: jbds-error.png, jboss-eap70-openshift.png > > > When adding a Server Adapter for an JBoss EAP 7 based deployments on OpenShift, operation fails with this error: > {{Could not sync /private/tmp/workspace-demo/.metadata/.plugins/org.jboss.ide.eclipse.as.core/inventory-dev-ssadeghi@inventory/deploy to all pods running the service inventory > OpenShiftBinaryCapability process exited: error: auth info "ssadeghi-redhat.com" does not exist}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24216) CDK Server adapter editor: "Minishift Location" is not validated

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24216?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24216: ------------------------------- Sprint: devex #130 April 2017 > CDK Server adapter editor: "Minishift Location" is not validated > ----------------------------------------------------------------- > > Key: JBIDE-24216 > URL: https://issues.jboss.org/browse/JBIDE-24216 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4296) Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4296?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4296: ------------------------------------ I thougth that we plan to run with both empty and include/exclude will be used only in special cases. But you are right, it is not the clever approach, especially considering problem like PMD. This PR solve this problem (not merged yet): Master: https://github.com/jbdevstudio/jbdevstudio-qa/pull/134 4.4.x: https://github.com/jbdevstudio/jbdevstudio-qa/pull/135 > Create smoke test that installs Devstudio from installer jar and then all the Central/EarlyAccess stuff on top > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4296 > URL: https://issues.jboss.org/browse/JBDS-4296 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: integration-tests, rpm > Affects Versions: 10.4.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.4.0.AM3 > > > We need to create jenkins job which can be used as smoke test for Devstudio installed from installer jar [0], on all three supported OS platforms (RHEL7/Fedora24, Win10, MacOS 10). > This job should be configurable, we want to be able to pass in a different parameters as URLs and then use the same job to test both snapshot and staging. > The job should: > # Install devstudio from installer jar > # Clean and start eclipse in strict mode and in clean work space > # Install all stuff from Red Hat Central *using graphical interface* > ** Install everything at once - this is the fastest approach but also makes diagnosing errors more difficult. > ** So, when problems occur, could re-run the job (manually or with naginator plugin?) using parameter connectorIDsToInstall = "net.sourceforge.pmd.eclipse" for example > # Restart Eclipse > # Check for errors > # Should also test if some software from Central works - run quickstarts or wizards > Possible configuration parameters: > * installer jar URL (snapshot/staging/stable) [0] > * jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (eg., https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... or https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1... or https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/) > * ERROR_PATTERN (like [rpm_rh_central_test|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.red...] has) > * TESTS_FORK = jbosstools ? > * TEST_BRANCH = master or jbosstools-4.4.x or jbosstools-4.4.4.x ? > * connectorIDsToInstall = "" (install everything found) or specific value [1] for re-running if something fails > [0] https://devstudio.jboss.com/10.0/staging/builds/devstudio-10.3.0.GA-build... or https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_10.0.neon... or https://devstudio.jboss.com/static/10.0/stable/builds/devstudio-10.3.0.GA... > [1] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1082) SwitchYard specific updates to separate it from Fuse proper.

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1082?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBTIS-1082: ------------------------------------------ Handled with https://github.com/jboss-switchyard/tools/pull/658 and https://github.com/jboss-switchyard/tools/pull/659 We will need to revisit once the Fuse Tooling has an Oxygen build so we can update the path we depend on here: https://github.com/jboss-switchyard/tools/blob/master/pom.xml#L27 > SwitchYard specific updates to separate it from Fuse proper. > ------------------------------------------------------------ > > Key: JBTIS-1082 > URL: https://issues.jboss.org/browse/JBTIS-1082 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: switchyard > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > > Separate SwitchYard from Fuse Tooling proper. It should exist as a independent jar bundle. > Initial effort: - update to Oxygen JBTIS target platform > 1. Modify that org.switchyard.tools.bpmn2.feature requirement to be org.eclipse.bpmn2.modeler.feature.group [1.3.0,1.4.0] > 2. Pick up 4.5.0.AM1-SNAPSHOT as your JBTIS TP -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1017) Fuse - create a test which checks camel version detection for all available runtimes

by Dominik Jelinek (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1017?page=com.atlassian.jira.plugin... ] Dominik Jelinek commented on JBTIS-1017: ---------------------------------------- realize via matrix jenkins job > Fuse - create a test which checks camel version detection for all available runtimes > ------------------------------------------------------------------------------------ > > Key: JBTIS-1017 > URL: https://issues.jboss.org/browse/JBTIS-1017 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Final > Reporter: Tomáš Sedmík > Assignee: Dominik Jelinek > Priority: Critical > > There is a Camel Version detection in _New Fuse Integration Project Wizard_. Write a test which checks camel version detection for all available runtimes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24253) run batch with reddeer2

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24253?page=com.atlassian.jira.plugi... ] Ondrej Dockal reassigned JBIDE-24253: ------------------------------------- Assignee: Ondrej Dockal (was: Lukáš Valach) > run batch with reddeer2 > ----------------------- > > Key: JBIDE-24253 > URL: https://issues.jboss.org/browse/JBIDE-24253 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests > Reporter: Rastislav Wagner > Assignee: Ondrej Dockal > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-940) Create a test for checking whether a runtime detection also creates a server

by Dominik Jelinek (JIRA)

[ https://issues.jboss.org/browse/JBTIS-940?page=com.atlassian.jira.plugin.... ] Dominik Jelinek commented on JBTIS-940: --------------------------------------- Found workaround, in JBoss Runtime Detection is needed download and install new runtime, after that is possible to test this issue > Create a test for checking whether a runtime detection also creates a server > ---------------------------------------------------------------------------- > > Key: JBTIS-940 > URL: https://issues.jboss.org/browse/JBTIS-940 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.0.Final > Reporter: Andrej Podhradsky > Assignee: Dominik Jelinek > > Create a test for checking whether a runtime detections also creates a server. For more info please see FUSETOOLS-2176. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4361) BundleException: Exception in net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop()

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4361: ---------------------------------- Summary: BundleException: Exception in net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop() Key: JBDS-4361 URL: https://issues.jboss.org/browse/JBDS-4361 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: central Affects Versions: 10.4.0.AM3 Environment: Fedora 24, openjdk version "1.8.0_121", devstudio-10.4.0.AM3-v20170410-1340-B413 Reporter: Lukáš Valach Assignee: Nick Boldt Priority: Minor Fix For: 10.4.0.AM3 Attachments: eclipse-log-CheckstyleUIPlugin.log I saw this exception in eclipse log after installation of everything from RH Central. I see that you have met this problem in JBDS-2666 and jira was closed as 'can't reproduce'. It seems that this error is reproducable using automated test of installation from RH Central \[1\], see builds 18-20, choose OS and open eclipse-log-startAfterInstall.log. This error is in all builds and on all systems. \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... {code} !ENTRY net.sf.eclipsecs.ui 4 0 2017-04-12 13:10:03.802 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Exception in net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop() of bundle net.sf.eclipsecs.ui. at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:850) at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:946) at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:314) at org.eclipse.osgi.container.Module.doStop(Module.java:636) at org.eclipse.osgi.container.Module.stop(Module.java:498) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1661) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1580) at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:270) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:147) at org.eclipse.osgi.container.Module.doStop(Module.java:636) at org.eclipse.osgi.container.Module.stop(Module.java:498) at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ExceptionInInitializerError at net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop(CheckstyleUIPlugin.java:123) at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:830) at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:823) ... 13 more Caused by: java.lang.NullPointerException at org.eclipse.ui.plugin.AbstractUIPlugin.imageDescriptorFromPlugin(AbstractUIPlugin.java:664) at net.sf.eclipsecs.ui.CheckstyleUIPluginImages.<clinit>(CheckstyleUIPluginImages.java:95) ... 18 more Root exception: java.lang.ExceptionInInitializerError at net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop(CheckstyleUIPlugin.java:123) at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:830) at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:823) at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:946) at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:314) at org.eclipse.osgi.container.Module.doStop(Module.java:636) at org.eclipse.osgi.container.Module.stop(Module.java:498) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1661) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1580) at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:270) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:147) at org.eclipse.osgi.container.Module.doStop(Module.java:636) at org.eclipse.osgi.container.Module.stop(Module.java:498) at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at org.eclipse.ui.plugin.AbstractUIPlugin.imageDescriptorFromPlugin(AbstractUIPlugin.java:664) at net.sf.eclipsecs.ui.CheckstyleUIPluginImages.<clinit>(CheckstyleUIPluginImages.java:95) ... 18 more {code} Log: [^eclipse-log-CheckstyleUIPlugin.log] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 12 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 April 2017