nant-users — list for nant users. not for questions related to nant internals

[NAnt-users] NAnt msbuild looking for v4.0 but it should point to 15.0

[Saravana k. <sar...@gm...>]

Hello Team,

I need some help here.

I have my nant build file which targets MSBUILD PATH to
\framework64\v4.0.30139

I checked this with the help of the variable ${framework ::
get-tool-path('msbuild.exe')}

But I want my msbuild path to be on 2017\Community\MSBuild\15.0\bin

Kindly help what needs to be done

Re: [NAnt-users] Hi all

[Timotheus P. <tim...@po...>]

Hello Fabien,

I did not check the mail folder for NAnt for a very long time...

> I’d like to know if people still here could send on the ML any link, any
> piece of custom script task that could be added to the main Nant website? Or
> anything else that users can do to shock this project back to life?

We are using NAnt extensively for developing OpenPetra.
We can create Project files and solution files for various IDEs, and
are using NAnt for the whole toolchain of developing and delivering
OpenPetra.

We have a number of Nant scripts here:
https://github.com/openpetra/openpetra/tree/master/inc/nant
and various build files throughout the source code tree, eg.
https://github.com/openpetra/openpetra/blob/master/setup/setup.build
and some tasks developed here:
https://github.com/openpetra/openpetra/tree/master/inc/nanttasks

Hope this helps,
  Timotheus

[NAnt-users] <NUnit2> task running x86 tests

[Mike A. <xb...@ya...>]

Hello!

Im trying to run some tests using NAnt <nunit2> task, but it fails with next error:

---"Could not load file or assembly '-assembly info-' or one of its dependencies. An attempt was made to load a program with an incorrect format."

I tried to configure "appconfig" but it gave no result.

Then i tried to reproduce the error in NUnit-standalone and figured out that same error occures if i use "nunit-console.exe" instead of "nunit-console-x86.exe".

Its important to run the <nunit2> task because Teamcity supports Code Coverage only for that task.

Is it possible to run <nunit2> task with behaviour of "nunit-console-x86.exe"?

Thank you,
Mikhail.

Re: [NAnt-users] Hi all

[Ryan B. <rm...@gm...>]

Hi,

See inline...

On Wed, Dec 24, 2014 at 1:29 AM, Fabien Poirier <f.p...@in...>
wrote:

>  Hi,
>
>
>
> My name is Fabien, I was using Nant as a .Net build tool on C# projects.
> Now I’ve changed of work and I am using it as a build tool for Delphi
> projects (yes).
>
Nice to meet you.

>
>
> I am using SVN and I build my own continuous integration chain, I connect
> to SVN, get info in XML, do some xmlpeek to get last revision, compare it
> with the last built, and rebuilt if needed.
>
>
>
> I’d like to know if Nant project is still alive, are there some
> contributors that want to make this project grows?
>
I think the best way to describe the status is slowly waking up from a 2
year nap.  I just reviewed a back log of pull requests on github.com of
people fixing issues that they wanted to fix. I also fixed an issue that
was introduced in 0.92 related to the copy task (sorry about that) and I
just submitted another pull request for review to address another issue
reported some time ago. Dominik has been working on the CI system to
stabilize it since the system has changed since we last checked in on it
and reviewing the code in my pull requests. There are also new nightly
files that can be tested in sourceforge.net. So we are slowly getting back
on our feet here.

>
>
> I was using Ant before on java project, Nant is much more cool to use, but
> there are many, many things that could be better (IMHO), so many ways to go
> forward.
>
Yup.

>
>
> I’d like to know if people still here could send on the ML any link, any
> piece of custom script task that could be added to the main Nant website?
> Or anything else that users can do to shock this project back to life?
>
You can contribute code, examples, etc.  A good place to start is in the
wiki at github.com. It is a bit dated but it still applies.
https://github.com/nant/nant/wiki/Development-Guide

>
>
> Nant could be extended by so many means, but it is not easy to find
> example of source code, for example the while task, etc.
>
We can work on that. I have ideas I want to work on but it'll take time.

Happy holidays,
Ryan

>
>
> I wish you a Merry Christmas!
>
> Fabien
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> NAnt-users mailing list
> NAn...@li...
> https://lists.sourceforge.net/lists/listinfo/nant-users
>
>

[NAnt-users] Hi all

[Fabien P. <f.p...@in...>]

Hi,

My name is Fabien, I was using Nant as a .Net build tool on C# projects. Now I've changed of work and I am using it as a build tool for Delphi projects (yes).

I am using SVN and I build my own continuous integration chain, I connect to SVN, get info in XML, do some xmlpeek to get last revision, compare it with the last built, and rebuilt if needed.

I'd like to know if Nant project is still alive, are there some contributors that want to make this project grows?

I was using Ant before on java project, Nant is much more cool to use, but there are many, many things that could be better (IMHO), so many ways to go forward.

I'd like to know if people still here could send on the ML any link, any piece of custom script task that could be added to the main Nant website? Or anything else that users can do to shock this project back to life?

Nant could be extended by so many means, but it is not easy to find example of source code, for example the while task, etc.

I wish you a Merry Christmas!
Fabien

[NAnt-users] New Nightlys Available

[Ryan B. <rm...@gm...>]

Hi,

I just wanted to let people know that a new nightly builds have been
posted at sourceforge.net.  The links are below.

http://sourceforge.net/projects/nant/files/nant/nightly/2014-12-22/
http://sourceforge.net/projects/nantcontrib/files/nantcontrib/nightly/2014-12-22/

This build addresses the following items:

 * Fixes issues with the <copy/> task that was introduced in 0.92
 * Adds initial implementation of parallel execution
 * The net-2.0 target now uses the Windows SDKs by default instead of
the old .NET 2.0 sdk.
    - NAnt will fallback to the old .NET 2.0 sdk if no valid Windows
SDKs are found on the running machine.

We encourage the users to give this nightly build a try to see what
else they would like added/modified/fixed that have not already been
reported in NAnt's issues page on github.com.

https://github.com/nant

We'll send out updates as they come in.

You can also see commits to both NAnt/NAntContrib projects on twitter:
https://twitter.com/nantproject

Happy holidays. :)

Thanks,
Ryan

[NAnt-users] FileSystemWatcher Custom NAnt Task

[MacDiarmid, J. D. <JAM...@le...>]

There may be something already out there but I am working on one of my
own to monitor a build folder.   I'd like to pass in the Notify Type and
was wondering what would be the best way.   I was considering passing it
in as a piped string of keywords.  Is there a more elegant way of doing
it?

 

 

Thanks,

Jim

 

 

Re: [NAnt-users] Problem with vsscheckin task

[Bob A. <Bob...@am...>]

> I'm using the latest release versions of NAnt and NAnt Contrib (0.92) on a 64
> bit Windows 7 box. I am using the files from Issue 54
> (https://github.com/rmboggs/nant/downloads). I created the scripts on a 32
> bit XP machine, which has since bit the dust.
> 
> I am using it to do some things in Visual SourceSafe and perform a build. The
> vssget, vsscheckout, and vssadd tasks all seem to be working fine, but
> vsscheckin only checks in a few files and stops. The task does not throw an
> error, in fact, it states it completed successfully. I have been banging my
> head on the wall with this and can't figure this out.
> 
> We are phasing out XP, so getting a new XP machine is out of the question.
> 
> Any suggestions would be good.

I suggest using the exec task to execute the native vss command line tools. 

BOb

[NAnt-users] Problem with vsscheckin task

[Wilson, B. <Bri...@dh...>]

Howdy,

I'm using the latest release versions of NAnt and NAnt Contrib (0.92) on a 64 bit Windows 7 box. I am using the files from Issue 54 (https://github.com/rmboggs/nant/downloads). I created the scripts on a 32 bit XP machine, which has since bit the dust.

I am using it to do some things in Visual SourceSafe and perform a build. The vssget, vsscheckout, and vssadd tasks all seem to be working fine, but vsscheckin only checks in a few files and stops. The task does not throw an error, in fact, it states it completed successfully. I have been banging my head on the wall with this and can't figure this out.

We are phasing out XP, so getting a new XP machine is out of the question.

Any suggestions would be good.

Thank you,

Brian Wilson
Department of Human Resources

Re: [NAnt-users] nightly build Solution format not supported

[Bob A. <Bob...@am...>]

I suggest you modify your build script to use MSBuild task instead of the solution task.

BOb


From: Joao Miguel Ferreira [mailto:joa...@gm...]
Sent: Tuesday, January 07, 2014 10:33 AM
To: nan...@li...
Subject: [NAnt-users] nightly build Solution format not supported

Hello,

I'm using VS2010 on a Win7 32 bit. A few months ago I was able to build my C# .sln with nant-0.92. Meanwhile some developers moved to VS 2012 (I did not). Maybe some other changes happened that I'm not aware of.

Well, it does not build with nant anymore (tried 0.92 and the latest nightly build).

The message is the same in both:

"Solution format of file 'c:\...\....\...sln' is not supported"

Can you help?

Thank you
Joao

[NAnt-users] nightly build Solution format not supported

[Joao M. F. <joa...@gm...>]

Hello,

I'm using VS2010 on a Win7 32 bit. A few months ago I was able to build
my C# .sln with nant-0.92. Meanwhile some developers moved to VS 2012 (I
did not). Maybe some other changes happened that I'm not aware of.

Well, it does not build with nant anymore (tried 0.92 and the latest
nightly build).

The message is the same in both:

"Solution format of file 'c:\...\....\...sln' is not supported"

Can you help?

Thank you
Joao

[NAnt-users] Fake Conferences CSCI and WORLDCOMP of Hamid Arabnia

[<ric...@hu...>]

Fake Conferences CSCI and WORLDCOMP of Hamid Arabnia


Hamid Arabnia from University of Georgia is well known 
for his fake WORLDCOMP conferences 
https://sites.google.com/site/dumpconf  This website 
has an open challenge posted sometime in 2012 and it 
also has comments from several well-known researchers 
on WORLDCOMP. Hamd Arabnia never responded to these 
because his conferences are bogus.


Hamid Arabnia (the money hungry professor) has 
recently started 2014 International Conference on 
Computational Science and Computational Intelligence 
(CSCI'14) http://www.americancse.org to deceive 
researchers further. CSCI'14 is started under the 
title of “American Council on Science and Education” 
which is a dummy corporation (does not exist anywhere 
in the world). Hamid Arabnia buried his name in the 
list of names of other innocent steering and program 
committee members of CSCI’14 to avoid any special 
attention. He knows that if his name is given any 
special attention then researchers immediately notice 
that the conference is fake due to his “track record” 
with WORLDCOMP. Hamid Arabnia (Guru of Fake 
Conferences and champion of academic scam) spoiled the 
reputations and careers of many authors who submitted 
papers to his infamous WORLDCOMP for more than a 
decade and he is now ready to do the same using CSCI.


Interestingly, CSCI is scheduled to be held at the 
same venue where WORLDCOMP was held until 2012. CSCI 
has no general chair. It has no physical person’s 
name or physical address or phone number to contact. Only 
contact address is an email address. Hamid Arabnia and 
his puppets answer the emails, if needed, using fake names. 
Do not spoil your resume by submitting your papers in this 
bogus conference CSCI which will not be held beyond 2014.
CSCI will not be indexed by DBLP.
 

Recently, Hamid Arabnia paid money and published few 
“news articles” claiming him a victim of online harassment 
and cyber bullying. Now he started posting (using fake 
names and through his puppets) in various emails, blogs 
and forums, referring to those “news articles” and trying 
to get back sympathy and trust of the research community 
to make his CSCI successful. Hamid Arabnia is a Wolf in 
a Sheep’s skin.


We challenge Hamid Arabnia to openly publish the names and 
affiliation details of the reviewers for thousands of 
research papers submitted to WORLDCOMP for the last 
thirteen years. We also challenge Hamid Arabnia to openly 
publish all the reviews (after removing authors 
identification details) for all the thousands of research 
papers submitted to WORLDCOMP for the last thirteen years. 
There are more challenges at 
https://sites.google.com/site/moneycomp1 We know that he 
never accepts these challenges because there were no 
reviews and no reviewers and he simply cheated the research 
community for all these years. We are not surprised if he 
comes out tomorrow claiming that his computer crashed and he 
lost the reviews and reviewers’ details. He can play any 
deceiving trick.


See the important website 
https://sites.google.com/site/worlddump1 for more 
information on WORLDCOMP, including links to DBLP stop 
indexing WORLDCOMP proceedings. See 
http://worldcomp-fake-bogus.blogspot.com for Hamid Arabnia 
and his puppet’s Anti-Christmas Greetings campaign.


We ask Hamid Arabnia and his puppets to address the above 
issues and challenges before posting any other message.  


Do not spoil your resume by publishing in the fake 
conferences of Hamid Arabnia.


Sincerely,

Many researchers cheated by the conferences of Hamid Arabnia

[NAnt-users] Support for .Net 4.5 and 4.5.1 running/targeting

[Bob A. <Bob...@am...>]

I wonder if anyone is actively working on this project. I need to be able to build targeting .Net 4.5.1... it seems the last release stops support at 4.0.

If this is just a matter of adding some config info so Nant can find the framework/msbuild paths (it seems MSBuild 12 is now in the SDK path and not in the framework path) I would be happy to make the changes. Seems like a worthwhile thing to release .93 with only adding this.

I'm not sure what the solution task would need... but frankly I don't use it.

Anybody?

BOb

[NAnt-users] referencing mixed platform 3rd party assembly in custom task creation

[Munawar R. <a_m...@ho...>]

Hi,

I'm trying to create some a custom task to interact with our VisualSVN repo using SharpSVN api. I added a reference to the dll. I have one csproj file which all my individual task class files are bound to. It compiles fine, but with following warning.

There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "SharpSvn", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.   

Then when I run the task, it is failing with following message

System.IO.FileNotFoundException: Could not load file or assembly 'SharpSvn, Version=1.7002.1998.12257, Culture=neutral, PublicKeyToken=d729672594885a28' or one of its dependencies. The system cannot find the file specified.
File name: 'SharpSvn, Version=1.7002.1998.12257, Culture=neutral, PublicKeyToken=d729672594885a28'
   at XXX.Build.NAnt.CustomTasks.getSVNRevisionListTask.ExecuteTask()
   at NAnt.Core.Task.Execute()
   at NAnt.Core.Target.Execute()
   at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)
   at NAnt.Core.Project.Execute()
   at NAnt.Core.Project.Run()

Per somebody's suggestion in an online forum, I created a dll config file with the following content.

  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0"/>
  </startup>

But the problem persists. I also noted that nant.exe.config also has this entry, but without the useLegacyV2RuntimeActivationPolicy setting.

The SharpSVN dll should target win32/x86 platform. Although, I'm trying out the custom task in a widows server 2008 r2 server, I couldn't get the reference to x64 version of the dll to work with a console app, I was trying out earlier, leading me to stick with the x86 version. 

