Updates to Ant task

I've pushed through some bugs fixes over the last few days. Here is the list:
- Updated platform defaults to try the user trust directory first, then if not found, use the global trust directory, when localTrusted="true"
- Updated the platform trust directory paths to work with WindowsXP, Windows Vista/7, MacOSX, and Linux.
- Updated trust file to append and remove paths rather than create and destroy the file to support concurrent runs of the Ant task
- Updated inbound streaming to decode using UTF-8 to respect non-western languages coming from the FP
- Updated XML output to be safe for use with single quotes in failure/error messages
- Updated CIListner and Ant task to report the correct # of runs when multiple failures/errors for a single test are reported
I'm still having issues with the global trust directory on Linux (tested with Ubuntu), so unfortunatley no resolve for that issue yet. If anyone knows of the correct path to use, I'm definitely open to suggestion; we're currently using /etc/adobe/FlashPlayerTrust.
Although the changes have not been pushed to the FlexUnit master yet, if anyone would like to help me test out their platform of choice with my latest build of the Ant task, I would be very grateful. You can find the latest Ant task JAR and CIListener SWC @ http://flexunit.digitalprimates.net:8080/view/All/job/Demo-Versioned-Build/. Please note, you need to update both for the Ant task to work correctly.
Looking forward to any feedback.
-Brian

Manually create your manifest file ${input-dir}/META-INF/MANIFEST.MF before running your ant script. appc should pick up your manifest file instaed of creating a default one.
Make sure that the manifest file contains "version-info: Manifest-Version : version-number" as specified by the jar specification.
Regards,
Dhilip

Similar Messages

Using variables in WLST Script ant task

I have multiple scipts that are run using ant tasks, however, I do not want to have to enter the password every time one of these scripts is executed. Instead I would like to use the following ant task to store the password in a variable/property:
<target name="getPassword" >
 <echo message="Domain: ${domain}" />
<echo message="Username: system" />
<input message="Please enter password:" addproperty="password" />
</target>
I would then like to use that variable/property everytime a script is executed like this:
 <target name="deploy4x">
 <echo message="***** Copying 4X.ear *****" />
 <copy file="${build.path}\jar\4X.ear" todir="${apps.dir}" preservelastmodified="true"/>
 <echo message="***** Updating 4X.ear on ${domain} *****"/>
 <wlst debug="true" fileName="Deploy4X.py" executeScriptBeforeFile="true" failonerror="true" >
 <script>
 connect('system','%s' % ${password},'%s' % $url)
 </script>
 </wlst>
 </target>
However, the script blows up every time I try to run it b/c of the connect() line. I have also tried connect('system','%s' % password, '%s' % url).
Has anyone else successfully used variables in an Ant WLST Script task?
Thanks.

Hi,
when I use *XDIM_MEMBERSET ACCOUNT AS %TEST% = BAS(REVENUE) - it work fine.
BUT ! after my first commit, it seems like the variable value is lost. And the *Xdim_memberset takes all.....
Fortunately enough, *select still contains the variable value after *commit.
Thanks,
Joergen
*Correction !
It actually works, it still contains the variable value after commit !!
Edited by: Jørgen Dalby Andersen on Dec 30, 2011 1:33 PM

Java.lang.NullPointerException running flexunit ant task in 4.1 Beta 2

Hello,
After trying to debug this all day, I thought I would ask the community.
I am trying out the new FU4.1 Beta 2 (3.5) from the downloads page. We have a working CI system set up with 4.0, and I thought trying out 4.1 beta 2 would simply be a matter of replacing the binaries in my lib folder and re-running the ant script. Evidently not, or else I am missing something.
After updating to the 4.1 Beta 2 binaries, if I re-run a sample project in Eclipse, the build fails with a java NullPointerException when the <flexunit> ant task is invoked. We have an involved setup that uses the groovy AntBuilder and other esoteric constructs, so I thought I would create a very simple test script similar to the sample CI project to see if that would work. Unfortunately, I am still seeing the NPE. The worst part is that there is absolutely no debug information provided - no message, no traceback. I even attached the Ant source and debugged it. I could see the NPE being caught, but it contained a null message and null traceback.
Here is the simplified ant script:
<project name="tests" basedir=".">
 <target name="test-init" depends="">
 <mkdir dir="${build.dir}"/>
 <mkdir dir="${reports.dir}"/>
 <mkdir dir="${reports.xml}"/>
 <mkdir dir="${reports.html}"/>
 
 
 <flexunit
 swf="${build.dir}/TestRunner.swf"
 toDir="${reports.xml}"
 haltonfailure="false"
 verbose="true"
 localTrusted="true"
 timeout="60000"/>
 
 <junitreport todir="${reports.xml}">
 <fileset dir="${reports.xml}">
 <include name="TEST-*.xml" />
 </fileset>
 <report format="frames" todir="${reports.html}" />
 </junitreport>
 </sequential>
 </target>
</project>
The output is:
Buildfile: C:\EclipseWorkspace\tests\Source\Flex\build_test.xml
test-init:
run-flex-tests:
[flexunit] Validating task attributes ...
BUILD FAILED
C:\EclipseWorkspace\tests\Source\Flex\build_test.xml:23: java.lang.NullPointerException
Total time: 297 milliseconds
Is there something obvious I am missing?
Thanks for any help!
Trevor

Brian,
OK, a colleague worked with me (thanks, John!) to debug the problem a little further, and I think we found the fundamental problem. I wanted to post that info to save you some time...
Aside: One thing we did have to do was to rebuild the flexUnitTasks.jar to include debug information, since the binary in the 4.1 beta 2 package did not have debug=true. I'd suggest that we might want to change the build script to build the binaries with debug moving forward.
Back to the problem.
The NullPointerException is thrown in TaskConfiguration::validateSharedProperties(), when equals() is invoked. Here is the code snippet:
 //if we can't find the FLEX_HOME and we're using ADL or compilation
 if((flexHome == null || !flexHome.exists()) && (testRunConfiguration.getPlayer().equals("air") || shouldCompile()))
 throw new BuildException("Please specify, or verify the location for, the FLEX_HOME property. "
 + "It is required when testing with 'air' as the player or when using the 'testSource' element. "
 + "It should point to the installation directory for a Flex SDK.");
In my case, I do not have a FLEX_HOME property set in Ant currently. I'll bet most folks have this set, so the logic would run differently for them. For my case, the (flexHome == null) check is true. That means that the testRunConfiguration.getPlayer().equals("air")check will occur next, and here is the problem. The "player" member is not set in the testRunConfiguration yet at this point, so testRunConfiguration.getPlayer() returns null. testRunConfiguration.setPlayer() is called in generateDefaults(). But generateDefaults() is not called until after validateSharedProperties() is called. So, if properties initialization could be improved here and I think this code will run more robustly.
I can work-around my issue temporarily by just setting a FLEX_HOME property in Ant. But I hope you will agree that the initialization issue with "player" still should be addressed. Would you like me to open a bug report, or is this thread enough?
Thanks,
Trevor

Flexunit 4.1 beta 1 ant task fails if SDK or project dir contains spaces

downloaded FlexUnit 4.1 beta 1 for its directory scanning and test loading support. found a problem - if either the SDK dir (e.g. C:\Program Files\Adobe\Adobe Flash Builder 4\sdks\4.0.0) or the project dir (e.g. C:\Documents and Settings\flexuser\My Documents\mike\Adobe Flash Builder 4\AntFlexUnit4.1betaSampleCIProject) contain spaces, the flexunit ant task will fail, as the following output indicates:
<snip>
[flexunit] '+flexlib'
[flexunit] 'C:\Program'
[flexunit] 'Files\Adobe\Adobe'
[flexunit] 'Flash'
[flexunit] 'Builder'
[flexunit] '4\sdks\4.0.0\frameworks'
[flexunit] '-output'
[flexunit] 'C:\Documents'
[flexunit] 'and'
[flexunit] 'Settings\flexuser\My'
[flexunit] 'Documents\mike\Adobe'
[flexunit] 'Flash'
[flexunit] 'Builder'
[flexunit] '4\AntFlexUnit4.1betaSampleCIProject\target\bin\TestRunner.swf'
<snip>
BUILD FAILED
C:\Documents and Settings\flexuser\My Documents\mike\Adobe Flash Builder 4\AntFlex
Unit4.1betaSampleCIProject\build.xml:72: Compilation failed:
command line: Error: default arguments may not be interspersed with other options
everything worked fine if i relocated both the SDK and project dir. unfortunately most of our developers use SDK and project directories with spaces.
what's the ETA for beta 2 ;-) ? anxious to integrate this excellent new feature once the spacing problem is resolved.
thanks.
-mike

