Thanks Ben 

If you start it from a command window it will not close when done. (I almost 
always keep a Command Window open. anyway)

Better yet. 
Make a shortcut and pre-pend the command line in the "target" textbox with 
"cmd.exe /k " then mark SVN to add it to the ignore list so it does not get 
committed.  I will make a private script that updates and then builds by 
calling the new Update script and then the BuildDotNet script

As far a M2 is concerned I would be more inclined to take the pauses out and 
then the BuildDotNet script can be called from other scripts. This will be 
useful when we go to an automated daily build for all the trees.

Thanks for verifying the commit!!
Drew

 

________________________________________
From: Scott Golightly [[email protected]]
Sent: Tuesday, May 26, 2009 4:23 PM
To: Stonehenge Development
Subject: RE: [jira] Resolved: (STONEHENGE-63) Cleanup Dotnet Build Script

Drew,



I have tested it on a couple of VPCs. It works fine and rebuilds the the source 
code even when I ran it from a different starting directory. One minor 
complaint, I opened a command window and ran it from there. Upon finishing it 
closed the command window so I had to start another command window to run the 
RunServices.bat file to start the services. I would prefer that it not close 
the command window but I think that could be a M2 fix.



Scott Golightly

> From: [email protected]
> To: [email protected]
> Date: Tue, 26 May 2009 12:30:06 -0700
> Subject: RE: [jira] Resolved: (STONEHENGE-63) Cleanup Dotnet Build Script
>
> Could someone please verify this before I close it?
> Shankar doe it meet requirements?
> Thanks!
> Drew
>
>
> -----Original Message-----
> From: Andrew (Drew) (JIRA) [mailto:[email protected]]
> Sent: Tuesday, May 26, 2009 12:25 PM
> To: [email protected]
> Subject: [jira] Resolved: (STONEHENGE-63) Cleanup Dotnet Build Script
>
>
> [ 
> https://issues.apache.org/jira/browse/STONEHENGE-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
>
> Andrew (Drew) resolved STONEHENGE-63.
> -------------------------------------
>
> Resolution: Fixed
> Assignee: Andrew (Drew)
>
> Fixed
>
> > Cleanup Dotnet Build Script
> > ---------------------------
> >
> > Key: STONEHENGE-63
> > URL: https://issues.apache.org/jira/browse/STONEHENGE-63
> > Project: Stonehenge
> > Issue Type: Task
> > Components: DOTNET_BS, DOTNET_CLIENT, DOTNET_OPS
> > Affects Versions: M1
> > Environment: DotNet
> > Reporter: Andrew (Drew)
> > Assignee: Andrew (Drew)
> > Priority: Blocker
> > Fix For: M1
> >
> > Original Estimate: 2h
> > Remaining Estimate: 2h
> >
> > The build file for the .NET code assumes that the code is being built from 
> > SVN, and tries to update the current directory. This is not appropriate for 
> > a source code archive, which should be self-contained (apart from any 3rd 
> > party dependencies, which should be documented.).
> > The build file should check that any required environment variables are set 
> > up and exit with an error if not. Also any required settings should be 
> > documented somewhere, preferably in the script as well as in the top-level 
> > README or BUILDING file.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>

Reply via email to