Has anybody faced similar issue with referencing assemblies for custom task that may not be compiled with anycpu platform setting. Does NAnt have an intrinsic way to deal with this kind of scenario. The fact that the 'startup' entry is there in the config, tells me that some such feature may have been attempted in nant.



 		 	   		  

[NAnt-users] MS Build 12

[Bob A. <Bob...@am...>]

So is NAnt going to use MS Build 12 now? I'm not sure how it finds the MSBuild path. Does it find paths based on the Framework targeting version?

I guess a more general question, is NAnt able to work with .Net 4.5.1 yet? I don't use the SOLUTION task I use the MSBUILD Task.

BOb

[NAnt-users] csc task does not handle my preprocessor directive

[Alexander op de W. <A.o...@to...>]

Hi all,

I'm having trouble passing pre-processor directives to my csc task. Below is a snippet of my build file:

<property name="defineSymbols" value="DIRECTIVENAME"/>
<csc target="library" output="test.dll" define="${defineSymbols}" platform="AnyCPU">
...
</csc>

Strange to see is that if I include a <echo message="${defineSymbols}"/> task just before the csc task, it echo's DIRECTIVENAME, just as I expected. My code files nevertheless are compiled as if the pre-processor directive isn't set.

If I change the 'define="${defineSymbols}"' to 'define="DIRECTIVENAME"' it all compiles as expected.

Any one any idea?

With kind regards,
Alexander op de Weegh

Re: [NAnt-users] Difference between debug and verbose command-line switches?

[MacDiarmid, J. D. <JAM...@sa...>]

 

Thank you Martin.   

 

 

From: Martin Gainty [mailto:mg...@ho...] 
Sent: Tuesday, July 16, 2013 9:09 PM
To: MacDiarmid, James D.
Subject: RE: [NAnt-users] Difference between debug and verbose
command-line switches?

 

Jim
 
debug  = script traverses each component and spills the stack and heap
for each referenced component (White Box Testing)

verbose = Script side verbosity ..does not reach into the components to
see whats going on inside (Black Box Testing)

HTH
Martin 
______________________________________________ 
illegal Alien interceptors..Altering this email will reward you with a
permanent vacation (back to the Middle East!)


 

________________________________

Date: Tue, 16 Jul 2013 13:38:26 -0400
From: JAM...@sa...
To: nan...@li...
Subject: [NAnt-users] Difference between debug and verbose command-line
switches?

Can anyone explain the difference between debug and verbose nant
switches please?  

 

Thanks in advance,

Jim


------------------------------------------------------------------------
------ See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds. Start your free
trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk
trk
_______________________________________________ NAnt-users mailing list
NAn...@li...
https://lists.sourceforge.net/lists/listinfo/nant-users

[NAnt-users] Difference between debug and verbose command-line switches?

[MacDiarmid, J. D. <JAM...@sa...>]

Can anyone explain the difference between debug and verbose nant
switches please?  

 

Thanks in advance,

Jim

[NAnt-users] NAnt Intellisense in VS2010

[MacDiarmid, J. D. <JAM...@sa...>]

Hi all,

 

I have NAnt set up to use intellisense in VS2010.  It works as expected
however I'm getting a Blue Tilde (Something like this "~" )  appearing
after the closing task bracket.  It shows a warning as follows:  

 

1.       The element cannot contain white space. Content model is empty.

 

I'm getting this:

1.       After the closing bracket for the <try> element in the
<TryCatch> task.

2.       After the closing bracket for the <finally> element in the
<TryCatch> task.

3.       After the closing bracket of the comment syntax "<!-comment
-->" .

4.       After the closing bracket for the <when> element in the
<choose> task.

5.       After the closing bracket for the <otherwise> element in the
<choose> task.

6.        

 

I'm also getting warnings like the following.   Any idea what would
cause this and/or how to fix them, if it's on my end?

 

"The element 'http://nant.sf.net/release/0.92/nant.xsd:try' cannot
contain child element 'http://nant.sf.net/release/0.92/nant.xsd:call'
because the parent element's content model is empty."

 

"The element 'http://nant.sf.net/release/0.92/nant.xsd:when' cannot
contain child element
'http://nant.sf.net/release/0.92/nant.xsd:property' because the parent
element's content model is empty."

 

"The element 'http://nant.sf.net/release/0.92/nant.xsd:otherwise' cannot
contain child element 'http://nant.sf.net/release/0.92/nant.xsd:fail'
because the parent element's content model is empty."

 

"The element 'target' in namespace
'http://nant.sf.net/release/0.92/nant.xsd' has invalid child element
'UpdateAssemblyVersion' in namespace
'http://nant.sf.net/release/0.92/nant.xsd'. List of possible elements
expected: 'gunzip, tar, untar, unzip, zip, testtask, elementTest1, test,
asminfo, al, csc, delay-sign, ilasm, jsc, license, ndoc, regsvcs,
resgen, script, vbc, vjc, nunit, nunit2, cvs-changelog, cvs-checkout,
cvs-pass, cvs, cvs-export, cvs-rtag, cvs-tag, cvs-update, cl, lib, link,
mc, midl, rc, solution, aximp, locatesdk, monoregistry, readregistry,
regasm, tlbexp, tlbimp, attrib, available, call, choose, copy, delete,
description, echo, exec, fail, get, if, ifnot, include, loadfile,
loadtasks, foreach, mail, mkdir, move, nantschema, nant, property,
regex, setenv, sleep, style, sysinfo, touch, trycatch, tstamp, uptodate,
xmlpeek, xmlpoke, ildasm, servicecontroller, tarfileset, zipfileset,
assemblyfileset, moduleset, namespaceimports, resourcefileset,
warnaserror, categories, cvsfileset, filterchain, credential, fileset,
dirset, path, patternset, proxy' in namespace
'http://nant.sf.net/release/0.92/nant.xsd' as well as any element in
namespace '##other'."

 

The element 'filterchain' in namespace
'http://nant.sf.net/release/0.92/nant.xsd' has invalid child element
'replacetokens' in namespace 'http://nant.sf.net/release/0.92/nant.xsd'.
List of possible elements expected: 'filter' in namespace
'http://nant.sf.net/release/0.92/nant.xsd'.
C:\Workspaces\AHLTA\3.8.0\Build\Packages\TFS\SourceControl.Target.xml

 

Re: [NAnt-users] Nested variables

[Labout, D. <Dou...@ef...>]

Thanks Bob!
That fixed it.

-----Original Message-----
From: Bob Archer [mailto:Bob...@am...]
Sent: Monday, June 17, 2013 1:18 PM
To: Labout, Douglas; 'nan...@li...'
Subject: RE: Nested variables

Right... so use the property::get-value() function. I think this is what you need to do:

<?xml version="1.0" ?>
<project name="test">


        <loadproperties file="buildLabels.properties" />

        <!-- The foreach bellow will loop through the list of projects in the Project.Build.Order in the buildLabels.properties -->
        <foreach item="String" in="${Project.Build.Order}" delim="," property="properties.project.Ord">
                        <echo message="${properties.project.Ord}" />
                         <call target="build.project"/>
        </foreach>

        <target name="build.project">
                <property name="ProjectName" value="${ property::get-value(properties.project.Ord+'.ProjectName')}"/>
                <property name="ViewName" value="${ property::get-value(properties.project.Ord +'.ViewName')}"/>
                <property name="Label" value="${ property::get-value(properties.project.Ord +'.Label')}"/>
                <echo>${ProjectName} ${ViewName} ${Label}</echo>
                <call target="checkoutModuleSrc"/>
        </target>

        <!-- checkout src directory -->
        <target name="checkoutModuleSrc">
        <!--
                <exec program="${starteam.cmd}">
                                 <arg line="co -p ${STUser}:${STPassword}@${STServer}:${STPort}/${ProjectName} -o -cfgl ${Label}"/>
                </exec>
        -->
                <echo message="${ProjectName} -o -cfgl ${Label}" />

        </target>


</project>

> -----Original Message-----
> From: Labout, Douglas [mailto:Dou...@ef...]
> Sent: Monday, June 17, 2013 2:24 PM
> To: Bob Archer; 'nan...@li...'
> Subject: RE: Nested variables
>
> Hmm,
> Let's see if I can explain it better...
>
> Here is the properties file that contains all the components to be
> built and their associated views and labels.
>
> # Projects Build Order
> Project.Name=WCFServices
> Project.Build.Directory=C:\/VisualStudio\/
> Project.Build.Order=NETComponents,NETDLLs,App
> Project.Deploy=C:\/VisualStudio\/\Windows - BuildScripts\/Deploy\/
>
> # Windows - .NET Components
> NETComponents.ProjectName=Windows - .NET Components
> NETComponents.ViewName=Windows - .NET Components
> NETComponents.Label=201261654
>
> # Windows - .NET DLLs
> NETDLLs.ProjectName=Windows - .NET DLLs NETDLLs.ViewName=Windows -
> .NET DLLs
> NETDLLs.Label=2013064494
>
> # Windows - WCFServices_NewAccounts.DataAccess
> App.ProjectName=Windows - _WCFServices App.ViewName=Windows -
> _WCFServices
> App.Label=201111781
>
> I use <loadproperties file="buildLabels.properties" /> to load the
> lines in the property file.
>
> Here is the loop that pulles build order:
>
> <!-- The foreach bellow will loop through the list of projects in the
> Project.Build.Order in the buildLabels.properties -->
>
>         <foreach item="String" in="${Project.Build.Order}" delim=","
> property="properties.project.Ord">
>                  <call target="build.project"/>
>         </foreach>
>
> Here is the build.project target:
>
> <target name="build.project">
>         <property name="ProjectName" value="${
> properties.project.Ord+'.ProjectName'}"/>
>         <property name="ViewName" value="${ properties.project.Ord'
> +'.ViewName'}"/>
>         <property name="Label" value="${ properties.project.Ord'+'.Label'}"/>
>         <echo>${ProjectName} ${ViewName} ${Label}</echo>
>         <call target="checkoutModuleSrc"/>
>
> And finally, here is the checkoutModuleSrc target:
>
>         <!-- checkout src directory -->
>   <target name="checkoutModuleSrc">
>
>         <exec program="${starteam.cmd}">
>                  <arg line="co -p
> ${STUser}:${STPassword}@${STServer}:${STPort}/${ProjectName} -o -cfgl
> ${Label}"/>
>         </exec>
>
>
> You can see that I loop through the build order and pick up one of the
> projects to be built, then append the .Projectname, .viewname and
> .label and then check out the code.
>
> The problem is that I can get it to return the property.project.Ord,
> but can't append the .ProjectName, .ViewName, or Label without it
> interpreting it as NETDLLs.ProjectName.
>
>
> -----Original Message-----
> From: Bob Archer [mailto:Bob...@am...]
> Sent: Monday, June 17, 2013 10:47 AM
> To: Labout, Douglas; 'nan...@li...'
> Subject: RE: Nested variables
>
> Ok... I guess I'm still not understanding what is in each variable:
>
> > You are correct in that I'm trying to put together a couple of variables.
> > The build order is assigned to the variable ${properties.project.Ord}.
> > I then
>
> What is the exact text in that variable?
>
> > append to the end of that variable the .ProjectName,
>
> Is that a property, or a literal? What value is in .ProjectName
> (assuming that is a variable?)
>
>  .ViewName, and .Label
> > and assign them to ${ProjectName}. I then pass $ProjectName to my
> > starteam checkout.
>
> Same questions...
>
> Are you trying to build a new variable name? So, when you say you want
> to append .ProjectName you mean the contents of that?
>
> If I knew what was in each variable in addition to the final value you
> expect in the variable, I could help you with more specific code.
>
> BOb
>
>
> >
> > The trouble is that ${properties.project.Ord} returns as "NETDLLS"
> > but when I want the variable ${NETDLLS.ProjectName} to be returned
> > as "NETDLLs.ProjectName=Windows - .NET DLLs" it instead comes back
> > as "NETDLLS.ProjectName".
> >
> > StarTeam goes looking for a NETDLLS.ProjectName and of course can't
> > find it and dies.
> >
> > Thanks for the help!
> > Much appreciated!
> > -Doug
> >
> > -----Original Message-----
> > From: Bob Archer [mailto:Bob...@am...]
> > Sent: Monday, June 17, 2013 9:22 AM
> > To: Labout, Douglas; 'nan...@li...'
> > Subject: RE: Nested variables
> >
> > > Hello,
> > > I'm working on converting an Ant script to Nant and have ran into
> > > an issue with joining several variables together in Nant.
> > >
> > > Below is the original Ant script in which it pulls information
> > > from a properties file and uses the information to feed the build.
> > > The project starts by looping through build order (NETDLLS, App)
> > > and then uses that variable to prepend to the ProjectName to check
> > > out of
> StarTeam.
> > >
> > > Project.Build.Order=NETDLLs,App
> > >
> > > # Windows - .NET DLLs
> > > NETDLLs.ProjectName=Windows - .NET DLLs NETDLLs.ViewName=Windows
> -
> > > .NET DLLs
> > > NETDLLs.Label=201300722.20130508
> > >
> > > ANT script:
> > > <target name="build.project">
> > >       <property name="ProjectName"
> > > value="${buildProp.${project.Ord}.ProjectName}"/>
> > >       <property name="ViewName"
> > > value="${buildProp.${project.Ord}.ViewName}"/>
> > >       <property name="Label"
> > > value="${buildProp.${project.Ord}.Label}"/>
> > >
> > >       <antcall target="checkoutModuleSrc" inheritall="true"/>
> > >
> > > Here is what I have come up with in Nant which doesn't seem to be
> working.
> > >
> > > NAnt script:
> > > <target name="build.project">
> > >       <property name="ProjectName"
> > > value="${'properties.project.Ord'+'.ProjectName'}"/>
> > >       <property name="ViewName"
> > > value="${'properties.project.Ord'+'.ViewName'}"/>
> > >       <property name="Label"
> > > value="${'properties.project.Ord'+'.Label'}"/>
> > >       <echo>${ProjectName} ${ViewName} ${Label}</echo>
> > >       <call target="checkoutModuleSrc"/>
> > >
> >
> > I assume based on your title "nested variables" you want to do
> > something like
> > this:
> >
> >
> > <property name="ProjectName" value="${property::get-
> > value('properties.project.Ord.ProjectName')}"/>
> >
> > ?????
> >
> > BOb
> >
> >
> >
> > > Results of the script at the command line:
> > > checkoutModuleSrc:
> > >
> > >      [exec] StarTeam 10.4 Command Line Interface, Build 10.4.8.36
> > >      [exec] Copyright (c) 2003-2008 Borland Software Corporation.
> > > All rights res erved.
> > >      [exec] Using ini file: C:\Documents and Settings\All
> > > Users\Application Data \Borland\StarTeam\ConnectionManager.ini
> > >      [exec] Project not found: properties.project.Ord.ProjectName
> > >
> > > I would appreciate any help you can provide.
> > >
> > > Thanks,
> > > -Doug Labout
> > >
> > >
> > > The information contained in this electronic communication and any
> > > document attached hereto or transmitted herewith is confidential
> > > and intended for the exclusive use of the individual or entity
> > > named above. If the reader of this message is not the intended
> > > recipient or the employee or agent responsible for delivering it
> > > to the intended recipient, you are hereby notified that any
> > > examination, use, dissemination, distribution or copying of this
> > > communication or any part thereof is strictly prohibited. If you
> > > have received this communication in error, please immediately
> > > notify the sender by reply e-mail
> > and destroy this communication. Thank you.
> >
> > The information contained in this electronic communication and any
> > document attached hereto or transmitted herewith is confidential and
> > intended for the exclusive use of the individual or entity named
> > above. If the reader of this message is not the intended recipient
> > or the employee or agent responsible for delivering it to the
> > intended recipient, you are hereby notified that any examination,
> > use, dissemination, distribution or copying of this communication or
> > any part thereof is strictly prohibited. If you have received this
> > communication in error, please immediately notify the sender by
> > reply e-mail
> and destroy this communication. Thank you.
>
> The information contained in this electronic communication and any
> document attached hereto or transmitted herewith is confidential and
> intended for the exclusive use of the individual or entity named
> above. If the reader of this message is not the intended recipient or
> the employee or agent responsible for delivering it to the intended
> recipient, you are hereby notified that any examination, use,
> dissemination, distribution or copying of this communication or any
> part thereof is strictly prohibited. If you have received this
> communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.

The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.

Re: [NAnt-users] Nested variables

[Bob A. <Bob...@am...>]

Right... so use the property::get-value() function. I think this is what you need to do:

<?xml version="1.0" ?>
<project name="test">


	<loadproperties file="buildLabels.properties" />

	<!-- The foreach bellow will loop through the list of projects in the Project.Build.Order in the buildLabels.properties -->
	<foreach item="String" in="${Project.Build.Order}" delim="," property="properties.project.Ord">
			<echo message="${properties.project.Ord}" />			
			 <call target="build.project"/>
	</foreach>

	<target name="build.project">
		<property name="ProjectName" value="${ property::get-value(properties.project.Ord+'.ProjectName')}"/>
		<property name="ViewName" value="${ property::get-value(properties.project.Ord +'.ViewName')}"/>
		<property name="Label" value="${ property::get-value(properties.project.Ord +'.Label')}"/>
		<echo>${ProjectName} ${ViewName} ${Label}</echo>
		<call target="checkoutModuleSrc"/>
	</target>

	<!-- checkout src directory -->
	<target name="checkoutModuleSrc">
	<!--
		<exec program="${starteam.cmd}">
				 <arg line="co -p ${STUser}:${STPassword}@${STServer}:${STPort}/${ProjectName} -o -cfgl ${Label}"/>
		</exec>
	-->	
		<echo message="${ProjectName} -o -cfgl ${Label}" />
		
	</target>


</project>

> -----Original Message-----
> From: Labout, Douglas [mailto:Dou...@ef...]
> Sent: Monday, June 17, 2013 2:24 PM
> To: Bob Archer; 'nan...@li...'
> Subject: RE: Nested variables
> 
> Hmm,
> Let's see if I can explain it better...
> 
> Here is the properties file that contains all the components to be built and their
> associated views and labels.
> 
> # Projects Build Order
> Project.Name=WCFServices
> Project.Build.Directory=C:\/VisualStudio\/
> Project.Build.Order=NETComponents,NETDLLs,App
> Project.Deploy=C:\/VisualStudio\/\Windows - BuildScripts\/Deploy\/
> 
> # Windows - .NET Components
> NETComponents.ProjectName=Windows - .NET Components
> NETComponents.ViewName=Windows - .NET Components
> NETComponents.Label=201261654
> 
> # Windows - .NET DLLs
> NETDLLs.ProjectName=Windows - .NET DLLs
> NETDLLs.ViewName=Windows - .NET DLLs
> NETDLLs.Label=2013064494
> 
> # Windows - WCFServices_NewAccounts.DataAccess
> App.ProjectName=Windows - _WCFServices
> App.ViewName=Windows - _WCFServices
> App.Label=201111781
> 
> I use <loadproperties file="buildLabels.properties" /> to load the lines in the
> property file.
> 
> Here is the loop that pulles build order:
> 
> <!-- The foreach bellow will loop through the list of projects in the
> Project.Build.Order in the buildLabels.properties -->
> 
>         <foreach item="String" in="${Project.Build.Order}" delim=","
> property="properties.project.Ord">
>                  <call target="build.project"/>
>         </foreach>
> 
> Here is the build.project target:
> 
> <target name="build.project">
>         <property name="ProjectName" value="${
> properties.project.Ord+'.ProjectName'}"/>
>         <property name="ViewName" value="${ properties.project.Ord'
> +'.ViewName'}"/>
>         <property name="Label" value="${ properties.project.Ord'+'.Label'}"/>
>         <echo>${ProjectName} ${ViewName} ${Label}</echo>
>         <call target="checkoutModuleSrc"/>
> 
> And finally, here is the checkoutModuleSrc target:
> 
>         <!-- checkout src directory -->
>   <target name="checkoutModuleSrc">
> 
>         <exec program="${starteam.cmd}">
>                  <arg line="co -p
> ${STUser}:${STPassword}@${STServer}:${STPort}/${ProjectName} -o -cfgl
> ${Label}"/>
>         </exec>
> 
> 
> You can see that I loop through the build order and pick up one of the projects
> to be built, then append the .Projectname, .viewname and .label and then
> check out the code.
> 
> The problem is that I can get it to return the property.project.Ord, but can't
> append the .ProjectName, .ViewName, or Label without it interpreting it as
> NETDLLs.ProjectName.
> 
> 
> -----Original Message-----
> From: Bob Archer [mailto:Bob...@am...]
> Sent: Monday, June 17, 2013 10:47 AM
> To: Labout, Douglas; 'nan...@li...'
> Subject: RE: Nested variables
> 
> Ok... I guess I'm still not understanding what is in each variable:
> 
> > You are correct in that I'm trying to put together a couple of variables.
> > The build order is assigned to the variable ${properties.project.Ord}.
> > I then
> 
> What is the exact text in that variable?
> 
> > append to the end of that variable the .ProjectName,
> 
> Is that a property, or a literal? What value is in .ProjectName (assuming that is
> a variable?)
> 
>  .ViewName, and .Label
> > and assign them to ${ProjectName}. I then pass $ProjectName to my
> > starteam checkout.
> 
> Same questions...
> 
> Are you trying to build a new variable name? So, when you say you want to
> append .ProjectName you mean the contents of that?
> 
> If I knew what was in each variable in addition to the final value you expect in
> the variable, I could help you with more specific code.
> 
> BOb
> 
> 
> >
> > The trouble is that ${properties.project.Ord} returns as "NETDLLS" but
> > when I want the variable ${NETDLLS.ProjectName} to be returned as
> > "NETDLLs.ProjectName=Windows - .NET DLLs" it instead comes back as
> > "NETDLLS.ProjectName".
> >
> > StarTeam goes looking for a NETDLLS.ProjectName and of course can't
> > find it and dies.
> >
> > Thanks for the help!
> > Much appreciated!
> > -Doug
> >
> > -----Original Message-----
> > From: Bob Archer [mailto:Bob...@am...]
> > Sent: Monday, June 17, 2013 9:22 AM
> > To: Labout, Douglas; 'nan...@li...'
> > Subject: RE: Nested variables
> >
> > > Hello,
> > > I'm working on converting an Ant script to Nant and have ran into an
> > > issue with joining several variables together in Nant.
> > >
> > > Below is the original Ant script in which it pulls information from
> > > a properties file and uses the information to feed the build. The
> > > project starts by looping through build order (NETDLLS, App) and
> > > then uses that variable to prepend to the ProjectName to check out of
> StarTeam.
> > >
> > > Project.Build.Order=NETDLLs,App
> > >
> > > # Windows - .NET DLLs
> > > NETDLLs.ProjectName=Windows - .NET DLLs NETDLLs.ViewName=Windows
> -
> > > .NET DLLs
> > > NETDLLs.Label=201300722.20130508
> > >
> > > ANT script:
> > > <target name="build.project">
> > >       <property name="ProjectName"
> > > value="${buildProp.${project.Ord}.ProjectName}"/>
> > >       <property name="ViewName"
> > > value="${buildProp.${project.Ord}.ViewName}"/>
> > >       <property name="Label"
> > > value="${buildProp.${project.Ord}.Label}"/>
> > >
> > >       <antcall target="checkoutModuleSrc" inheritall="true"/>
> > >
> > > Here is what I have come up with in Nant which doesn't seem to be
> working.
> > >
> > > NAnt script:
> > > <target name="build.project">
> > >       <property name="ProjectName"
> > > value="${'properties.project.Ord'+'.ProjectName'}"/>
> > >       <property name="ViewName"
> > > value="${'properties.project.Ord'+'.ViewName'}"/>
> > >       <property name="Label"
> > > value="${'properties.project.Ord'+'.Label'}"/>
> > >       <echo>${ProjectName} ${ViewName} ${Label}</echo>
> > >       <call target="checkoutModuleSrc"/>
> > >
> >
> > I assume based on your title "nested variables" you want to do
> > something like
> > this:
> >
> >
> > <property name="ProjectName" value="${property::get-
> > value('properties.project.Ord.ProjectName')}"/>
> >
> > ?????
> >
> > BOb
> >
> >
> >
> > > Results of the script at the command line:
> > > checkoutModuleSrc:
> > >
> > >      [exec] StarTeam 10.4 Command Line Interface, Build 10.4.8.36
> > >      [exec] Copyright (c) 2003-2008 Borland Software Corporation.
> > > All rights res erved.
> > >      [exec] Using ini file: C:\Documents and Settings\All
> > > Users\Application Data \Borland\StarTeam\ConnectionManager.ini
> > >      [exec] Project not found: properties.project.Ord.ProjectName
> > >
> > > I would appreciate any help you can provide.
> > >
> > > Thanks,
> > > -Doug Labout
> > >
> > >
> > > The information contained in this electronic communication and any
> > > document attached hereto or transmitted herewith is confidential and
> > > intended for the exclusive use of the individual or entity named
> > > above. If the reader of this message is not the intended recipient
> > > or the employee or agent responsible for delivering it to the
> > > intended recipient, you are hereby notified that any examination,
> > > use, dissemination, distribution or copying of this communication or
> > > any part thereof is strictly prohibited. If you have received this
> > > communication in error, please immediately notify the sender by
> > > reply e-mail
> > and destroy this communication. Thank you.
> >
> > The information contained in this electronic communication and any
> > document attached hereto or transmitted herewith is confidential and
> > intended for the exclusive use of the individual or entity named
> > above. If the reader of this message is not the intended recipient or
> > the employee or agent responsible for delivering it to the intended
> > recipient, you are hereby notified that any examination, use,
> > dissemination, distribution or copying of this communication or any
> > part thereof is strictly prohibited. If you have received this
> > communication in error, please immediately notify the sender by reply e-mail
> and destroy this communication. Thank you.
> 
> The information contained in this electronic communication and any document
> attached hereto or transmitted herewith is confidential and intended for the
> exclusive use of the individual or entity named above. If the reader of this
> message is not the intended recipient or the employee or agent responsible for
> delivering it to the intended recipient, you are hereby notified that any
> examination, use, dissemination, distribution or copying of this communication
> or any part thereof is strictly prohibited. If you have received this
> communication in error, please immediately notify the sender by reply e-mail
> and destroy this communication. Thank you.

