Tomas,
That's a good point -- I can imagine that each included external library adds
potential complications.
You can get the full discussion on the various ways of accessing MySql via the .NET
Frameowork at http://www.mysql.com/articles/dotnet/index.html. The short version is
that it's possible to use OleDb but not supported, and no instructions are given; ODBC
is recommended and documented. Both OleDb and ODBC require drivers to be installed on
the client, and ODBC would still require a similar refactoring of the SqlTask.
To me, the client drivers are the killer, meaning yet another piece of software I have
to get my development team to install and configure, and since they're already saddled
with .NET, VJ#, NUnit, NAnt, and a few other tools, I'd like to make things as simple
as possible for the end users of NAnt. So I checked out the MySQLNet native provider
and found it to come in very smoothly (except for the SharpZipLib version mismatch
which I mentioned earlier).
If the general concensus is that we want to minimize external libraries in the
NAntContrib general release, maybe we should split NAntContrib into a number of
SourceForge packages. The SourceForge download page then could look something like
the Ant External Tools and Tasks page (http://ant.apache.org/external.html).
Any thoughts on this? Too much work? Is there any way to set up CVS module-level
security on SourceForge so, for example, I could have commit rights to a SqlEx module
but not other modules?
Just throwing around some thoughts. If the patch gets disregarded for simplicity's
sake, I'll get over it. :)
- Jason
-----Original Message-----
From: Tomas Restrepo [mailto:[EMAIL PROTECTED]
Sent: Wed 2/26/2003 9:03 PM
To: Jason Pettys; NAntC-Dev
Cc:
Subject: Re: [NAntC-Dev] NAntContrib Release - MySql patch
Hi Jason,
Quick question here...
What does this bring to the table, that using a OLEDB provided didn't? (I
don't know crap about MySql so please excuse my ignorance :))
I ask because I, for one, am not thrilled about having to distribute yet
another external thing with nantcontrib. If we think all of this is important, then
I'd seriously consider giving a look at abstractado.net and use that instead....
- -
Tomas Restrepo
[EMAIL PROTECTED]
----- Original Message -----
From: Jason Pettys <mailto:[EMAIL PROTECTED]>
To: NAntC-Dev <mailto:[EMAIL PROTECTED]>
Sent: Wednesday, February 26, 2003 3:28 PM
Subject: RE: [NAntC-Dev] NAntContrib Release - MySql patch
Any thought of including the expanded SqlTask code I submitted? I
guess it may cause a little trouble because the MySql data providers use a newer
version of SharpZipLib than NAnt does. I overcame the problem by rebuilding NAnt and
NAntContrib with the newer version.
Anyway, I'd like to see it make it in eventually, as I think it adds a
lot of value and flexibility to the task. So I'll just bring it up every once in a
while until someone tells me to stuff it :)
- Jason Pettys
-----Original Message-----
From: Scott Hernandez [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 26, 2003 2:19 PM
To: NAntC-Dev
Subject: [NAntC-Dev] NAntContrib Release based on 0.8.1
I think we should do a release. We should now state that
NAntContrib uses NAnt 0.8.1 and run with it...
Does that work for everyone?
(This means we no longer build NAntContrib with the cvs
version of NAnt.)
N隊X'u)Y\gbH zG( 4
&z�x%M{B{khlqzm?X( ~zwXb?r&z�
