[
https://issues.jboss.org/browse/JBIDE-11879?page=com.atlassian.jira.plugi...
]
Vlado Pakan commented on JBIDE-11879:
-------------------------------------
When running SWT Bot tests via maven correct setting of
org.eclipse.swt.browser.XULRunnerPath affect these properties:
{noformat}
org.eclipse.swt.browser.XULRunnerInitialized
org.eclipse.swt.browser.XULRunnerPath
{noformat}
If property is not correctly set properties has these values and VPE is not available
within JBT.
{noformat}
org.eclipse.swt.browser.XULRunnerInitialized=false
org.eclipse.swt.browser.XULRunnerPath=
{noformat}
We should not need to set this property in pom.xml. It's limiting pom.xml to contain
exact name of XULRunner which is changed every time when XULRunner version is changed.
Maven runs this command when starting JBT:
{noformat}
/bin/sh -c cd
/home/hudson/workspace/jsf.bot.tests/jsf/tests/org.jboss.tools.jsf.ui.bot.test &&
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/bin/java -Dosgi.noShutdown=false
-Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86_64
'-javaagent:/home/hudson/workspace/jsf.bot.tests/.repository/org/jacoco/org.jacoco.agent/0.5.7.201204190339/org.jacoco.agent-0.5.7.201204190339-runtime.jar=destfile=/home/hudson/workspace/jsf.bot.tests/jsf/tests/target/jacoco.exec,append=true,includes=org.jboss.tools.*'
-Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -Dswtbot.test.skip=false
-Dtest.configurations.dir=resources/properties/
-Djbosstools.test.jboss-as.home=/home/hudson/workspace/jsf.bot.tests/jsf/tests/org.jboss.tools.jsf.ui.bot.test/../../../requirements/target/jboss-as-web-7.0.2.Final
-Dorg.jboss.tools.vpe.ui.bot.test.richfaces.ui.jar.location=/home/hudson/workspace/jsf.bot.tests/jsf/tests/org.jboss.tools.jsf.ui.bot.test/../../../requirements/target//richfaces-4.2.1.Final/artifacts/ui/richfaces-components-ui-4.2.1.Final.jar
-Dusage_reporting_enabled=false -jar
/home/hudson/workspace/jsf.bot.tests/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.2.0.v20110502/org.eclipse.equinox.launcher-1.2.0.v20110502.jar
-data
/home/hudson/workspace/jsf.bot.tests/jsf/tests/org.jboss.tools.jsf.ui.bot.test/target/work/data
-dev
file:/home/hudson/workspace/jsf.bot.tests/jsf/tests/org.jboss.tools.jsf.ui.bot.test/target/dev.properties
-install
/home/hudson/workspace/jsf.bot.tests/jsf/tests/org.jboss.tools.jsf.ui.bot.test/target/work
-configuration
/home/hudson/workspace/jsf.bot.tests/jsf/tests/org.jboss.tools.jsf.ui.bot.test/target/work/configuration
-application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties
/home/hudson/workspace/jsf.bot.tests/jsf/tests/org.jboss.tools.jsf.ui.bot.test/target/surefire.properties
-testApplication org.eclipse.ui.ide.workbench -product org.eclipse.platform.ide
-nouithread
{noformat}
When this command is run from shell then VPE is available in JBT. Mentioned properties are
properly set.
When run via maven VPE is not available.
Maven tests using VPE require org.eclipse.swt.browser.XULRunnerPath
to be set -> not multi-platform config
----------------------------------------------------------------------------------------------------------
Key: JBIDE-11879
URL:
https://issues.jboss.org/browse/JBIDE-11879
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JSF, QA, Visual Page Editor core, XULRunner
Affects Versions: 3.3.0.Beta2
Reporter: Mickael Istria
Assignee: Vlado Pakan
Fix For: 3.3.0.CR1
For an unknown (yet) reason, Maven tests using VPE need to set the
"org.eclipse.swt.browser.XULRunnerPath" system property to a platform-specific
value. This requires people on other platform to tweak the pom for their specific
environment, which is not convenient.
VPE should behave like Eclipse browser to resolve XulRunner, which runs well with Maven:
http://www.eclipse.org/swt/faq.php#howdetectmozilla . Seems like there is a difference
somewhere that makes VPE fail where SWT Browser works.
An example project is jsf/tests/org.jboss.tools.jsf.ui.bot.test
--
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