Re: [NAnt-users] Nested variables

[Labout, D. <Dou...@ef...>]

Hmm,
Let's see if I can explain it better...

Here is the properties file that contains all the components to be built and their associated views and labels.

# Projects Build Order
Project.Name=WCFServices
Project.Build.Directory=C:\/VisualStudio\/
Project.Build.Order=NETComponents,NETDLLs,App
Project.Deploy=C:\/VisualStudio\/\Windows - BuildScripts\/Deploy\/

# Windows - .NET Components
NETComponents.ProjectName=Windows - .NET Components
NETComponents.ViewName=Windows - .NET Components
NETComponents.Label=201261654

# Windows - .NET DLLs
NETDLLs.ProjectName=Windows - .NET DLLs
NETDLLs.ViewName=Windows - .NET DLLs
NETDLLs.Label=2013064494

# Windows - WCFServices_NewAccounts.DataAccess
App.ProjectName=Windows - _WCFServices
App.ViewName=Windows - _WCFServices
App.Label=201111781

I use <loadproperties file="buildLabels.properties" /> to load the lines in the property file.

Here is the loop that pulles build order:

<!-- The foreach bellow will loop through the list of projects in the Project.Build.Order in the buildLabels.properties -->

        <foreach item="String" in="${Project.Build.Order}" delim="," property="properties.project.Ord">
                 <call target="build.project"/>
        </foreach>

Here is the build.project target:

<target name="build.project">
        <property name="ProjectName" value="${ properties.project.Ord+'.ProjectName'}"/>
        <property name="ViewName" value="${ properties.project.Ord' +'.ViewName'}"/>
        <property name="Label" value="${ properties.project.Ord'+'.Label'}"/>
        <echo>${ProjectName} ${ViewName} ${Label}</echo>
        <call target="checkoutModuleSrc"/>

And finally, here is the checkoutModuleSrc target:

        <!-- checkout src directory -->
  <target name="checkoutModuleSrc">

        <exec program="${starteam.cmd}">
                 <arg line="co -p ${STUser}:${STPassword}@${STServer}:${STPort}/${ProjectName} -o -cfgl ${Label}"/>
        </exec>


You can see that I loop through the build order and pick up one of the projects to be built, then append the .Projectname, .viewname and .label and then check out the code.

The problem is that I can get it to return the property.project.Ord, but can't append the .ProjectName, .ViewName, or Label without it interpreting it as NETDLLs.ProjectName.


-----Original Message-----
From: Bob Archer [mailto:Bob...@am...]
Sent: Monday, June 17, 2013 10:47 AM
To: Labout, Douglas; 'nan...@li...'
Subject: RE: Nested variables

Ok... I guess I'm still not understanding what is in each variable:

> You are correct in that I'm trying to put together a couple of variables.
> The build order is assigned to the variable ${properties.project.Ord}.
> I then

What is the exact text in that variable?

> append to the end of that variable the .ProjectName,

Is that a property, or a literal? What value is in .ProjectName (assuming that is a variable?)

 .ViewName, and .Label
> and assign them to ${ProjectName}. I then pass $ProjectName to my
> starteam checkout.

Same questions...

Are you trying to build a new variable name? So, when you say you want to append .ProjectName you mean the contents of that?

If I knew what was in each variable in addition to the final value you expect in the variable, I could help you with more specific code.

BOb


