]
Denis Golovin commented on JBIDE-11879:
---------------------------------------
If it works for most platforms without maven settings for xulrunne, then it doesn't
worth to keep xulrunner configuration through system properties as default. As workaround
there should be profile activated for fedora 14 32-bit.
Does VPE works on fedora 14 32-bit in regular JBT installation?
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: Yahor Radtsevich
Fix For: 3.3.0.CR1
Attachments: vpemvnerror.png, vpemvnnotworking.png, vpemvnworking.png
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: