To be more precise, I am using Ant to call compiled perl scripts. When a a script is called which verifies that you are in a view, for some reason it does
not think it is in a view on NT3.5.1. If you have a view
mapped to a logical drive and run ant:
G:\>ant -buildfile foo.xml
...the code dies and states that you are not in a view.
This works fine on W2K and all UNIX/Linux flavors. | [reply]
[d/l] |
My point was that NT 3.5.1 was at best, a barely supported (by MS) platform. It pre-dated Java anything by a looong way, and was rapidly and totally superceded by NT4. I am amazed that anyone is still using it as it had no merits over NT4 and many, many downsides and caveats. I don't know for sure, but I doubt that you would be able to get any support from MS for this outdated and superceded product.
You are describing your problem in terms of a Java-based product, running on a very old platform. You are not describing anything that can be directly (nor even indirectly) attributed to Perl. This is a Perl related site.
What makes you think that the problem is a Perl problem and not an ant or java-runtime or java virtual machine or java compiler or NT3.5.1 one?
Have you tried running the perl commands individually from outside of ant? Do they work from the command line via the logical drive?
Have you tried substituting a non-perl command located on the logical drive in place of the perl scripts? Are they invoked correctly via ant on NT3.5.1?
As I said, the specific problem you describe is "you are not in a view". This is not a Perl error! Wouldn't the Ant/java/Jakarta project support/discussion forums be a better place to be asking?
Well It's better than the Abottoire, but Yorkshire!
| [reply]
[d/l] |
I solved the problem. It was a combination
of Perl, Ant, and XML. The value I was passing
in Ant/XML was being used for the Perl call. That
made Perl think it was elsewhere than the drive
mapped to the view when the `$CT pwv -s` check
was made.
Thanks for your help :)
-P0w3rK!d
| [reply] |