>
> The trouble is that ${properties.project.Ord} returns as "NETDLLS" but
> when I want the variable ${NETDLLS.ProjectName} to be returned as
> "NETDLLs.ProjectName=Windows - .NET DLLs" it instead comes back as
> "NETDLLS.ProjectName".
>
> StarTeam goes looking for a NETDLLS.ProjectName and of course can't
> find it and dies.
>
> Thanks for the help!
> Much appreciated!
> -Doug
>
> -----Original Message-----
> From: Bob Archer [mailto:Bob...@am...]
> Sent: Monday, June 17, 2013 9:22 AM
> To: Labout, Douglas; 'nan...@li...'
> Subject: RE: Nested variables
>
> > Hello,
> > I'm working on converting an Ant script to Nant and have ran into an
> > issue with joining several variables together in Nant.
> >
> > Below is the original Ant script in which it pulls information from
> > a properties file and uses the information to feed the build. The
> > project starts by looping through build order (NETDLLS, App) and
> > then uses that variable to prepend to the ProjectName to check out of StarTeam.
> >
> > Project.Build.Order=NETDLLs,App
> >
> > # Windows - .NET DLLs
> > NETDLLs.ProjectName=Windows - .NET DLLs NETDLLs.ViewName=Windows -
> > .NET DLLs
> > NETDLLs.Label=201300722.20130508
> >
> > ANT script:
> > <target name="build.project">
> >       <property name="ProjectName"
> > value="${buildProp.${project.Ord}.ProjectName}"/>
> >       <property name="ViewName"
> > value="${buildProp.${project.Ord}.ViewName}"/>
> >       <property name="Label"
> > value="${buildProp.${project.Ord}.Label}"/>
> >
> >       <antcall target="checkoutModuleSrc" inheritall="true"/>
> >
> > Here is what I have come up with in Nant which doesn't seem to be working.
> >
> > NAnt script:
> > <target name="build.project">
> >       <property name="ProjectName"
> > value="${'properties.project.Ord'+'.ProjectName'}"/>
> >       <property name="ViewName"
> > value="${'properties.project.Ord'+'.ViewName'}"/>
> >       <property name="Label"
> > value="${'properties.project.Ord'+'.Label'}"/>
> >       <echo>${ProjectName} ${ViewName} ${Label}</echo>
> >       <call target="checkoutModuleSrc"/>
> >
>
> I assume based on your title "nested variables" you want to do
> something like
> this:
>
>
> <property name="ProjectName" value="${property::get-
> value('properties.project.Ord.ProjectName')}"/>
>
> ?????
>
> BOb
>
>
>
> > Results of the script at the command line:
> > checkoutModuleSrc:
> >
> >      [exec] StarTeam 10.4 Command Line Interface, Build 10.4.8.36
> >      [exec] Copyright (c) 2003-2008 Borland Software Corporation.
> > All rights res erved.
> >      [exec] Using ini file: C:\Documents and Settings\All
> > Users\Application Data \Borland\StarTeam\ConnectionManager.ini
> >      [exec] Project not found: properties.project.Ord.ProjectName
> >
> > I would appreciate any help you can provide.
> >
> > Thanks,
> > -Doug Labout
> >
> >
> > The information contained in this electronic communication and any
> > document attached hereto or transmitted herewith is confidential and
> > intended for the exclusive use of the individual or entity named
> > above. If the reader of this message is not the intended recipient
> > or the employee or agent responsible for delivering it to the
> > intended recipient, you are hereby notified that any examination,
> > use, dissemination, distribution or copying of this communication or
> > any part thereof is strictly prohibited. If you have received this
> > communication in error, please immediately notify the sender by
> > reply e-mail
> and destroy this communication. Thank you.
>
> The information contained in this electronic communication and any
> document attached hereto or transmitted herewith is confidential and
> intended for the exclusive use of the individual or entity named
> above. If the reader of this message is not the intended recipient or
> the employee or agent responsible for delivering it to the intended
> recipient, you are hereby notified that any examination, use,
> dissemination, distribution or copying of this communication or any
> part thereof is strictly prohibited. If you have received this
> communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.

The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.

Re: [NAnt-users] Nested variables

[Bob A. <Bob...@am...>]

Ok... I guess I'm still not understanding what is in each variable:

> You are correct in that I'm trying to put together a couple of variables.
> The build order is assigned to the variable ${properties.project.Ord}. I then

What is the exact text in that variable?

> append to the end of that variable the .ProjectName,

Is that a property, or a literal? What value is in .ProjectName (assuming that is a variable?)

 .ViewName, and .Label
> and assign them to ${ProjectName}. I then pass $ProjectName to my starteam
> checkout.

Same questions...

Are you trying to build a new variable name? So, when you say you want to append .ProjectName you mean the contents of that? 

If I knew what was in each variable in addition to the final value you expect in the variable, I could help you with more specific code.

BOb


> 
> The trouble is that ${properties.project.Ord} returns as "NETDLLS" but when I
> want the variable ${NETDLLS.ProjectName} to be returned as
> "NETDLLs.ProjectName=Windows - .NET DLLs" it instead comes back as
> "NETDLLS.ProjectName".
> 
> StarTeam goes looking for a NETDLLS.ProjectName and of course can't find it
> and dies.
> 
> Thanks for the help!
> Much appreciated!
> -Doug
> 
> -----Original Message-----
> From: Bob Archer [mailto:Bob...@am...]
> Sent: Monday, June 17, 2013 9:22 AM
> To: Labout, Douglas; 'nan...@li...'
> Subject: RE: Nested variables
> 
> > Hello,
> > I'm working on converting an Ant script to Nant and have ran into an
> > issue with joining several variables together in Nant.
> >
> > Below is the original Ant script in which it pulls information from a
> > properties file and uses the information to feed the build. The
> > project starts by looping through build order (NETDLLS, App) and then
> > uses that variable to prepend to the ProjectName to check out of StarTeam.
> >
> > Project.Build.Order=NETDLLs,App
> >
> > # Windows - .NET DLLs
> > NETDLLs.ProjectName=Windows - .NET DLLs NETDLLs.ViewName=Windows -
> > .NET DLLs
> > NETDLLs.Label=201300722.20130508
> >
> > ANT script:
> > <target name="build.project">
> >       <property name="ProjectName"
> > value="${buildProp.${project.Ord}.ProjectName}"/>
> >       <property name="ViewName"
> > value="${buildProp.${project.Ord}.ViewName}"/>
> >       <property name="Label"
> > value="${buildProp.${project.Ord}.Label}"/>
> >
> >       <antcall target="checkoutModuleSrc" inheritall="true"/>
> >
> > Here is what I have come up with in Nant which doesn't seem to be working.
> >
> > NAnt script:
> > <target name="build.project">
> >       <property name="ProjectName"
> > value="${'properties.project.Ord'+'.ProjectName'}"/>
> >       <property name="ViewName"
> > value="${'properties.project.Ord'+'.ViewName'}"/>
> >       <property name="Label"
> > value="${'properties.project.Ord'+'.Label'}"/>
> >       <echo>${ProjectName} ${ViewName} ${Label}</echo>
> >       <call target="checkoutModuleSrc"/>
> >
> 
> I assume based on your title "nested variables" you want to do something like
> this:
> 
> 
> <property name="ProjectName" value="${property::get-
> value('properties.project.Ord.ProjectName')}"/>
> 
> ?????
> 
> BOb
> 
> 
> 
> > Results of the script at the command line:
> > checkoutModuleSrc:
> >
> >      [exec] StarTeam 10.4 Command Line Interface, Build 10.4.8.36
> >      [exec] Copyright (c) 2003-2008 Borland Software Corporation. All
> > rights res erved.
> >      [exec] Using ini file: C:\Documents and Settings\All
> > Users\Application Data \Borland\StarTeam\ConnectionManager.ini
> >      [exec] Project not found: properties.project.Ord.ProjectName
> >
> > I would appreciate any help you can provide.
> >
> > Thanks,
> > -Doug Labout
> >
> >
> > The information contained in this electronic communication and any
> > document attached hereto or transmitted herewith is confidential and
> > intended for the exclusive use of the individual or entity named
> > above. If the reader of this message is not the intended recipient or
> > the employee or agent responsible for delivering it to the intended
> > recipient, you are hereby notified that any examination, use,
> > dissemination, distribution or copying of this communication or any
> > part thereof is strictly prohibited. If you have received this
> > communication in error, please immediately notify the sender by reply e-mail
> and destroy this communication. Thank you.
> 
> The information contained in this electronic communication and any document
> attached hereto or transmitted herewith is confidential and intended for the
> exclusive use of the individual or entity named above. If the reader of this
> message is not the intended recipient or the employee or agent responsible for
> delivering it to the intended recipient, you are hereby notified that any
> examination, use, dissemination, distribution or copying of this communication
> or any part thereof is strictly prohibited. If you have received this
> communication in error, please immediately notify the sender by reply e-mail
> and destroy this communication. Thank you.

