Check out JNI Registry at www.trustice.com/java.directory.shtml (ICE Engineering)
Regards, Terry ----- Original Message ----- From: "Steve Loughran" <[EMAIL PROTECTED]> To: "Ant Users List" <[EMAIL PROTECTED]> Sent: Thursday, November 21, 2002 12:35 PM Subject: Re: Ant Featured in Out-of-the-Box > > ----- Original Message ----- > From: "Eric Weidner" <[EMAIL PROTECTED]> > To: "Ant Users List" <[EMAIL PROTECTED]> > Sent: Wednesday, November 20, 2002 5:05 PM > Subject: Re: Ant Featured in Out-of-the-Box > > > > On Windows, we use InstallShield to initially drive the installation, > > call out to other Windows installers (e.g., JDK, Apache, MySQL, WinCVS, > > etc.), update the registry as needed, and finally kick off our master > > Ant script to do the bulk of the installation (e.g., > > extracting/decrypting/copying/moving files, regex replacements, CRLF > > fixes, calling other Ant-based installs, running JUnit/HttpUnit, > > processing XML docs with XSLT, creating/updating properties files, > > creating and populating databases, building and deploying J2EE apps, > > etc.). There are actually one or two places that we have Ant call Java > > code to create/update some Windows environment variables via JNI, but > > it's fairly simple and well-contained. > > > > On Linux, we use Ant to do it all because there's no need for registry > > manipulation. We have Ant ask the user for input up front (e.g., where > > to install, DNS setup, user ID/password, etc.) then do all the rest > > without further user interaction. > > > > so what you are saying is we need a <regedit> task for java, which creates a > regedit file and then execs regedit. An interesting thought... > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
