dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

Hi Bob.

I'll have to look at this, but as far as I can tell (and I'm not
> really the world's java expert) you can't really tell the java source
> code to pick which jre it wants to use.  Kind of like the adage about
> children not being able to pick their parents.  By the time that code
> is running its kind of too late.


Duh. Good point.


>  I guess the only thing which can be
> done (and maybe this is what you mean) is to change settings in the
> launch4j config file.  But again this can't really be done at install
> time ..... unless of course the launch4j packaging of the "exe" is
> actually done as an install step.  I guess this might be possible but
> it starts to get hairy.  Off the top of my head:
> 1.  launch4j would need to be bundled in the installer package by bitrock
> 2.  bitrock would need to be clever enough to modify launch4j config file
>


This is possible. But, my idea was to modify this  during the actual build
of the installer. So, I was thinking that BitRock would modify the pom.xml
of the DHIS2 live app, build it, and then package it. Once we do the build,
BitRock can revert the file back to its original condition.  Once we create
a custom version of the Live EXE specifically for the BitRock install,
without influencing what is on trunk, as if we hard code the JRE (which
needs to be done in the pom of the Live app). Of course, we can do this on
trunk, but this would be bad ,as if others are using the Live app, it would
not work.


Not sure about those other points. I was thinking that the Live app would be
compiled as part of the installer build process, with a special version of
the Live app.


> I'm trying to understand again why we want to do this.  If we are
> indeed bundling a jre then can't we set that jre as the one to be used
> as part of the build process of dhis2-live.exe?  Someone remind me why
> we want to do this at install time?
>

We are talking about the user machine here. The idea about packaging a JRE
is to ensure that a valid one is there. If we place it in the DHIS2 install
directory, and hard code the DHIS2 live exe file, then we can be sure it is
using one that is correct. Capiche?

JPP



> Regards
> Bob
>
> > Regards,
> > Jason
> >
> >
> >
> >>
> >>
> >> Knut
> >>>
> >>>
> >>>>
> >>>> I must say though, I am still a bit confused why we are not
> considering
> >>>> the H2 approach more? I have an installer already for this, and it
> works
> >>>> like a charm, at least on a stock XP machine.
> >
> > I still think that for a typical district install, H2 should suffice. I
> > hope. We need to test it, as there are some definite advantages.
> >>>
> >>> Well its a good point. I can only say that postgres is more proven,
> more
> >>> people have knowledge about it, it provides better supportive
> applications
> >>> (pgadmin), and I have experienced problems with importing large amounts
> of
> >>> data with H2. But H2 is improving and we will definitely have "full H2
> >>> compliance" as a goal.
> >>>
> >>>>
> >>>> I have taken a look at .embedding the JRE which is simple, but it
> would
> >>>> require a change to the DHIS2 Live app, which of course would break
> other
> >>>> DHIS2 live installs that may not use the embedded JRE that we would
> package
> >>>> with the installer. We could alter the Live app source code at the
> builder
> >>>> compile time, to suit the needs of the installer. Better yet, would be
> a
> >>>> config file for the app that we could write during the installation,
> which
> >>>> could read the JRE location. Maybe we could use this for other
> properties,
> >>>> like memory settings as well.
> >>>>
> >>>
> >>> Yeah I'm sure we (Bob?) could do some magic here and the JRE is only 15
> >>> mb. So I'll say we go for it.
> >>> Lars
> >>>
> >>> _______________________________________________
> >>> Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> >>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> >>> Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
> >>
> >>
> >> --
> >> Cheers,
> >> Knut Staring
> >
> >
> >
> > --
> > --
> > Jason P. Pickering
> > email: jason.p.pickering@xxxxxxxxx
> > tel:+260968395190
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> > Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~dhis2-devs<https://launchpad.net/%7Edhis2-devs>
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
>



-- 
--
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+260968395190