March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3826) Some components fail with folder name containing non-standard characters

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3826?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3826. --------------------------------- Resolution: Done I've fixed both issues. Below is explanation what was the problem with each installer: 1. In DevStudio installer generated .bat file to run eclipse p2-director when installing devstudio out of p2-repo embedded into installer.jar. '%' is a special symbol and gets replaced to current .bat file name, so it leads to error in DevStudio installer. Also # in path causes p2-director to fail, because it cannot find framework path 2. Cygwin 'layered' powershell command cannot handle '&' in executable file name (1) is fixed by banning % and # chars from target directory. (2) is fixed by enclosing file name into "'" > Some components fail with folder name containing non-standard characters > ------------------------------------------------------------------------ > > Key: JBDS-3826 > URL: https://issues.jboss.org/browse/JBDS-3826 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.4.0.AM2 > > > I have tried installing into this folder: > {noformat}c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform{noformat} > And JBDS installation failed immediately, the install.log was not very helpful. > {noformat}Fri, 15 Apr 2016 11:49:50 GMT-INFO: jbds - Execute c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - > Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds failed to install: Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24122) CDK3 runtime detector should look in ~/.minishift/config/config.json

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24122?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-24122: ----------------------------------- Assignee: Rob Stryker > CDK3 runtime detector should look in ~/.minishift/config/config.json > -------------------------------------------------------------------- > > Key: JBIDE-24122 > URL: https://issues.jboss.org/browse/JBIDE-24122 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection, server > Affects Versions: 4.4.4.AM2, 4.5.0.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.4.AM2, 4.5.0.AM1 > > > The ~/.minishift/config/config.json file lists the vm-driver chosen during the installer or setup-cdk. This should be correctly selected by runtime detection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-17710) error importing kitchensink angularjs quickstart when no jboss-eap runtime available

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17710?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-17710. ------------------------------ Resolution: Out of Date I wasn't able to reproduce it anymore (using Devstudio 10.4.0.AM1). If somebody will encounter this issue, feel free to reopen. Closing as Out Of Date. > error importing kitchensink angularjs quickstart when no jboss-eap runtime available > ------------------------------------------------------------------------------------ > > Key: JBIDE-17710 > URL: https://issues.jboss.org/browse/JBIDE-17710 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Beta2 > Environment: Linux 64 (Fedora 18), JDK 1.8 > Reporter: Nick Boldt > Assignee: Radim Hopp > Priority: Critical > Fix For: 4.4.4.Final > > Attachments: config-jboss-maven.png, error-quickstart-kitchensink-angularjs.png, install-jpa2-NPE.txt, jbds8b3a-jdk8-quickstart-angularjs-launch-NPE-thrown.log.txt, jbds8b3a-jdk8-quickstart-angularjs-launch-no-NPE-thrown-simpler-settings.xml.png, jbds8b3a-jdk8-quickstart-angularjs-launch-no-server-runtime-found-imports-fine-only-1-warning-compiles-ok.png, jbds8b3a-jdk8-quickstart-angularjs-launch-no-server-runtime-found.png, settings.xml > > > 1. install JBDS 8.0.0.Beta2-v20140617-2058-B166 from update site into Eclipse 4.4.0.R Luna JEE bundle. > 2. Install Arquillian from JBoss Central EA site (using -D flags above) > 3. launch kitchensink-angularjs quickstart. > 4. Get NPE installing JPA 2.0 > 5. Get numerous import problems in MemberRegistrationTest.java and other source files; quickfixes don't work. > Also had the same issues with JBT 4.2.0.Beta2, so it doesn't seem this is a JBDS only issue. > !error-quickstart-kitchensink-angularjs.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-22965: --------------------------------------- Do we support proxy settings for CDK3 server adapter in Eclipse? Or are we planning to do so? [~dbocharov] [~rob.stryker] ? > CDK tools should work behind proxy > ---------------------------------- > > Key: JBIDE-22965 > URL: https://issues.jboss.org/browse/JBIDE-22965 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: create_proxy-test_env.sh > > > Proxy support has been added in CDK vagrant box and in vagrant-registration plugin. > We should make sure our CDK tooling supports it too. > In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... > Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982 > + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25 > Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]: > {noformat} > lalatenduM: we exepect customers workstation is configured to porixy server > that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work > lalatenduM: on a customer worksttaion > lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information > lalatenduM: vagrant-registration uses subscription manager for registraton > lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23391) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23391?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23391: ---------------------------------- Assignee: Jeff MAURY (was: Fred Bricon) > For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [central] > ---------------------------------------------------------------- > > Key: JBIDE-23391 > URL: https://issues.jboss.org/browse/JBIDE-23391 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Minor > Labels: task > Fix For: 4.4.x > > > For JBIDE 4.4.2.AM3 [central]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.discovery.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui.workbench > > org.eclipse.equinox.p2.ui > > org.eclipse.mylyn.discovery.ui > -- > [CoreUIDependency] org.jboss.tools.maven.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.jdt.ui > > org.eclipse.ui.workbench > > org.eclipse.m2e.core.ui > -- > [CoreUIDependency] org.jboss.tools.maven.sourcelookup.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.eclipse.jdt.ui > > org.eclipse.ui.workbench > > org.eclipse.m2e.core.ui{code} > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23410) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [integration-tests]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23410?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23410: ---------------------------------- Assignee: Pavol Srna (was: Fred Bricon) > For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [integration-tests] > -------------------------------------------------------------------------- > > Key: JBIDE-23410 > URL: https://issues.jboss.org/browse/JBIDE-23410 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Nick Boldt > Assignee: Pavol Srna > Priority: Minor > Labels: task > Fix For: 4.4.x > > > For JBIDE 4.4.2.AM3 [integation-tests]: The following core plugins depend on UI plugins directly or indirectly. > {code} > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (core-has-ui-deps) @ org.jboss.tools.perf.test.core --- > [WARNING] Rule 0: org.jboss.tools.releng.CoreUIDependency failed with message: > [CoreUIDependency] org.jboss.tools.perf.test.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.jboss.tools.common.model.ui > > org.eclipse.ui.editors > > org.eclipse.ui.workbench > > org.eclipse.ui.ide > > org.jboss.tools.ui.bot.ext > > org.eclipse.ui.forms > > org.eclipse.ui.views.properties.tabbed > {code} > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23396) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [webservices]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23396?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23396: ---------------------------------- Assignee: Jeff MAURY (was: Brian Fitzpatrick) > For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [webservices] > -------------------------------------------------------------------- > > Key: JBIDE-23396 > URL: https://issues.jboss.org/browse/JBIDE-23396 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Minor > Labels: task > Fix For: 4.4.x > > > For JBIDE 4.4.2.AM3 [webservices]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.ws.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.eclipse.jst.jsf.ui > > org.eclipse.jst.ws.consumption.ui > -- > [CoreUIDependency] org.jboss.tools.ws.creation.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui > > org.eclipse.jdt.ui > > org.eclipse.jst.jsf.ui > > org.eclipse.jst.ws.consumption.ui > -- > [CoreUIDependency] org.jboss.tools.ws.jaxrs.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.wst.common.frameworks.ui > -- > [CoreUIDependency] org.jboss.tools.websockets.core is a Core plugin, but depends on these UI plugins directly or transitively: > > org.eclipse.ui{code} > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 updated JBDS-3866: ----------------------------- Fix Version/s: 10.4.0.GA (was: 10.4.0.AM2) > 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)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20063) locked up machine with "Loading descriptor" ...

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20063?page=com.atlassian.jira.plugi... ] Rastislav Wagner commented on JBIDE-20063: ------------------------------------------ Which commit addressed this issues ? If we cannot reproduce it than it should be closed as "cannot reproduce bug" > locked up machine with "Loading descriptor" ... > ----------------------------------------------- > > Key: JBIDE-20063 > URL: https://issues.jboss.org/browse/JBIDE-20063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Josef Kopriva > Fix For: 4.4.4.Final > > > when loaded javaee7-samples I ended up with frozen eclipse showing this: > https://www.dropbox.com/s/ttx9ppieads5m7n/Screenshot%202015-06-13%2001.31... > its so frozen I cannot even get a stacktrace from jps. > I tried looking for "Loading descriptor" in common and batch but no luck so maybe it is not in batch this is happening but something is definitely locking up ;/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20063) locked up machine with "Loading descriptor" ...

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20063?page=com.atlassian.jira.plugi... ] Rastislav Wagner edited comment on JBIDE-20063 at 3/22/17 12:24 PM: -------------------------------------------------------------------- Which commit addressed this issue ? If we cannot reproduce it than it should be closed as "cannot reproduce bug" was (Author: rawagner): Which commit addressed this issues ? If we cannot reproduce it than it should be closed as "cannot reproduce bug" > locked up machine with "Loading descriptor" ... > ----------------------------------------------- > > Key: JBIDE-20063 > URL: https://issues.jboss.org/browse/JBIDE-20063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Josef Kopriva > Fix For: 4.4.4.Final > > > when loaded javaee7-samples I ended up with frozen eclipse showing this: > https://www.dropbox.com/s/ttx9ppieads5m7n/Screenshot%202015-06-13%2001.31... > its so frozen I cannot even get a stacktrace from jps. > I tried looking for "Loading descriptor" in common and batch but no luck so maybe it is not in batch this is happening but something is definitely locking up ;/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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