@mike - Ok I've updated my fork @ http://github.com/blegros/flexunit with the fix. If you don't want to build from source, you can download the flexunit.zip file from my fork and just pull the Ant task out to use temporarily. You can find the artifact from my fork's build @ http://flexunit.digitalprimates.net:8080/view/Contributors/job/blegros/lastSuccessfulBuild /artifact/flexunit.zip.
Let me know if this works out for you.
-Brian

Why wlappc ANT task forces aways the generation of the EJB classes ?

I've got a problem with the ANT task "wlappc" witch interfaces Weblogic compilator.
In fact, I would like to execute the ebj compilation only when needed (if the deployment descriptor or a class changed for example).
It seems that this is the default behavior and the 'forcegeneration' option of the wlappc Ant task can change it (the doc is below).
forceGeneration :
Forces generation of EJB and JSP classes. Without this flag, the classes will not be regenerated unless a checksum indicates that it is necessary.
So I wrote :
<wlappc source="${descriptors}/CommandeEntities" output="${build}/CommandsEntities.jar" keepgenerated="true" verbose="true" forcegeneration="false">
<classpath refid="ejb.classpath"/>
</wlappc>
but I got the folowing result :
ejbjar:
[wlappc] Warning, output location exists H:\devWv2\wv2\build\CommandesEntities.jar
[wlappc] Created working directory: C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [VersionHelper] Recompiling because no previous hashes found
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Compliance Checker said bean was compliant
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Bean Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating source for ejb WCritereListeMulticritere
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generated the following sources for this EJB: [C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\WCritereListeMulticritere_u6449c_LocalHomeImpl.java, C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\WCritereListeMulticritere_u6449c_ELOImpl.java]
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Persistence Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Bean Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating source for ejb Document
[wlappc] 18 sept. 2008 11:23:00 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generated the following sources for this EJB: [C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\Document_6vm6yi_LocalHomeImpl.java, C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\Document_6vm6yi_ELOImpl.java]
[wlappc] 18 sept. 2008 11:23:02 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Persistence Sources
[wlappc] 18 sept. 2008 11:23:02 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Compiling EJB sources
[wlappc] Note: Some input files use unchecked or unsafe operations.
[wlappc] Note: Recompile with -Xlint:unchecked for details.
[wlappc] 18 sept. 2008 11:23:10 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Recompilation completed
[wlappc] 18 sept. 2008 11:23:10 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Rmic completed
[wlappc] Compilation completed successfully.
[jar] Updating jar: H:\devWv2\wv2\build\CommandesEntities.jar
BUILD SUCCESSFUL
All the classes witch hasn't changed has been checked and regenerated. The compliler says "Recompiling because no previous hashes found".
But why ? It could be besause it creates a different working directory each time I execute this ant task ? Is this working directory configurable ?
Would you have any idea of what's happening ?
Thanks.

You can find this in the 'org\apache\tools\ant\taskdefs\defaults.properties'
file of %wl-home%\server\lib\ant\ant.jar
--Sathish
<Michael Lee> wrote in message news:[email protected]..
I mean the definition of "wlappc" not the help for wlappc???thx.
i.e.
where can i find the sentence list below:
<taskdef name="wlappc" classname="weblogic.ant.taskdefs.j2ee.Appc"/>
I mean which files this "taskdef" is being in .

Change manifest file in existing EAR file with ANT task

Hi,
I use ant task (ojdeploy) to create EAR files from ADF application.
Now I want to add the application version number to MANIFEST.MF.
Is it possible to do the manifest file modification IN THE EXISTING EAR FILE (or while creating the EAR file with ojdeploy) with ant task or do I have to do the modification in the source MANIFEST.MF and after this create EAR file with ojdeploy?
BTW: I tried the <ear> task to create the EAR file instead of using ojdeploy but I was not able to find the needed deployment descriptor (appxml="application.xml") in my ADF appication.
regards
Peter

