It must be something specific to WinZIP. My 1.5.2 jars/wars/zip all
deploy fine, can be read with numerous zip reading programs, including
the built-in zip file support on Windows XP. I don't even have winZIP
installed, but I would be happy to get it and test if necessary.
Zip-file readers that
I'd be interested in it, although I am a firm believer in maintaining
compatibility with old-style get. A question for the Ant Powers That
Be:
What's the recommended way to do this sort of migration? Create a new
task that's similar to the old but includes the enhancements, or add
options to the
I do it with one line in my build.xml:
test todir=${junit.results} name=${testcase} if=testcase/
and a small change to the batchtest task:
batchtest todir=${junit.results} unless=testcase
Both of these in are my test target, so I just run ant with
ant -Dtestcase=com.whatever.TestWhatever test
Workspace needs to be a name as defined by PVCS, not a filesystem
location. For example /@/Public/Dev. PVCS will use the workfile
location set for the workspace for the files.
This should probably go to the ant-users list, though.
s
-Original Message-
From: Pothula,
Sorry to hear of your problems.
As one of the current contributors to the PVCS task let me
assure you that it does work, we use it extensively every
day at my employer. If you have not already taken it to the
ant users list I encourage you to take it there. I have not
been monitoring that list
