9 Replies Latest reply on Feb 14, 2004 12:25 AM by Sherman Wood

    Installshield, commit done

    Noel Rocher Apprentice

       

      "noel.rocher" wrote:
      Hi all,

      I committed the installshield (in the distrib module).

      To make it run :


      - build nukes as I need some nukes lib components
      - go to distrib and run build
      - then run build deploy-installer
      - run installer webapp : http://127.0.0.1:8080/nukes-installer/install



      this version uses the sample-setup.xml file in WEB-INF directory.

      My work now is to create all setup.xml for the modules and to take into account your comments.



        • 1. Re: Installshield, commit done
          Viet Master

           

          "cooper" wrote:
          great it looks very professional


          • 2. Re: Installshield, commit done
            jae Master

             

            "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
              Sherman Wood Apprentice


              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 Apprentice

                 

                "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
                  Sherman Wood Apprentice


                  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
                    Dennis Przybyla Novice

                    Why are you not letting the EJB create the tables when it is deployed?

                    • 7. Re: Installshield, commit done
                      Viet Master

                      we don't just need creation of tables, we also need management, i.e deletion, etc...

                      • 8. Re: Installshield, commit done
                        Noel Rocher Apprentice

                         

                        "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
                          Sherman Wood Apprentice


                          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