Hi Peter,
I don't know of a way to do it directly in ANT/ojdeploy. However, you could try exploding the EAR, updating the manifest, and recreating the EAR - cumbersome and slow, but it should work.
John

Passing extra compiler options to flexunit ANT task?

Hi,
Is there a way to send any extra compiler options to the <flexunit> ANT task?
I'm using conditional compilation and compilation (mxmlc) is failing from the <flexunit> task:
"Error: Access of undefined property DEBUG.
CONFIG::DEBUG {"
I tried sneaking "-define+=CONFIG::DEBUG,false" in with one of the other compiler options you can set on the <flexunit> task, but that just doesn't work or results in a validation error like this:
"One of the directories specified as a 'testSource' element does not exist."
Let me know if this is possible at all.
Thanks,
Wijnand

Hi Brian,
legrosb wrote:
@Wijnand - Sorry for the belated response.
Not late at all! I think a response within a day on a forum is quite fast!
legrosb wrote:
I thought I had captured this on the wiki, but it looks like I haven't, so thank you for the heads up.
I'll also update the wiki @ http://docs.flexunit.org/index.php?title=Ant_Task to be more detailed regarding compilation so other don't have to dig.
Did you just do an update on that Wiki page or did I completely miss the part that explained the <flexunit> parameters?
legrosb wrote:
In 4.2, which is super pre-alpha right now, I've added support to accept a series of flex-config.xml files provided by the user. Not sure if conditional compilation can be tackled with a custom flex-config.xml file, but if so then that'd be the feature that may help you.
Yes, being able to add (+=) a custom config file will solve this problem for me. You can define properties and values like this:
<flex-config>
 <compiler>
 <define>
 <name>CONFIG::DEBUG</name>
 <value>false</value>
 </define>
 </compiler>
<flex-config>
So in your AS code you can use:
CONFIG::DEBUG {
 // Do something that only should be done in debug mode.
I have another question, I ran into this one during testing my SWF with flexunit.
unittest.xml:82: java.util.concurrent.ExecutionException: command [<testcase classname='com.tuenti.video.unittest.testcase.player::MockPlayerCase' name='loadPlayer' time='0.000' status='success'/>] not understood
I had a look at the FlexUnitSocketThread.parseInboundMessages method that throws this error and it looks like that your defined END_OF_SUCCESS doesn't entirely match what the SWF is spitting out. They are of by 1 space: END_OF_SUCCESS is defined as: "status=\"success\" />", whereas my SWF spits out the following: "status='success'/>" (single quotes and no space before the closing of the tag).
It looks like I'm not the only one with the ExecutionException as it is reported on StackOverflow as well: http://stackoverflow.com/questions/3953677/flexunittasks-error-of-command-not-understood
Cheers,
Wijnand

How to generate not nillable complexType with ant task autotype

Hi all,
The file types.xml created by ant task autotype contains, among others, all element definitions of my java classes.
For testing purposes I have a simple class that holds (wraps) only a string. In the types.xml it is shown as followed:
<xsd:complexType name="StringHolder">
<xsd:sequence>
<xsd:element name="mystring"
type="xsd:string"
nillable="true"
minOccurs="1"
maxOccurs="1">
</xsd:element>
</xsd:sequence>
</xsd:complexType>
Somehow nullabel is always true, but I want to be false. Does anyone knows how?

Hello digitxm,
Since the hardware you have is the limiting factor, with the NI 6008 you can perform a software timed pwm output if timing in your application is not critical (your cycle time is in the seconds range and you do not mind some milliseconds of delay) you can use a digital output with software timing control for your PWM generation. Also, see how to use AO channel(s) to control the voltage level of a square wave output (period of the square wave can be varied). Otherwise, this can be accomplished by using the following example on generating a digital waveform using non-regeneration in order to update frequency and duty cycle on-the-fly using National Instruments M Series or X series DAQ devices.
Best regards,
Ali M
Applications Engineer
National Instruments
www.ni.com/support

Propagation Ant Tasks

Some known issues with the WebLogic Portal Propagation Ant tasks in 9.2 GA:
1. Some JARs need to be unpacked from library modules
Symptoms:
ClassNotFoundException when running ant tasks
Reference: CR290002
Solution:
See install guide for instructions
http://edocs/wlp/docs92/prodOps/scripts-using.html#wp1048812
2. The classpath for each task needs to be expanded
Symptoms:
Exceptions seen when running the ant tasks:
java.lang.NoClassDefFoundError: com/bea/xml/XmlException
NoClassDefFoundError
Reference: CR292993
Solution:
The classpath for tasks should appear as follows:
<pathelement location="${deploy.dir}/platform/lib/p13n/p13n_common.jar"/>
<pathelement location="${deploy.dir}/common/p13n/lib/p13n_prop.jar"/>
<pathelement location="${deploy.dir}/common/p13n/lib/p13n_prop_ant.jar"/>
<pathelement location="${deploy.dir}/portal/lib/content_prop.jar"/>
<pathelement location="${deploy.dir}/portal/lib/netuix/web/netuix_prop.jar"/>
<pathelement location="${deploy.dir}/server/lib/xbean.jar"/>
<pathelement location="${deploy.dir}/server/lib/api.jar"/>
3. Admin server should be running when Propagation Commit is invoked
Reference: CR273379
Solution:
The Admin Server should be running during a propagation commit. This enables
updates to the internal LDAP server to be properly distributed across
the cluster.
4. Content Type propagation will fail on Boolean properties with undefined default value
Symptoms:
A content type does not propagate
NullPointerException from XmlBeanTranslator.constructPropertyChoicesAsXmlBean
Reference: CR295866
Workaround:
Define a default value for the Boolean, true or false
5. OnlineMaintenanceModeTask does not implement Condition
Reference: CR293781
6. Global policies in policy file passed to offlineCombineTask are ignored
Symptoms:
Elections are always accepted even if global policy in file is set to 'N'
Reference: CR295985
Workaround:
Specify flags such as globalDeleteFlag="false" on the task.

No this is by design I think. For it to work, you have to specify the actual portlet definition from the library as a scope rule.
As a workaround which seems to work quite nicely, we used the XIP tool to get the XML version of the desktop tree. We then developed a small XSL transform to generate the scope file, based on the portlet definitions of the XIP output. This scope file contained all the relavent portlet definitions from the library.
So far, we haven't seen any major side affects, although that isn't to say there maybe something hidden.
Regards,
Jonathan

[svn] 4001: Adding support for asdoc in flex ant tasks

Revision: 4001 Author: [email protected] Date: 2008-11-03 13:46:13 -0800 (Mon, 03 Nov 2008) Log Message: ----------- Adding support for <asdoc> in flex ant tasks QE Notes: Tests need to be added to the flextasks test suite. Doc Notes: flex tasks documentation should be updated with example for <asdoc> task. Reviewer: Paul Bugs: SDK-9775 tests: checkintests Ticket Links: ------------ http://bugs.adobe.com/jira/browse/SDK-9775 Modified Paths: -------------- flex/sdk/trunk/modules/antTasks/flexTasks-internal.tasks flex/sdk/trunk/modules/antTasks/flexTasks.tasks Added Paths: ----------- flex/sdk/trunk/modules/antTasks/src/flex/ant/AsDocTask.java

You should use compiler.library-path to include libraries.
Try the following
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<project basedir="." default="build" name="Project_name">
<property environment="env"/>
<property name="FLEX_HOME" value="C:/Program Files/Flex 3.4"/>
<property name="APP_ROOT" value="./src"/>
<property name="Project_name.location" value="../Project_name"/>
<taskdef resource="flexTasks.tasks" classpath="${FLEX_HOME}/ant/lib/flexTasks.jar"/>
<target name="build">
<mxmlc file="${APP_ROOT}/AdminConsole.mxml">
<source-path path-element="${FLEX_HOME}/frameworks"/>
<compiler.library-path>
<include name="${Project_name.location}/src" />
</compiler.library-path>
</mxmlc>
</target>
</project>
Although, I don't know what are you planning to include, and whether you should use compiler.library-path for that.

Up-to-date check on genInterface ant task

I have been using the genInterface ant task to generate a java interface from a WSDL file. Works great, except that eventhough my wsdl file does not change it regenerates the interface every time and then since the java file got touched, forces a needless compile.
Is there anything I can do to stop this behavior? I would hate to not include the task in my standard build, that would stop the interface from getting regenerated when the WSDL actually got updated.
Thanks,
Greg

I just found that ANT has its own 'uptodate' check.
http://ant.apache.org/manual/CoreTasks/uptodate.html
...so I'll hold off on using XJC until it can support this.

JDeveloper Ant Task (10g)

Hi,
The download link for JDeveloper Ant Task in http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/130355.xml#uk.org.damselfly.jdev.ant does not work anymore.
Does anyone know where i can get the file jdev-ant-task-bundle.zip (http://www.oracle.com/technology/products/jdev/101/update/extensions/jdev-ant-task-bundle.zip)
Groeten,
HJH

Try taking a look at this page.
http://www.oracle.com/technetwork/developer-tools/jdev/index-094585.html
Hopefully it will get you going in the right direction.
--jb

Is there an ant task on FlexUnit to open browser with swf embedded?

Here is the same (unanswered) question asked by someone else: http://forums.adobe.com/thread/740495?tstart=0#740495
Basically I need to open my flex app in a browser window from ant, and the FlexUnit task apparently does not support this.
I have downloaded a sample from FlexMonkey. When they (sample writers) execute flexunit in this sample, one of the arguments to FU is "url". However, I can find no evidence of this version of FU (that uses that "url" argument) existing anywhere. Using the swf argument doesn't work as documented in the previous question above. So I don't know if my problem is Flex version, or it's just not supported by FlexUnit.
I'm using the Flex sdk 3.2.0 and the FU libraries below:
flexunit-4.1.0-33-as3_3.5.0.12683.swc
flexunit-4.1.0-33-flex_3.5.0.12683.swc
flexunit-cilistener-4.1.0-33-3.5.0.12683.swc
flexunit-uilistener-4.1.0-33-3.5.0.12683.swc
flexUnitTasks-4.1.0-33.jar
Please tell me if this issue has been solved and if so what libraries I need to implement it. If it is done for Flex 4.x, but not for Flex 3.2, perhaps you could guide me to the java source for the ant task for Flex 4.x so that I can implement this for Flex 3.2 or Flex 3.x.
thanks,
Phil

@Linden - Have not heard of this side effect from anyone as of yet, but good to know. Sounds like the file lock is coming from the Flash Player and causing the spawning process (rundll32.exe) to hang around as well. The FlexUnit team runs on Hudson using the FlexUnit Ant task, but we don't seem to encounter the same issue. What's the longest interval you've tried to use with the sleep task? Does the FP ever release its handle to the test SWF on your development machines?
Not sure this is a problem with the FlexUnit Ant task, but in 4.2 we could try to explicitly kill the rundll32 process since we'll have the PID when the task launches it. Head on over to JIRA and file a feature request for us and I'll see what I can do in the new year. In the short term though, maybe try upgrading your version of the stand alone debug flash player to see if that helps. Has anyone else seen this issue? Could you possible just move the clean target to be called before the xci-test target is run? Just some suggestions.
-Brian

Does new type of unit testing in Flash Builder4 support ANT task ?

Hi,
I am using the new way of creating unit tests following this page http://help.adobe.com/en_US/flashbuilder/using/WS27ECA937-059A-4308-A2E2-F3A3AAB64337.html #WSF04FE993-D0BA-4a2b-BDF1-8B8ABF22E448, which is really easier and more efficient than old ways.
But I then found that the old ANT task "flexunit" for running unit test not working any more. So if I want to get the results of unit testing from a CI server, how could I do now?
Thanks a lot
Michael

@Michael Lin89 - You can find information on using FlexUnit4 via Ant @ http://docs.flexunit.org/index.php?title=Ant_Task. There has been a lot of information collected on the wiki as well related to the CI process. You can see that info @ http://docs.flexunit.org/index.php?title=Continuous_Integration_Support. There are also an assortment of community projects built to work with FlexUnit which you can check out on the community page @ http://docs.flexunit.org/index.php?title=Community_Projects. There is also a sample project for working with CI, Ant, Maven, and a few other technologies @ http://docs.flexunit.org/index.php?title=CI_Sample_Project_Information.
Hope this helps to fill in the gaps as to what support we offer in terms of Ant and CI.
-Brian

Built-in wlst ant task does not work in weblogic 10.3.1

Hi,
We have an installer script that deploys an ear file to a weblogic managed server. The script also invokes the build-tin wlst ant task to bounce the managed server. However, in version 10.3.1 the wlst task seems to be broken. I get this error:
[echo] [wlst] sys-package-mgr: can't create package cache dir, '/u00/webadmin/product/10.3.1/WLS/wlserver_10.3/server/lib/weblogic.jar/./java
tmp/wlstTemp/packages'
[echo] [wlst] java.io.IOException: No such file or directory
[echo] [wlst] at java.io.UnixFileSystem.createFileExclusively(Native Method)
[echo] [wlst] at java.io.File.checkAndCreate(File.java:1704)
[echo] [wlst] at java.io.File.createTempFile(File.java:1792)
[echo] [wlst] at java.io.File.createTempFile(File.java:1828)
[echo] [wlst] at com.bea.plateng.domain.script.jython.WLST_offline.getWLSTOfflineInitFilePath(WLST_offline.java:240)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[echo] [wlst] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[echo] [wlst] at java.lang.reflect.Method.invoke(Method.java:597)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.getOfflineWLSTScriptPath(WLSTUtil.java:63)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.setupOffline(WLSTUtil.java:214)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:133)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:75)
[echo] [wlst] at weblogic.ant.taskdefs.management.WLSTTask.execute(WLSTTask.java:103)
[echo] [wlst] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
Obviously that is not a valid directory...so I am wondering what it is trying to do, and why. The wlst task worked perfectly in 10.3.0. No changes were made when attempting to run the script against 10.3.0 and 10.3.1, which tells me that something is different with the 10.3.1 setup. Here is the ant code I am running:
<target name="init-taskdefs">
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="ant-ext/ant-contrib.jar" />
</classpath>
</taskdef>
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy" />
<taskdef name="wlst" classname="weblogic.ant.taskdefs.management.WLSTTask" />
</target>
<macrodef name="wlShutdownServer">
<attribute name="adminUser" default="${deploy.admin.username}" />
<attribute name="adminPassword" default="${deploy.admin.password}" />
<attribute name="adminUrl" default="${deploy.admin.url}" />
<attribute name="serverTarget" />
<sequential>
<trycatch property="server.error">
<try>
<wlst failonerror="true"
arguments="@{adminUser} @{adminPassword} @{adminUrl} @{serverTarget}">
<script>
adminUser=sys.argv[0]
adminPassword=sys.argv[1]
adminUrl=sys.argv[2]
serverTarget=sys.argv[3]
connect(adminUser,adminPassword,adminUrl)
target=getMBean("/Servers/"+serverTarget)
if target == None:
target=getMBean("/Clusters/"+serverTarget)
type="Cluster"
else:
type="Server"
print 'Shutting down '+serverTarget+'...'
shutdown(serverTarget,type,'true',15,force='true')
print serverTarget+' was shut down successfully.'
</script>
</wlst>

<echo message="Deleting any lok files that have not been removed..." />
<delete failonerror="false">
<fileset dir="${env.DOMAIN_HOME}/servers/@{serverTarget}" includes="**/*.lok"/>
</delete>
</try>
<catch>
<fail message="@{serverTarget} shutdown failed. ${server.error}" />
</catch>
<finally/>
</trycatch>
</sequential>
</macrodef>
Any help would be appreciated. Thanks!

Well, it looks like passing something like "-Djava.io.tmpdir=/var/tmp/javatmp/`date +%Y%m%d`" to ant did the trick. I had to make sure that directory existed first, otherwise it threw a java ioexception.
I still don't understand what changes between 10.3.0 and 10.3.1 to necessitate this change.

Updates to Ant task

Similar Messages

Maybe you are looking for