[
https://jira.jboss.org/jira/browse/JBIDE-4703?page=com.atlassian.jira.plu...
]
Nick Boldt updated JBIDE-4703:
------------------------------
Attachment: test.xml_3.zip
Probably the difference between AntRunner w/ JUnit3.8 + ETF and AntRunner in Eclipse.
Evidently there's a flaw in the way we run tests, and I want to move away from the
Eclipse3.2-era test framework to something that supports JUnit4 and SWTBot, both in
Eclipse and headlessly... I'm just not sure how to proceed to get your tests working
as is. If that's even possible w/ the current setup.
Here's how the test process runs the org.eclipse.ant.core.antRunner application:
$JAVA_HOME/bin/java $Xflags -enableassertions -cp $cpAndMain -ws $ws -os $os -arch $arch
\
-application org.eclipse.ant.core.antRunner -data $workspaceDir -f
${relengCommonBuilderDir}/builder/tests/test.xml $antTestTarget \
$Dflags -Dws=$ws -Dos=$os -Darch=$arch -D$installmode=true -Dbuildcfg=${buildcfg}
-DdownloadsDir=${downloadsDir} -DtestingDir=${testingDir} \
-DrelengBaseBuilderDir=${relengBaseBuilderDir}
-DrelengCommonBuilderDir=${relengCommonBuilderDir} -DrelengBuilderDir=${relengBuilderDir}
\
$J2SE15flags $J2SE16flags \
$properties -logger org.apache.tools.ant.DefaultLogger
(full script here
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.ecli...)
It then runs this script:
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.ecli...
which then fires up the generated test.xml for each plugin:
<ant antfile="(a){testPluginNameAndID}/test.xml"
dir="${eclipse-home}">
<property name="eclipse-home" value="${eclipse-home}" />
</ant>
I've attached the three generated test.xml files for the latest yellow build in
Hudson. If you can see what might be missing from the classpath, or how I'm using the
wrong/different classloaders... please let me know.
Include pi4soa CDL editor plugins into JBT
------------------------------------------
Key: JBIDE-4703
URL:
https://jira.jboss.org/jira/browse/JBIDE-4703
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Affects Versions: 3.1.0.M3
Reporter: Gary Brown
Assignee: Nick Boldt
Fix For: 3.1.0.M4
Attachments: test.xml_3.zip, testresults.zip
The pi4soa project provides a WS-CDL editor and associated capabilities that are required
for project Overlord.
The location of the pi4soa plugins is at:
https://pi4soa.svn.sourceforge.net/svnroot/pi4soa/trunk
There are two features that need to be included: org.pi4soa.feature.core and
org.pi4soa.feature.monitor.
The monitor feature and associated plugin may only be required temporarily, as a web
based monitoring UI is being developed, but for now it is required.
--
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