[NAnt-users] non-readonly properties

2012-02-22 Thread Chris Fouts
I have the following properties defined in mynant.build file
!-- Use these Bools for enable either Project1 and/or Project2 
builds --
property name=enable_project1_build value=true 
readonly=false /
property name=enable_project2_build value=true 
readonly=false /

But when I run script where I override the defined properties, e.g.,
C:\ nant mynant.build -D:enable_project1_build=false

I get...
Read-only property enable_project1_build cannot be overwritten.

I do echo the values for testing, I get the correct value, so should I just 
ignore the noise?

-chris



***This e-mail message is intended only for the above named recipient(s)
and may contain information that is sensitive or proprietary. If you have
received this message in error or are not the named recipient(s), please 
immediately notify the sender, delete this e-mail message without making
a copy and do not disclose or relay this e-mail message to anyone.***
--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users


Re: [NAnt-users] non-readonly properties

2012-02-22 Thread Bob Archer
Properties set on the command line are always read-only.

If you want to not reset a property value if it was set from the command line 
you can use overwrite=false.

Also, when you pass false from the command line you don't need to quote it.

BOb


From: Chris Fouts [mailto:chris.fo...@caemilusa.com]
Sent: Wednesday, February 22, 2012 1:04 PM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] non-readonly properties

I have the following properties defined in mynant.build file
!-- Use these Bools for enable either Project1 and/or Project2 
builds --
property name=enable_project1_build value=true 
readonly=false /
property name=enable_project2_build value=true 
readonly=false /

But when I run script where I override the defined properties, e.g.,
C:\ nant mynant.build -D:enable_project1_build=false

I get...
Read-only property enable_project1_build cannot be overwritten.

I do echo the values for testing, I get the correct value, so should I just 
ignore the noise?

-chris



***This e-mail message is intended only for the above named recipient(s)
and may contain information that is sensitive or proprietary. If you have
received this message in error or are not the named recipient(s), please
immediately notify the sender, delete this e-mail message without making
a copy and do not disclose or relay this e-mail message to anyone.***
--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users


Re: [NAnt-users] non-readonly properties

2012-02-22 Thread Chris Fouts
Thanks, I was actually setting the arguments in CCNET, via buildArgs

From: Bob Archer [mailto:bob.arc...@amsi.com]
Sent: Wednesday, February 22, 2012 1:25 PM
To: Chris Fouts; nant-users@lists.sourceforge.net
Subject: RE: non-readonly properties

Properties set on the command line are always read-only.

If you want to not reset a property value if it was set from the command line 
you can use overwrite=false.

Also, when you pass false from the command line you don't need to quote it.

BOb


From: Chris Fouts [mailto:chris.fo...@caemilusa.com]
Sent: Wednesday, February 22, 2012 1:04 PM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] non-readonly properties

I have the following properties defined in mynant.build file
!-- Use these Bools for enable either Project1 and/or Project2 
builds --
property name=enable_project1_build value=true 
readonly=false /
property name=enable_project2_build value=true 
readonly=false /

But when I run script where I override the defined properties, e.g.,
C:\ nant mynant.build -D:enable_project1_build=false

I get...
Read-only property enable_project1_build cannot be overwritten.

I do echo the values for testing, I get the correct value, so should I just 
ignore the noise?

-chris



***This e-mail message is intended only for the above named recipient(s)
and may contain information that is sensitive or proprietary. If you have
received this message in error or are not the named recipient(s), please
immediately notify the sender, delete this e-mail message without making
a copy and do not disclose or relay this e-mail message to anyone.***
--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users


[NAnt-users] Various NAnt Updates

2012-02-22 Thread Ryan Boggs
Hi all,

Just checking in with some progress that has been occurring in NAnt's
development.  It's not a complete list but there are a few big ones
that I think are worth highlighting.

* The VS project solution files for both NAnt and NAntContrib projects
have been updated to VS2010 format.

* .NET/Mono 1.* runtime support for NAnt has been dropped.  Target
support for .NET/Mono 1.* still exists, however.

* The style/ task has been updated to use xslCompiledTransform,
which should address the issue described here on Stackoverflow:
http://stackoverflow.com/questions/5032347/xslt-stylesheet-replaces-self-closing-tags-with-empty-paired-tags
Thanks to Michael Tutty for the contribution via pull request for this item.

* The mail/ task has been updated to use System.Net.Mail instead of
System.Web.Mail.  During the process of updating this task, additional
features were added that we thought to be very helpful (such as
specifying a reply to address, specifying the port number to send mail
to, indicating whether or not to use an ssl connection, etc).

* More work has gone into the msbuild/ with the help from Dominik
Guder and Martin Aliger.  From what I understand, there are still a
couple of outstanding issues with this item but the task is working
better with recent versions of msbuild scripts.  This is still a high
priority.

* Quite a bit of work has been put into upgrading the nunit2/ task
to reference the latest version of NUnit.  I'm happy to say that these
changes are currently in review to be imported into nant/master.  The
version of NUnit being used for this upgrade is 2.6 final (which was
released just a few days ago).  I'm hoping that this will go into
master soon.  I want to say thanks to Charles Poole and the rest of
the NUnit dev team for their help and insight to get the nunit2/ up
to speed.  They were very helpful in this process.  Anyone interested
in viewing these changes can see them here:
https://github.com/nant/nant/tree/nunitupdates

* The nightly process for both NAnt and NAntContrib projects have
started up again.  This time, an automated process has been setup with
extensive help from Dominik Guder to make sure that new nightly files
are generated whenever changes occur on the master branches of either
project.  The last nightly was built on 2/19/2012 and includes all the
changes listed above except for the nunit changes.  The nightly files
can be found in the following locations:
NAnt Nightlys:
https://sourceforge.net/projects/nant/files/nant/nightly/

NAntContrib Nightlys:
https://sourceforge.net/projects/nantcontrib/files/nantcontrib/nightly/

We are still trying to nail down release dates and should be
announcing them as soon as they are finalized.

The next version number being targeted for NAnt/NAntContrib is
currently 0.92. It seems like the natural progression but we are
curious if you have any reasons to use a different version number (ie:
should we skip 0.92 and go to 0.95, etc).

That's all I have for now.  I will try to send out these kinds of
notices more often as progress continues.

Thanks,
Ryan

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users