The .NET code required to create a windows service is minimal, and therefore
it would be fairly trivial to decouple it from the Autonomy core.
Additionally there are a couple of places in the VSS and DevEnv integration
that use the registry. We have no need for these modifications but if
anybody submits the changes we will integrate them.
I'm not sure exactly how a web-app version would work. Obviously it would
be possible to manually start builds via a web interface, but how would it
poll the repository and automatically kick off builds when a change is
detected?
If you want to discuss this further, then we should probably take it to
autonomy's dev list. Subscription info can be found on
http://www.chive.com/products/autonomy.
MG
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-admin;lists.sourceforge.net]On Behalf Of Griffin
Caprio
Sent: 23 October 2002 04:44
To: 'Graeme Humphrey'; [EMAIL PROTECTED]
Subject: RE: [nant-dev] NAnt Build Server
The discussion of which open-source license is the best is a religious
battle I don't think should be touched on here ;)
However, the last time I checked Autonomy, it was still running
as a windows
service. Not only would I prefer a web-app version, but running as a
service severely limits the portability of autonomy.
Any plans to make two versions? or be able to pick which way its run?
-Griffin
---
This sf.net emial is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0002en
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers