April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19453) Remote host information does not fit in the server editor

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19453?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19453: --------------------------------------- OK, Max is right - when I make the window really really big then it's shown correctly. I counted that you need the window to be at least ~1030 pixels wide to show all the content properly. If I then start resizing the window to a smaller width, the two main columns will be getting smaller (cutting off more and more of the Browse buttons for the remote host) and eventually at the width of around 850 pixels, the horizontal scrollbar will appear and the columns will stay at this width even if you make the window smaller. > Remote host information does not fit in the server editor > --------------------------------------------------------- > > Key: JBIDE-19453 > URL: https://issues.jboss.org/browse/JBIDE-19453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: remote-runtime-does-not-fit.png, server-editor-2.png > > > Today I noticed this. When I set up a remote server and then open it in the Server editor, the part under Server Behavior where it shows the remote host configuration (e.g. Remote Server Home) does not fix - it needs more space to the right, but it's hidden and there is no way to scroll to view it. > !remote-runtime-does-not-fit.png! > The same problem applies to both JBDS 8.1.0.Beta1 and JBDS 9.0.0.Alpha1. So you may want to clone this for 4.3.x. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3430) Creating a AngularJS project from scratch fails with an error installing tern

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3430?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3430. ---------------------------- Fix Version/s: 9.0.0.Beta1 Resolution: Rejected Please stop using this pre-Alpha2 build from April 05. You're having problems because you're mixing old crap (April 05 pre-Alpha2 built in master branch) with new crap (April 17 Alpha2 actual bits built from Alpha2x branch). BTW, to know if you've mixed streams, compare the build numbers. B2918 (large number) = master. B13 (small number) = stable branch (Alpha2x). If you perform an update of JBDS first, you will be then able to install whatever Tern stuff you need. But because we hard code the version of Tern we require into the JST plugins, and that version is aligned to the version of JBDS, you have to update JBDS at the same time as installing Tern/JST. > Creating a AngularJS project from scratch fails with an error installing tern > ----------------------------------------------------------------------------- > > Key: JBDS-3430 > URL: https://issues.jboss.org/browse/JBDS-3430 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > The error is: > Your original request has been modified. > "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > Software currently installed: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > Only one of the following can be installed at once: > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822) > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150417-0104-B13) > Cannot satisfy dependency: > From: JBoss Developer Studio (Core Features) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.feature.feature.group 9.0.0.Alpha2-v20150405-1144-B2918) > To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Developer Studio (Branded Product) 9.0.0.Alpha2-v20150405-1144-B2918 (com.jboss.devstudio.core.package 9.0.0.Alpha2-v20150405-1144-B2918) > To: com.jboss.devstudio.core.feature.feature.group [9.0.0.Alpha2-v20150405-1144-B2918] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150417-0104-B13 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150417-0104-B13) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150417-0104-B13] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19049?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19049: --------------------------------------- I checked with latest nightly and indeed it works as Rob described. I would probably agree that it's not necessary to restrict the versions in the dialog. > Enable JBoss servers to run with java 9 > --------------------------------------- > > Key: JBIDE-19049 > URL: https://issues.jboss.org/browse/JBIDE-19049 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: Java9 > Fix For: 4.3.0.Beta1 > > > I briefly tried to use java 9 for our tooling and to run servers. > I downloaded it from here: > https://jdk9.java.net/download/ > {code} > nattura:8.0.2 rasp$ java -version > java version "1.9.0-ea" > Java(TM) SE Runtime Environment (build 1.9.0-ea-b45) > Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode) > {code} > I use OS X 10.10 Yosemite. > There are a couple of problems: > 1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that. > 2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all. > {code} > nattura:bin rasp$ ./standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final > JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > Unrecognized VM option 'MaxPermSize=256m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} > Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19697: --------------------------------------- OK, so the mystery remains :) The Eclipse instance I was running when this happened is in: /Users/rasp/jbossqa/JBDS/9.0.0/Eclipse-runtime-test.app So how can one of these: $ECLIPSE_HOME/../../../../studio/runtime_locations.properties or in $ECLIPSE_HOME/../../studio/runtime_locations.properties. result in one of these /Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha1-java8/studio/runtime_locations.properties /Users/rasp/jbossqa/JBDS/9.0.0/jbdevstudio-9.0.0.Alpha2-24/studio/runtime_locations.properties ? Remember my $ECLIPSE_HOME does not contain either jbdevstudio-9.0.0.Alpha1-java8 or jbdevstudio-9.0.0.Alpha2-24. That's just weird. > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19571: --------------------------------------- Actually it seems that the link downloads the FSW installer jar and not zip. So that might explain the problem. Indeed, I can only see the jar available on jboss.org: https://www.jboss.org/products/fsw/download/ So if they don't have a zip, that might be a no-go for us. > Add FSW to downloadable runtimes > -------------------------------- > > Key: JBIDE-19571 > URL: https://issues.jboss.org/browse/JBIDE-19571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > FSW 6.0 is not available in download runtimes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19571: --------------------------------------- Of course if this is really the wrong link in stacks, then the JDF JIRA needs to be reopened, too. But I'll leave that to you - I'm not 100 % sure now that it's the link. > Add FSW to downloadable runtimes > -------------------------------- > > Key: JBIDE-19571 > URL: https://issues.jboss.org/browse/JBIDE-19571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > FSW 6.0 is not available in download runtimes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-19571: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Add FSW to downloadable runtimes > -------------------------------- > > Key: JBIDE-19571 > URL: https://issues.jboss.org/browse/JBIDE-19571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > FSW 6.0 is not available in download runtimes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message

by Martin Malina (JIRA)

Martin Malina created JBIDE-19738: ------------------------------------- Summary: Failed runtime download offers no error message Key: JBIDE-19738 URL: https://issues.jboss.org/browse/JBIDE-19738 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.2.3.Final Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.3.0.Beta1 While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-19697: --------------------------------------- No,it won't. JBosTools/JBDS doesn't search ECLIPSE_HOME/../*. It has found your EAP 6.3 in $ECLIPSE_HOME/../../../../studio/runtime_locations.properties or in $ECLIPSE_HOME/../../studio/runtime_locations.properties. > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9563) AS7 does not pick hot-deployed jsp files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9563?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-9563. -------------------------------- Thanks, Max :) And closing once more :) > AS7 does not pick hot-deployed jsp files > ---------------------------------------- > > Key: JBIDE-9563 > URL: https://issues.jboss.org/browse/JBIDE-9563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.3.0.M3 > Environment: AS7 Final, JBDS 5.0 trunk build H737, JBossAS Tools 2.3.0.v20110817-1604-H645-M3 > Reporter: Libor Zoubek > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.2.0.Final > > > When saving jsp file, hotdeployment copies it over to server's deploy dir, but server does not notice that. Server should compile this jsp file and return new content via web browser. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 2015