Re: [NAnt-users] Nested variables

[Labout, D. <Dou...@ef...>]

Bob,
You are correct in that I'm trying to put together a couple of variables.
The build order is assigned to the variable ${properties.project.Ord}. I then append to the end of that variable the .ProjectName, .ViewName, and .Label and assign them to ${ProjectName}. I then pass $ProjectName to my starteam checkout.

The trouble is that ${properties.project.Ord} returns as "NETDLLS" but when I want the variable ${NETDLLS.ProjectName} to be returned as
"NETDLLs.ProjectName=Windows - .NET DLLs" it instead comes back as "NETDLLS.ProjectName".

StarTeam goes looking for a NETDLLS.ProjectName and of course can't find it and dies.

Thanks for the help!
Much appreciated!
-Doug

-----Original Message-----
From: Bob Archer [mailto:Bob...@am...]
Sent: Monday, June 17, 2013 9:22 AM
To: Labout, Douglas; 'nan...@li...'
Subject: RE: Nested variables

> Hello,
> I'm working on converting an Ant script to Nant and have ran into an
> issue with joining several variables together in Nant.
>
> Below is the original Ant script in which it pulls information from a
> properties file and uses the information to feed the build. The
> project starts by looping through build order (NETDLLS, App) and then
> uses that variable to prepend to the ProjectName to check out of StarTeam.
>
> Project.Build.Order=NETDLLs,App
>
> # Windows - .NET DLLs
> NETDLLs.ProjectName=Windows - .NET DLLs NETDLLs.ViewName=Windows -
> .NET DLLs
> NETDLLs.Label=201300722.20130508
>
> ANT script:
> <target name="build.project">
>       <property name="ProjectName"
> value="${buildProp.${project.Ord}.ProjectName}"/>
>       <property name="ViewName"
> value="${buildProp.${project.Ord}.ViewName}"/>
>       <property name="Label"
> value="${buildProp.${project.Ord}.Label}"/>
>
>       <antcall target="checkoutModuleSrc" inheritall="true"/>
>
> Here is what I have come up with in Nant which doesn't seem to be working.
>
> NAnt script:
> <target name="build.project">
>       <property name="ProjectName"
> value="${'properties.project.Ord'+'.ProjectName'}"/>
>       <property name="ViewName"
> value="${'properties.project.Ord'+'.ViewName'}"/>
>       <property name="Label"
> value="${'properties.project.Ord'+'.Label'}"/>
>       <echo>${ProjectName} ${ViewName} ${Label}</echo>
>       <call target="checkoutModuleSrc"/>
>

I assume based on your title "nested variables" you want to do something like this:


<property name="ProjectName" value="${property::get-value('properties.project.Ord.ProjectName')}"/>

?????

BOb



> Results of the script at the command line:
> checkoutModuleSrc:
>
>      [exec] StarTeam 10.4 Command Line Interface, Build 10.4.8.36
>      [exec] Copyright (c) 2003-2008 Borland Software Corporation. All
> rights res erved.
>      [exec] Using ini file: C:\Documents and Settings\All
> Users\Application Data \Borland\StarTeam\ConnectionManager.ini
>      [exec] Project not found: properties.project.Ord.ProjectName
>
> I would appreciate any help you can provide.
>
> Thanks,
> -Doug Labout
>
>
> The information contained in this electronic communication and any
> document attached hereto or transmitted herewith is confidential and
> intended for the exclusive use of the individual or entity named
> above. If the reader of this message is not the intended recipient or
> the employee or agent responsible for delivering it to the intended
> recipient, you are hereby notified that any examination, use,
> dissemination, distribution or copying of this communication or any
> part thereof is strictly prohibited. If you have received this
> communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.

The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.

Re: [NAnt-users] Nested variables

[Bob A. <Bob...@am...>]

> Hello,
> I'm working on converting an Ant script to Nant and have ran into an issue with
> joining several variables together in Nant.
> 
> Below is the original Ant script in which it pulls information from a properties
> file and uses the information to feed the build. The project starts by looping
> through build order (NETDLLS, App) and then uses that variable to prepend to
> the ProjectName to check out of StarTeam.
> 
> Project.Build.Order=NETDLLs,App
> 
> # Windows - .NET DLLs
> NETDLLs.ProjectName=Windows - .NET DLLs
> NETDLLs.ViewName=Windows - .NET DLLs
> NETDLLs.Label=201300722.20130508
> 
> ANT script:
> <target name="build.project">
>       <property name="ProjectName"
> value="${buildProp.${project.Ord}.ProjectName}"/>
>       <property name="ViewName"
> value="${buildProp.${project.Ord}.ViewName}"/>
>       <property name="Label" value="${buildProp.${project.Ord}.Label}"/>
> 
>       <antcall target="checkoutModuleSrc" inheritall="true"/>
> 
> Here is what I have come up with in Nant which doesn't seem to be working.
> 
> NAnt script:
> <target name="build.project">
>       <property name="ProjectName"
> value="${'properties.project.Ord'+'.ProjectName'}"/>

What are you trying to do here? The value you are going to get in project name is:

"properties.project.Ord.ProjectName"

I assume that is not what you want? When you put something in an expression in quotes it is a string literal, it won't be evaluated. Are you trying to get the value of properties.project.Ord.ProjectName and put it into project name? I really don't understand your snippet here.

Also, what line does that error occur on?

BOb


>       <property name="ViewName"
> value="${'properties.project.Ord'+'.ViewName'}"/>
>       <property name="Label" value="${'properties.project.Ord'+'.Label'}"/>
>       <echo>${ProjectName} ${ViewName} ${Label}</echo>
>       <call target="checkoutModuleSrc"/>
> 
> Results of the script at the command line:
> checkoutModuleSrc:
> 
>      [exec] StarTeam 10.4 Command Line Interface, Build 10.4.8.36
>      [exec] Copyright (c) 2003-2008 Borland Software Corporation. All rights res
> erved.
>      [exec] Using ini file: C:\Documents and Settings\All Users\Application Data
> \Borland\StarTeam\ConnectionManager.ini
>      [exec] Project not found: properties.project.Ord.ProjectName
> 
> I would appreciate any help you can provide.
> 
> Thanks,
> -Doug Labout
> 
> 
> The information contained in this electronic communication and any document
> attached hereto or transmitted herewith is confidential and intended for the
> exclusive use of the individual or entity named above. If the reader of this
> message is not the intended recipient or the employee or agent responsible for
> delivering it to the intended recipient, you are hereby notified that any
> examination, use, dissemination, distribution or copying of this communication
> or any part thereof is strictly prohibited. If you have received this
> communication in error, please immediately notify the sender by reply e-mail
> and destroy this communication. Thank you.