| 
| AutoGUI and deployments [message #38448] | Tue, 01 November 2005 11:52  |  | 
| Eclipse User  |  |  |  |  | Hi Ali: 
 first let me say your AutoGUI documentation is truly excellent, and the tool
 itself is looking really useful.
 
 I do have a question about deployments: it appears that the hyades
 deployment artifacts (e.g. the workspace location) are not currently being
 used during a standard launch: I've debugged the code down to the point
 where the remote process VM args are being specified:
 
 AutoGUIExecObjAdapter.setupExecutableObject(IExecutableObjec t, CFGClass,
 IImplementor, TPFDeployment) line: 61
 
 but the "-data" flag seems to be hard-coded to a temporary location at
 "TPTP-Auto-Workspace-" + System.currentTimeMillis();
 
 Am I missing something?  I'd like to fix this problem if you could point me
 in the right places.  I'm building from the CVS head
 /cvsroot/tptp/test/org.eclipse.tptp.test.auto.gui, and have the 2005-10-18
 build of eclipse/hyades installed.
 
 Regards,
 
 Simon.
 
 --
 --
 P. Simon Tuffs, D.Phil
 simon@simontuffs.com
 http://www.simontuffs.com
 |  |  |  | 
| 
| Re: AutoGUI and deployments [message #38514 is a reply to message #38448] | Tue, 01 November 2005 13:01  |  | 
| Eclipse User  |  |  |  |  | Hi Simon, 
 Thanks for the complements.
 You're right about users not being able to specify a workspace location
 resource with a customly defined deployment file.  This is something that
 couldn't be contained in 4.1 and will be addressed in 4.2
 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=109880).  To address this
 issue, you can write your own object adapter and have it registered in the
 plugin.xml.  You'll need to change the class attribute of the following
 fragment:
 
 <!-- Executable Object Adapter for TPTP Automated GUI Test Suite -->
 <ExecutableObjectAdapter
 name="AUTOMATEDGUI_EXECUTABLE_OBJECT_ADAPTER"
 
 class=" org.eclipse.tptp.test.auto.gui.internal.runner.AutoGUIExecOb jAdapter "
 id=" org.eclipse.tptp.test.auto.gui.internal.runner.AutoGUIExecOb jAdapter ">
 
 
 <SupportedTestType
 name="org.eclipse.hyades.test.auto.gui.testSuite">
 </SupportedTestType>
 
 
 </ExecutableObjectAdapter>
 
 The purpose of the object adapter is to sepcify the VM arguments.  You can
 look up to see if a deployment file is specified and whether a workspace
 location resource is associated with the file.  We'll appreciate it if you
 contribute your code to the Eclipse community by attaching it to the feature
 report.
 
 Good luck,
 
 Ali M.
 
 
 
 
 "Simon Tuffs" <simon@simontuffs.com> wrote in message
 news:dk86g7$1es$1@news.eclipse.org...
 > Hi Ali:
 >
 > first let me say your AutoGUI documentation is truly excellent, and the
 tool
 > itself is looking really useful.
 >
 > I do have a question about deployments: it appears that the hyades
 > deployment artifacts (e.g. the workspace location) are not currently being
 > used during a standard launch: I've debugged the code down to the point
 > where the remote process VM args are being specified:
 >
 >  AutoGUIExecObjAdapter.setupExecutableObject(IExecutableObjec t, CFGClass,
 > IImplementor, TPFDeployment) line: 61
 >
 > but the "-data" flag seems to be hard-coded to a temporary location at
 > "TPTP-Auto-Workspace-" + System.currentTimeMillis();
 >
 > Am I missing something?  I'd like to fix this problem if you could point
 me
 > in the right places.  I'm building from the CVS head
 > /cvsroot/tptp/test/org.eclipse.tptp.test.auto.gui, and have the 2005-10-18
 > build of eclipse/hyades installed.
 >
 > Regards,
 >
 > Simon.
 >
 > --
 > --
 > P. Simon Tuffs, D.Phil
 > simon@simontuffs.com
 > http://www.simontuffs.com
 >
 >
 |  |  |  | 
Powered by 
FUDForum. Page generated in 0.06488 seconds