[CACTUS-79] cactus task doesn't delete old webapp if tmpdir is specified on tomcat5x

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5
• Fix Version/s: 1.6
• Component/s: Ant Integration
• Environment: Operating System: Windows XP; Platform: PC
• Bugzilla Id: 25034
• Assignee: Vincent Massol
• Reporter: Daniel Rabe
• Created: 27/Nov/03 05:39
• Updated: 17/Apr/04 15:42
• Resolved: 17/Apr/04 15:42

Description

I have an ant script that runs cactus against a tomcat5x container. By default,
the cactus was is deployed to a system temp directory. When I run this task
more than once, I usually see lines like this, indicating that cactus is
cleaning up the previous webapp:

[cactus] Deleting 1089 files from C:\DOCUME~1\Drabe\LOCALS~1
\Temp\cactus\tomcat5x
[cactus] Deleted 295 directories from C:\DOCUME~1\Drabe\LOCALS~1
\Temp\cactus\tomcat5x

The tomcat5x container allows you to specify your own temp directory. I specify
mine as <tomcat5x ... tmpdir="c:\temp"/>. When I execute it this way, it
creates c:\temp\webapps, and puts my war file in there. When I re-run the
cactus task, it copies over a new war file, but does NOT delete the previously
exploded webapp. Therefore, it ends up executing an old version of the webapp.

I don't see any reason why the behavior should be different if I specify my own
tmpdir. I would expect the old webapp to be deleted when the new war file is
copied over.