March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11351) getting NPE errors when having local deployer with old file system setup

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11351: ------------------------------------------- Summary: getting NPE errors when having local deployer with old file system setup Key: JBIDE-11351 URL: https://issues.jboss.org/browse/JBIDE-11351 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Fix For: 3.3.0.Beta3 opened old workspace with a remote deployment setup without a matching host/path names and I got: "Could not publish to server" and a NPE exception: java.lang.NullPointerException at org.jboss.ide.eclipse.as.rse.core.RSEUtils.getRSEConfigName(RSEUtils.java:75) at org.jboss.ide.eclipse.as.rse.core.RSEUtils.getDeployRootFolder(RSEUtils.java:109) at org.jboss.ide.eclipse.as.rse.core.RSEUtils.getDeployRootFolder(RSEUtils.java:79) at org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.loadRemoteDeploymentDetails(RSEPublishMethod.java:169) at org.jboss.ide.eclipse.as.rse.core.RSEPublishMethod.publishStart(RSEPublishMethod.java:67) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishStart(DeployableServerBehavior.java:64) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:927) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Why arne't our server adapters checking their setup before NPE'ing ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-9923) Once cloning the repo fails because of missing key, you have to add your keys to the prefs and restart eclipse

by Andre Dietisheim (Created) (JIRA)

Once cloning the repo fails because of missing key, you have to add your keys to the prefs and restart eclipse -------------------------------------------------------------------------------------------------------------- Key: JBIDE-9923 URL: https://issues.jboss.org/browse/JBIDE-9923 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
11
0 / 0

[JBoss JIRA] (JBIDE-11339) Create an openshift client library for the new OpenShift REST service

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-11339: ---------------------------------------- Summary: Create an openshift client library for the new OpenShift REST service Key: JBIDE-11339 URL: https://issues.jboss.org/browse/JBIDE-11339 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta3 The current OpenShift service is RESTy, not really following RESTful design principles. Our current java client for the OpenShift PaaS is communicating with this service. The OpenShift team implemented an alternative, fully REST-full service which will replace the legacy service at some point. We therefore have to implement a client library for the new REST service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-10136) Move OpenShift Express component to github

by Nick Boldt (Created) (JIRA)

Move OpenShift Express component to github ------------------------------------------ Key: JBIDE-10136 URL: https://issues.jboss.org/browse/JBIDE-10136 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-10460) Openshift Express: Vertical scroll bar dose not work in embedded cartridge result output page

by meng bo (Created) (JIRA)

Openshift Express: Vertical scroll bar dose not work in embedded cartridge result output page --------------------------------------------------------------------------------------------- Key: JBIDE-10460 URL: https://issues.jboss.org/browse/JBIDE-10460 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Environment: Fedora15_i686 with screen resolution : 1680x1050 Reporter: meng bo Assignee: Andre Dietisheim Steps: 1. Create an Openshift application. 2. Edit this application and embedded more than four cartridge at one time. 3. Wait the result output page comes. Actual result: The vertical scroll bar doesn't work, and the cartridges information will show incomplete. (In my case, there are 6 cartridges embedded and only showed about 4 of them.) !2011-12-13-Embedded_cartridge_output.png! Expect result: The vertical scroll bar should work as usual. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

6
10
0 / 0

[JBoss JIRA] (JBIDE-11267) Remote Configuration, Runtime Server config missing field "Remote Configuration"

by Leo Breuss (JIRA)

Leo Breuss created JBIDE-11267: ---------------------------------- Summary: Remote Configuration, Runtime Server config missing field "Remote Configuration" Key: JBIDE-11267 URL: https://issues.jboss.org/browse/JBIDE-11267 Project: Tools (JBoss Tools) Issue Type: Bug Components: central, JBossAS/Servers Affects Versions: 3.3.0.Beta2 Reporter: Leo Breuss Assignee: Snjezana Peco In the JBoss Runtime Server configuration, I am no longer able to specify the Remote Configuration (e.g. standalong-full.xml). It seems like this field has been dropped between 20111208 and today's 3.3.0b2. In earlier versions, obviously designed for JBoss 6 and earlier, the implementation of the JBoss Runtime Server for JBoss 7 had some problems. I'm listing here some of the problems disucussed in the Forum Reference. 1. The path on the server to look for the existence of the configuration was the concatenation of <Remote Server Home> + "/server/" + <Remote Server Configuration>. But JBoss 7 has a different layout structure. No /server/ directory. Interestingly enough, the field Remote Server Home can be set by browsing the remote file system. 2. In the field "Remote Configuration" you should be able to select the appropriate configuration file from the remote server file system. Instead, one could browse for a local configuration, but had to manually strip the absolute path. Only the filename may remain, because of the concatenation. And the local JBoss installation has to reflect the remote JBoss regarding the configuration file names. The default value "default" did not work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
11
0 / 0

[JBoss JIRA] (JBIDE-10305) The username should get selected when you click into the Username text field

by Andre Dietisheim (Created) (JIRA)

The username should get selected when you click into the Username text field ---------------------------------------------------------------------------- Key: JBIDE-10305 URL: https://issues.jboss.org/browse/JBIDE-10305 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M5 The first page in the OpenShift Express wizard offers text fields for the username and the password. It would be convenient if the whole text in the username would get selected as soon as you click into it (or move to it with the tab/shift-tab). This way you could delete the current value with a single delete/backspace stroke. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

8
9
0 / 0

[JBoss JIRA] (JBIDE-11283) Remote Server Launch Configuration, wrong filepath separators in path to jboss-modules.jar in Automatically Calculated start command

by Leo Breuss (JIRA)

Leo Breuss created JBIDE-11283: ---------------------------------- Summary: Remote Server Launch Configuration, wrong filepath separators in path to jboss-modules.jar in Automatically Calculated start command Key: JBIDE-11283 URL: https://issues.jboss.org/browse/JBIDE-11283 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.Beta2 Environment: Eclipse 3.7 on Windows 7, JBoss Tools 3.3.0 Beta2 Reporter: Leo Breuss The remote path to jboss-modules.jar is rewritten with the wrong filepath separator. Source platform is Eclipse 3.7 on Windows 7 Remote platform is Linux (CentOS 6.2) Remote Home is "/opt/jboss-as/" In der Server view, double clicking the remote server, Open Launch Configuration. Last tab Remote Launch shows a start command (Automatically Calculated by default) which has an invalid remote path with backslashes for the jboss-modules.jar: ... -jar \opt\jboss-as\jboss-modules.jar ... The full start command: java -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/opt/jboss-as/standalone/log/boot.log" "-Dlogging.configuration=file:/opt/jboss-as/standalone/configuration/logging.properties" "-Djboss.home.dir=/opt/jboss-as" -jar \opt\jboss-as\jboss-modules.jar -mp "/opt/jboss-as/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone& -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-11142) Forge tests do not run with Maven

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11142: -------------------------------------- Summary: Forge tests do not run with Maven Key: JBIDE-11142 URL: https://issues.jboss.org/browse/JBIDE-11142 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Mickael Istria Assignee: Koen Aers When running a "mvn install" on forge, tests do not execute. Indeed, test plugins have packaging "eclipse-plugin" which does not run tests (except if surefire is called in a build/plugins/plugin/execution step). These bundles should be turned into "eclipse-test-plugin" so tycho-surefire-plugin will run them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
7
0 / 0

[JBoss JIRA] (JBIDE-10919) Forge: "Home" and "End" keys do not work as expected

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-10919: ---------------------------------- Summary: Forge: "Home" and "End" keys do not work as expected Key: JBIDE-10919 URL: https://issues.jboss.org/browse/JBIDE-10919 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 3.3.0.M5 Reporter: Pavol Srna Assignee: Koen Aers Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
4
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 2012