This content has been marked as final.
Show 9 replies
-
1. Re: Installshield, commit done
julien1 Jan 11, 2004 5:50 PM (in response to noel.rocher)"cooper" wrote:
great it looks very professional -
2. Re: Installshield, commit done
jae77 Jan 23, 2004 8:07 PM (in response to noel.rocher)"jae77" wrote:
wow - looks great, but i was unable to get it to create any of the tables. is that portion still not fully working, or am i doing something wrong? -
3. Re: Installshield, commit done
sgwood Feb 9, 2004 7:39 AM (in response to noel.rocher)
Working off the CVS snapshot as of the 7th, I see there are some setup.xmls around in the modules, but the installer does not look for them. Noel, are you still working on it? I have the Postgres ones done.
Sherman -
4. Re: Installshield, commit done
noel.rocher Feb 9, 2004 10:03 AM (in response to noel.rocher)"sgwood" wrote:
Working off the CVS snapshot as of the 7th, I see there are some setup.xmls around in the modules, but the installer does not look for them. Noel, are you still working on it? I have the Postgres ones done.
Sherman
Hi Sherman,
I didn't make setup.xml for postgresql because several modules didn't have one.
But I didn't work on it last weeks. I will look at it.
BTW, look at the hsqldb & mysql setup.xml files to see if you are able to produce yours. I think its very simple. -
5. Re: Installshield, commit done
sgwood Feb 10, 2004 7:10 AM (in response to noel.rocher)
Hmmm, I said that I have them done and ready. Do you want them? How do I get the changes to you?
I also changed a few things in the installer so that Postgres appears as an option as a DB type in the datasource screen.
What about the issue with the installer needing to look into the available modules to work out what modules to present as options to install?
Sherman -
6. Re: Installshield, commit done
thepriz Feb 13, 2004 12:51 AM (in response to noel.rocher)Why are you not letting the EJB create the tables when it is deployed?
-
7. Re: Installshield, commit done
julien1 Feb 13, 2004 5:09 AM (in response to noel.rocher)we don't just need creation of tables, we also need management, i.e deletion, etc...
-
8. Re: Installshield, commit done
noel.rocher Feb 13, 2004 11:52 AM (in response to noel.rocher)"sgwood" wrote:
Hmmm, I said that I have them done and ready. Do you want them? How do I get the changes to you?
Hi all,
Sherman, do you have a write access to CVS to put the postgresql setup.xml files for some (or maybe all) modules ?
PostgreSQL can't be used in Installshield if core setup.xml files are not in nukes project. The best would be to have them for all modules.
If you know well PostgreSQL you can do it easily.
If you don't have a write access to CVS, please ask Julien ("cooper") for it."sgwood" wrote:
I also changed a few things in the installer so that Postgres appears as an option as a DB type in the datasource screen.
great"sgwood" wrote:
What about the issue with the installer needing to look into the available modules to work out what modules to present as options to install?
Sherman
The module list is built from setup.xml files that are concatenated at build time in one (one by database type).
Hope this help -
9. Re: Installshield, commit done
sgwood Feb 14, 2004 12:25 AM (in response to noel.rocher)Sherman, do you have a write access to CVS to put the postgresql setup.xml files for some (or maybe all) modules ?
I have them for all modules. I'll ask Julien about getting CVS access.The module list is built from setup.xml files that are concatenated at build time in one (one by database type).
I am not seeing this behavior. In the nukes.installer.war, I see a copy of what was in distrib/src/resources/nukes-installer-war/WEB-INF/database with the subdirectories of each database type. There is no concatenation of setup.xmls from other modules. I would think that the build.xml for distrib should use the module discovery process of the main build script to discover what modules are available, and merge them in.
Sherman