[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6175) Cannot create JbossWS client on EAP 4.2

[ https://jira.jboss.org/jira/browse/JBIDE-6175?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6175: ------------------------------------------ Grid, even with changing the path and the jvm arguments, your test doesn't run on my machine. It hangs as it tries to import the project. Couple of things... 1) I'm not a fan of hardcoding server locations in JUnit tests. I think it's a dangerous practice. 2) Talking to Nick Boldt, he suggested providing an external JVM argument to specify the path... Something like -DJBOSSWS_HOME_DEFAULT=D:/softinstall/jboss-4.2.3GA/jboss-4.2.3.GA You could then check to see if that argument is specified and override the internal variable... // if command-line argument is specified, it should take // precedence over the hard-coded value here. // -DJBOSSWS_HOME_DEFAULT=D:/softinstall/jboss-4.2.3GA/jboss-4.2.3.GA // then get the argument with // System.getProperty("JBOSSWS_HOME_DEFAULT"); String cmdlineHomeDefault = System.getProperty("JBOSSWS_HOME_DEFAULT"); if (cmdlineHomeDefault != null && cmdlineHomeDefault.trim().length() > 0) { AbstractJBossWSCommandTest.JBOSSWS_HOME_DEFAULT = cmdlineHomeDefault; System.setProperty(JBOSSWS_42_HOME, JBOSSWS_HOME_DEFAULT); AbstractJBossWSCommandTest.JBOSS_AS_42_HOME = System.getProperty( JBOSSWS_42_HOME, JBOSSWS_HOME_DEFAULT); } That said, this is still failing on RHEL for me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira