That sounds ideal! Cheers!
-Original Message-
From: Scott Hernandez [mailto:[EMAIL PROTECTED]
Sent: 05 March 2004 18:55
To: [EMAIL PROTECTED]
Subject: Re: [Nant-users] Double expansion of property names?
Pete,
Using the new expression support that is the nightly builds,
Title: Message
Peter,
Can you please try using the solution task
again with the latest nightly build ?
I made a lot of improvements over the weekend, but
please send me a zip file containing a repro if its still not working. I'm
really committed to fixing this !
Gert
- Original
Hi,
Thanks Jason the Copy task worked a
treat.
Although I am not there yet I am interested to
know how you guys are doing your final
deployment builds, Nant or VS?
Although slightly off topic for this form I think,
I am
interested to hear about yor experiences for say
For example,
client
Hello,
Within our project, we rely heavily on the use of the NDoc task to keep our
project
(source code) documentation up-to-date.
When we apply this within our build cycle while being online (logged user
runs the
NAnt project/task tree), it all works just fine with the expected results.
On
Hi,
I'm just asking to get an idea of how many people actually use it, but how
would you feel if we would remove WebDAV support from the solution task ?
We've noticed that lots of people have problems configuring their webserver,
in order to get the solution task working, so it might be better
I haven't used WebDAV, but if I could use it to distribute a website to a final
server, it would be very very useful to me. At the moment, I have a manual FTP step is
required to move a web project to the production server.
Erick
-Original Message-
From: [EMAIL PROTECTED]
Perhaps we could have a webdav-copy task instead that would be similar to
copy but accept WebDAV sources/targets.
+1 for the idea of removing WebDAV from the solution task.
Jarek
- Original Message -
From: Erick Thompson [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]; NAnt Users
The latest stuff has the EnableWebDAV stuff to prevent it being used by
default. It's been in there for a month or so and tells the user to
either provide a webmap or set EnableWebDAV = true to make it work.
-1 for removing it - if people want it, they can be pointed at
documentation to set
On second thought, it may be beneficial to break out the WebDAV stuff
into a separate webdav-* task.
I'm not sure if people are relying on being able to build code via
WebDAV shares, however. Perhaps the solution task could use WebDAV via
the alternate task, rather than the internal WebDAV
+1 on WebDAV tasks. This is something that will be more and more useful in
the future. It sounds like a lot of new server projects are providing webdav
file access.
In fact, I believe one of the deployment options for Subversion is via
webdav. This would really simplify the requirements to do a
10 matches
Mail list logo
