It will output a warning if it's still used, and will continue to actually
use it for now.
- Original Message -
From: "Bernard Vander Beken" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>; "Nant-Developers (E-Mail)"
<[EMAIL PROTECTED]>
Sent: Thursday, July 03, 2003 8:45 AM
Sub
Hello,
To be consistent, this would be a useful change.
Maybe NAnt should output a warning if the nant.failure task is still
found after this change.
Best regards,
Bernard
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 03, 2003 8:29 AM
To: Nant-D
further 2 cents:
1) thanks for biting the bullet, very much!
2) does it make sense that nantcontrib ends up in a single dll as
opposed to several dlls, smaller, per task set? seems to me it might
complicate the configuration a little bit more, but would yield easier
to handle subproject (eg: if o
I think you are on to something here. I only use NAnt right now to build
release candidate code so don't have the need for multi configuration
builds, but your idea is certainly good.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jaroslaw
Kowalski
Sent: Sa
Nick
I send you both files for the task. Just tested them with
latest version of NAnt and NAntContrib from cvs and they compile and
works.
committed. Please be aware of the whitespace and formatting standards
for nant -
http://sourceforge.net/docman/display_doc.php?docid=6080&group_id=31650
John Barstow wrote:
On a related note, I do have the tests building cleanly (and am thus happy
to branch) but do not have all the tests passing. Ian, can you tell me how
you got this to pass?
did you sync NAntCOntrib.build ? TlbImpTask has a dependency on
DotnetTasks.dll which wasn't being co
Hi Ian,
I send you both files for the task. Just tested them with latest
version of NAnt and NAntContrib from cvs and they compile and works.
It should find them there. Are you running nant from
\build\nant-0.8.3-debug\bin and does the nant.exe.config in that directory
contain :
defau
Can someone with CVS write access create a branch for the upcoming 0.8.3
release? Ian says he has the project building and testing cleanly, so now
is a good time to branch.
The command is:
cvs tag -b BRANCH-083
After running the command, you will still be on the main branch and people
can start
Phillippe: I've checked in a fix that allows you to generate VB
resources from the WinForms projects. As far as I can tell, it
generates identical resource filenames to VS.NET's.
I can send you a pre-compiled solution task if you'd like - it may work
within your NAnt installation.
Matthew Mas
Someone posted a patch for this item earlier... I don't know if it was
ever applied. I can look and make sure it's in CVS.
Philippe Lavoie wrote:
That did the trick, I added vbc (by contract, not choice) to the path
and now it got a lot further. However, now it's stuck with the following
which
That did the trick, I added vbc (by contract, not choice) to the path
and now it got a lot further. However, now it's stuck with the following
which I hope is now fixed inside CVS (except that I can't compile CVS...
)
Web_IClicWeb.vbproj\Global.asax.resx
Total time: 0 seconds.
BUILD FAILED
INTER
Is CSC.EXE in your path while running NAnt?
I'm hoping one day to add a web path mapping property to the solution
task. Right now it has a very basic set of error-prone WebDAV methods to
handle compiling of a web project that is usually on the build server
anyways. It also tries to use the cred
I have nant from a daily build installed (2003-06-21) and I
try to build nant (cvs version) from it, I get the following result
[exec]
C:\Projects\3rdParty\nant-cvs/build/nant-0.8.3-debug/bin/NAnt.exe
buildfile:NAnt.build debug self-test -D:project.version=0.8.3
-k:net-1.1
I wanted to use slingshot and for some reason it would load
(and it doesn’t work with VS 2003 anyway). Then, I noticed that the
solution might be the way to go.
I added a simple solution task to my build system
The first time I was
Johnny Bowtie wrote:
Please don't commit to NAntContrib until that is also branched; that
should happen tomorrow as Ian has explained how to compile the tests.
and the tests are passing cleanly now - for me anyway.
Ian
---
This SF.Net emai
Hi,
I have still been working towards setting up cruise control, although it
sounds like this is a temporary solution until the build can be migrated
to ThoughtWorks. In the end I think this migration will be a more
stable solution.
In any case, here is the **temporary** url:
http://cc
On Thu, 2003-07-03 at 05:38, Gert Driesen wrote:
> Apparently, for previous releases a branch was make named rel- number> eg. rel-0-8-3
>
> perhaps we should use the same naming scheme for the 0.8.3 branch ...
>
I intend to use the rel-0-8-3 tag for the final 0.8.3 release; I may
have misundersto
On Thu, 2003-07-03 at 04:13, Gert Driesen wrote:
> I forgot : I'll increment the version number later today ...
>
> what version number do you recommend, 0.8.4. ?
>
> what was actually decided after the discussion on this subject ?
>
0.8.4.xxx for the main branch. Typically, the suggestion
Apparently, for previous releases a branch was make named rel- eg. rel-0-8-3
perhaps we should use the same naming scheme for the 0.8.3 branch ...
Can we start committing to the main branch now ?
Gert
- Original Message -
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "John Barstow" <[EM
rather than comment out that reference try building with :
nant -D:nant.dir=C:\cvs\nant\build\nant-0.8.3-debug
if you've just built a new NAnt from source then
C:\cvs\nant\build\nant-0.8.3-debug\bin\ will contain
NAnt.Core.Tests.dll, satisfying the reference.
Ian
Ian MacLean writes:
they are
+1
Good idea.
I'll wait until after the 0.8.3 branch has been made before committing it to
the main branch.
Gert
- Original Message -
From: "Bernard Vander Beken" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>; "Nant-Developers (E-Mail)"
<[EMAIL PROTECTED]>
Sent: Thursday, J
sorry for the confusion but :
we decided to keep the tasks in NAntcontrib for now and
move a bunch of them into nant - post 0.83 release - see the 'Namespaces
and NAnt.Cnntrib tasks' post for details on what tasks will go where.
but don't worry the bullet remains bitten. I've rolled the changes
I forgot : I'll increment the version number later today ...
what version number do you recommend, 0.8.4. ?
what was actually decided after the discussion on this subject ?
John, will you assign a fixed (0.8.3.x) version number to the 0.8.3
branch before building the release ?
will you
Hi John,
I've created a branch and named it BRANCH-083, as a tag has to start
with a letter and cannot contain dots.
Gert
On Thu, 2003-07-03 at 03:46, John Barstow wrote:
> Now that we have a cleanly building code base, can someone with CVS write
> access create a branch for the 0.8.3 release?
>
Good idea.
I'll wait until after the 0.8.3 branch has been made before committing it to
the main branch.
Gert
- Original Message -
From: "Bernard Vander Beken" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>; "Nant-Developers (E-Mail)"
<[EMAIL PROTECTED]>
Sent: Thursday, July
25 matches
Mail list logo
