FYI.. Kindly help
Thanks & Regards
Vinod Soni
Enterprise Architecture (Humana)
Desk: +91-120-4398818
Mobile:+91-989969
- Forwarded by Vinod Soni/Non Employee/Humana on 02/15/2011 06:56 AM
-
Vinod Soni/Non Employee/Humana
02/15/2011 06:52 AM
To
nant-developers@lists.sourceforge.net
nant-developers@lists.sourceforge.net
Subject: RE: [nant-dev] FW: System.Data.OracleClient assembly no longer
resolved(different behaviour 0.85 v 0.86b1)
Eric,
For .NET, we now use an explicit set of assemblies that we can automatically
resolve to a full path.
This set can be configured in the NAnt.exe.config fi
complete now.
Gert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erik
Renes
Sent: woensdag 16 april 2008 18:33
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] FW: System.Data.OracleClient assembly no longer
resolved(different behaviour 0.85 v
Hi all,
When upgrading Nant to the latest version today, I noticed that a lot of my
previously working build scripts were failing. Compile errors arose from the
fact that System.Data.OracleClient.dll wasn't referenced.
Further investigation showed that nant 0.85 resolves the following:
Hi All,
Is the Wiki link on http://nant.sourceforge.net/ broken?
Can't get to it. Get the following error:
lib/WikiDB/backend/PearDB.php:32: Fatal[256]: Can't connect to
database: wikidb_backend_mysql: fatal database error
DB Error: connect failed
( [nativecode=Unknown MySQL S
Hello,
strangly, it do even for me, when clicked on that url directly. It works,
when I copy&paste it into mine IE. No idea why. This freeweb is rather
buggy, it seems. Unfortunatelly, maillist refuse to accept .zips >40kB.
Sorry for inconvenience.
Otherwise, I'm glad you want to try out this s
Gary Feldman a écrit :
This looks like a good idea, but could be difficult to do generally
across all tasks.
In the meantime, a simple approach that works today is to duplicate the
task invocation with if/unless attributes, and use a property to
indicate which to do:
In the setup targets:
On 4/22/05, Ian MacLean <[EMAIL PROTECTED]> wrote:
somthing like this could be a good solution. Another possibility is tohave a way to set an attributes value such that its equivalent to it notbeing set - somthing like null for attributes. For example;
I guess the _expression_ help page for
Troy Laurin wrote:
Anyway, I might have a play with it over the next few weeks, and if I
don't find any nasty side-effects with targets or other elements, then
I'll submit it as a patch post-0.85.
PS- no offense, but some of the code to initialise the project and
process the build file could us
On 4/21/05, Gary Feldman <[EMAIL PROTECTED]> wrote:
This looks like a good idea, but could be difficult to do generallyacross all tasks.
I think there is a way to do it, but it is a little more complicated
than I like... Basically the NAnt.Core.Element class could be
extended with late binding att
Hi
I usually leave the doc generation always enabled. I just switch
off/on the ndoc call.
Thibaut
2005/4/21, Gary Feldman <[EMAIL PROTECTED]>:
> Troy Laurin wrote:
>
> > Just a pie-in-the-sky (whatever that means)...
> >
> > These kind of issues aren't all that uncommon in builds... how
> > fea
Troy Laurin wrote:
Just a pie-in-the-sky (whatever that means)...
These kind of issues aren't all that uncommon in builds... how
feasible is a meta-element that can be nested under any
element and decorates it with an attribute. If the
meta-element supported if/unless and lazy property evalua
Just a pie-in-the-sky (whatever that means)...
These kind of issues aren't all that uncommon in builds... how feasible
is a meta-element that can be nested under any
element and decorates it with an attribute. If the
meta-element supported if/unless and lazy property
evaluation, then it could b
nant-developers@lists.sourceforge.netSubject: [nant-dev] FW:
task
Hi
!
I am new with that
mailing list.
However did you
notice my message? Did I sent to the correct address?
Thanks
Ynon
-Original
Message-From: Ynon
Koralek [mailto:[EMAIL PROT
Title: FW: bug report
Sorry, I find reason, I just thing what something wrong in contrib libory, but it is another Task lib
_
From: Andrejs Mamontovs
Sent: Wednesday, December 08, 2004 12:35 PM
To: '[EMAIL PROTECTED]'
Subject: bug report
Hello,
30
> To: [EMAIL PROTECTED]
> Subject: [nant-dev] FW: Build Failure
>
> Hi,
> I have a project that references Visio Type library.
> I'm using the tag so that my solution and build
> files are always in sync. However, the build is failing with
> the following erro
Hi,
I have a project that references Visio Type library. I'm using the
tag so that my solution and build files are always in sync. However,
the build is failing with the following error
System.ApplicationException: Couldn't find reference to type library 'Visio'
(TYPELIB\{00021A98-
Hi Jeremy,
Can you try using NAnt 0.85 RC1 ?
Thanks,
Gert
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jeremy Owens-BoggsSent: maandag 29 november 2004
16:11To: [EMAIL PROTECTED]Subject:
[nant-dev] FW:
From: Jeremy Boggs Sent
From: Jeremy Boggs Sent: Monday,
November 29, 2004 7:57 AMTo:
'[EMAIL PROTECTED]'Subject: Solution task blows
up on tlbimport
The solution
task is blowing up on a tlbimport. Attached is a copy of the project that
exhibits this behavior, and a copy of the output. The project file i
Jim,
I was hoping you would say that :-)
John
>I looked at the msi/msm tasks (to build installs for NAnt/NAntContrib) a
>couple days ago and saw that they were broken... I'll take a better look
>and fix them hopefully this week. I agree that having a working install of
>NAnt would be a good t
I looked at the msi/msm tasks (to build installs for NAnt/NAntContrib) a
couple days ago and saw that they were broken... I'll take a better look
and fix them hopefully this week. I agree that having a working install of
NAnt would be a good thing.
>
> One thing that I would really like to have
t familiar with NAnt and it's nuances.
Another opinion...
John Cole
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of James
Geurts
Sent: Saturday, June 05, 2004 10:54 AM
To: [EMAIL PROTECTED]
Subject: [nant-dev] FW: 0.85 release
Hi all,
I haven't b
Hi all,
I havent been watching this list (I just subscribed), but looking through
the archives shows that this hasnt been brought up for a little while. Im
thinking that we should push a 0.85 release out the door. It has been over
5 months since the last release, and I generally think that a
Title: RE: [nant-dev] FW: cvs-checkout bug
AbstrackSourceControl refers to UpdateTask.CommandName. I'm not sure whether it should be that way. I guess it can be refactored but not necessary.
Nat
-Original Message-
From: Clayton Harbour [mailto:[EMAIL PROTECTED]]
Sent: Wedn
: Nat Luengnaruemitchai [mailto:[EMAIL PROTECTED]
Sent: Wed 5/26/2004 7:19 AM
To: Clayton Harbour
Cc: [EMAIL PROTECTED]
Subject:RE: [nant-dev] FW: cvs-checkout bug
AbstrackSourceControl refers to UpdateTask.CommandName. I'm not sure whether
it should be that way. I guess i
PROTECTED]
Sent: Tue 5/25/2004 7:43 AM
To: [EMAIL PROTECTED]
Cc:
Subject:[nant-dev] FW: cvs-checkout bug
In CheckoutTask.cs under /src/NAnt.SourceControl,
line 81: public const string CvsCommandName = "update";
should be
line 81: public const string CvsC
In CheckoutTask.cs under
/src/NAnt.SourceControl,
line 81:
public const string CvsCommandName =
"update";
should
be
line 81:
public const string CvsCommandName =
"checkout";
Otherwise, the code
will not be checked out properly.
In addition to
that, I guess that the
I forwarded this to the nant dev list ...
Please avoid sending these mails directly to me ..
Thanks
Gert
- Original Message -
From: "Tom Whitner (Fidelity)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, May 12, 2004 7:44 PM
Subject: Contributing n
t: Wednesday, April 21, 2004 12:56 AM
Subject: [nant-dev] FW: Compile error
>
> Fyi, I found the problem. My project has a gac reference. It appears
> that when parsing the projects, the assumption is made if it is in the
> gac to find it in the framework directory, which is not wher
Title: FW: Compile error
Fyi, I found the problem. My project has a gac reference. It appears that when parsing the projects, the assumption is made if it is in the gac to find it in the framework directory, which is not where this dll is located.
Here is the code that fails.
DirectoryInf
That works. I'd rather specifiy the namespace at the class level though.
Ian
In that case I should check when I'm scanning for methods that they are
all lowercase - or we can just map a lowercase name to the correct
methodinfo object. So even if you define the method in code as
void SomeFunc()
> In that case I should check when I'm scanning for methods that they are
> all lowercase - or we can just map a lowercase name to the correct
> methodinfo object. So even if you define the method in code as
>
> void SomeFunc()
>
> it will be mapped to the nant custom function somefunc() and attem
In that case I should check when I'm scanning for methods that they are
all lowercase - or we can just map a lowercase name to the correct
methodinfo object. So even if you define the method in code as
void SomeFunc()
it will be mapped to the nant custom function somefunc() and attempting
to
> Do you think the functions need to be defined as static ? I was thinking
> of making them public instance and passing a Project instance to the
> containing objects constructor so that functions can have access to
> various information inside the project - the same as tasks can now. It
> might be
> user to specify it. I'm allowing functions to be imported from the same
> assemblies that are currently scanned for tasks ie those in the nant bin
> dir. Then any extra libs can be added using somthing like the
> task you describe below. Maybe could
> override namespace defined with the attribu
Jarek,
What does your "custom function loading code" do?
I presume that you want to load functions from external dlls and make them
available to EE.
thats correct. It scans assemblies looking for classes marked with a
special attribute - then loads MethodInfo objects from those classes
into a
-- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, December 08, 2003 9:35 AM
Subject: Re: [nant-dev] Fw: Expression evaluator changes
> Awesome, thanks !
>
Awesome, thanks !
Ian
Jaroslaw Kowalski wrote:
OK. Committed.
Jarek
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, December 08, 2003 9:23 AM
Subject: R
OK. Committed.
Jarek
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, December 08, 2003 9:23 AM
Subject: Re: [nant-dev] Fw: Expression evaluator changes
Could you just commit to the branch ? I'd like to merge these changes
with my custom function loading code.
Ian
As my previous e-mail bounced because it was too big (41 KB > 40KB limit!)
I'm resending this to the list without the patch.
Again, I encourage everyone to download and try "test2" and
As my previous e-mail bounced because it was too big (41 KB > 40KB limit!)
I'm resending this to the list without the patch.
Again, I encourage everyone to download and try "test2" and share your
opinion.
Jarek
- Original Message -
From: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
To: <[EMA
Title: solution stuff
hi - we are trying to get our solution to build by
nAnt - actually we are not successful -> there seems to be something missing
- we reference a COM dll (BAWPublicV5) and solution task produces follwoing
error:
* using nant-20031028.zip nighlty build
any hints ?
gree
Please see the note below. Does anyone know if there are plans to
upgrade from version 2.1.3 to 2.1.4 for the release?
Also, is there a problem with the list or does everyone just need to
sign up to post in order to control spam? The reason I am asking is
John seemed to have an issue with his e
These should be fixed in cvs now.
Thanks !
Gert
- Original Message -
From: "Martin Aliger" <[EMAIL PROTECTED]>
To: "! nant" <[EMAIL PROTECTED]>
Sent: Monday, August 25, 2003 10:46 AM
Subject: [nant-dev] Fw: two more problems in Solution task (path relate
Hi again,
I found two more thinks:
1/ "csc @temp-path\commands.txt" do not start propertly, when temp-path is
in "x:\documents and settings" becouse of spaces in path
2/ when extra output files are copied and source and dest is in same path -
source is deleted! (I change smthing in /doc stuff, bu
I’m having this problem when attempting
to run a test build of one of our .NET solution files. Do you have any ideas about what could
be causing the problem?
D:\Downloads\NAnt\nant-0.8.3-rc2\nant-0.8.3-rc2\bin>nant
NAnt version 0.8.3
Copyright (C) 2001-2003 Gerry Shaw
http://nant.sou
(cross posted between nant-dev and nantcontrib-dev)
Erv Walter wrote on nant-dev:
NAntContrib is mostly useless if a person can't find a version that
matches their version of NAnt. At a minimum, we should strive to
release a version of NAntContrib that works with NAnt 0.8.3 and we
should do so n
xt build and so forth.
Jason
-Original Message-
From: John Barstow [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2003 3:57 PM
To: 'Gert Driesen'; 'Nant-Developers (E-mail)'
Cc: 'Ian MacLean'
Subject: RE: Upcoming 0.8.4? release (was RE: [nant-dev] FW:
Mike Roberts:
>There's been discussion of this on nantcontrib-dev this week
Out of curiosity, does anyone have an idea of how much overlap there is
between the two lists?
(I am on both, and so I have been seeing this discussion in both forums)
I ask, because if (as I suspect) most everyone t
Ian MacLean <[EMAIL PROTECTED]> wrote:
>Gert Driesen wrote:
>
>>John,
>>
>>We should .. euhm .. could ... (never say should, if there's a slight chance
>>that Ian is gonna read the mail .. LOL) also move to a fixed version number
>>for rel
One common practice (recommend by Microsoft gurus) is to increment your
version number immediately _after_ a release, not right before a
release. This means that you have plenty of time to debug any issues
related to that version number change. I assume that's why the version
is 0.8.3 in CVS righ
I like this idea. It keeps momentum going - ie regular releases. And we
don't get in the "just one more feature" situation.
Ian
Matt:
Is it alright to do a couple of pre-0.8.3 builds before the real one (at
least one)?
In light of this, and Gert's request to fit more features in before
Erv Walter wrote:
> It seems kind of odd to suggest that the next version of NAnt
> should be 0.8.4, doesn't it? The newest release version is 0.8.2, why
> are we skipping 0.8.3?
It's mainly because the CVS version has been marked as 0.8.3 for quite some
time now, and it would be clearer to incr
<[EMAIL PROTECTED]>, "'Nant-Developers
(E-mail)'"
><[EMAIL PROTECTED]>
>CC: 'Ian MacLean' <[EMAIL PROTECTED]>
>Subject: RE: Upcoming 0.8.4? release (was RE: [nant-dev] FW: Upcoming
0.8.3
>release)
>Date: Fri, 27 Jun 2003 10:57:28 +120
27; <[EMAIL PROTECTED]>, "'Nant-Developers (E-mail)'"
<[EMAIL PROTECTED]>
CC: 'Ian MacLean' <[EMAIL PROTECTED]>
Subject: RE: Upcoming 0.8.4? release (was RE: [nant-dev] FW: Upcoming 0.8.3
release)
Date: Fri, 27 Jun 2003 10:57:28 +1200
Lots of comme
Lots of commentary last night. Here are my responses in no particular
order.
> I would still like to get a few things in the 0.8.3 release : upgrade
to a
> new version of #cvslib, perhaps upgrade to a yet-to-be-released
version of
> log4net (which now uses the same assembly name for all framework
Matt:
>Is it alright to do a couple of pre-0.8.3 builds before the real one (at
>least one)?
In light of this, and Gert's request to fit more features in before
releasing, I wonder if NAnt might not benefit from doing time-boxed,
instead of feature-boxed releases. If the project were to releas
Is it alright to do a couple of pre-0.8.3 builds before the real one (at
least one)?
I found that for the last release, people are more likely to test and
send bug reports for a pre- build than a development build.
Matt.
John Barstow wrote:
I'm hoping to do an 0.8.3 release sometime next we
I'll just ignore that part of that directed at me. Yep we *should* use a
fixed version number. Thats part of the reason we moved to a common
assemblyinfo.cs file in the first place isn't it ?
It was intended as a joke, but you know that right ...
yeah - I figured.
Ian
---
Gert Driesen wrote:
John,
We should .. euhm .. could ... (never say should, if there's a slight chance
that Ian is gonna read the mail .. LOL) also move to a fixed version number
for releases, now that all assemblies are built using a common
assemblyinfo.cs file.
I'll just ignore that part of tha
inion. Ian, what do you suggest ?
"should" we do this ?
Gert
- Original Message -
From: "John Barstow" <[EMAIL PROTECTED]>
To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]>
Sent: Thursday, June 26, 2003 7:14 AM
Subject: [nant-dev] FW: Upcomin
CTED]>
Sent: Thursday, June 26, 2003 7:14 AM
Subject: [nant-dev] FW: Upcoming 0.8.3 release
> I'm hoping to do an 0.8.3 release sometime next weekend. Before we can
> release, however, we'll need a clean build.
> The following tests FAIL when attempting to build from the latest CVS
I'm hoping to do an 0.8.3 release sometime next weekend. Before we can
release, however, we'll need a clean build.
The following tests FAIL when attempting to build from the latest CVS.
If no-one fixes them before I wake up, I'll probably send in a patch or
two. Note that they're ALL failing on t
John,
You are right - a release is due soonish.
I can't seem to build the latest nant-contrib. It errors out looking
for a tools folder.
Futhermore, copying the prebuilt binaries to my nant directory and
attempting to use the or task fails; it claims
'unknown task'.
There has been some discussio
I can't seem to build the latest nant-contrib. It errors out looking
for a tools folder.
Futhermore, copying the prebuilt binaries to my nant directory and
attempting to use the or task fails; it claims
'unknown task'.
Isn't it about time for a 0.8.3 release, BTW? 0.8.2 has some known bugs
tha
Title: Message
Hi Nanters
Here goes...
Pat
-Original Message-From: Turpin, Jay
[mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04, 2003
18:13To: Patrice CalvéSubject: RE: [nunit-developer] Nunit
2.0 and Nant
You
may want to repost this to [EMAIL PROTECTED] instead.
I know th
Brian you should send this stuff to the nant-dev list (see nant.sf.net
for a link). I haven't had any time to actually touch the code in the
last couple of weeks but maybe somebody else with CVS access will patch
these in.
>From the sounds of things the BuildServer project is going to be
replace
OTECTED]
[mailto:nant-developers-
> [EMAIL PROTECTED]] On Behalf Of Gerry Shaw
> Sent: Monday, June 24, 2002 10:35 PM
> To: [EMAIL PROTECTED]
> Subject: [nant-dev] FW: NAntTask Patch
>
> What do people think of this? IMO the neseted properties for the nant
> task seems to fall into
What do people think of this? IMO the neseted properties for the nant
task seems to fall into line with the concept of Tomas's optionset idea.
-Original Message-
From: Mark Griffiths [mailto:[EMAIL PROTECTED]]
Sent: Mon, June 24, 2002 2:32 AM
To: Gerry Shaw
Subject: RE: NAntTask Patch
69 matches
Mail list logo
