Haven't been able to follow this thread much (at the hospital with my
newborn :-) )

Just wanted to remind folks that installer config .xml drives the website
badge installer as well as enables the auto-update mechanism for the
Installer.

Thanks,
Om
On Jan 11, 2014 10:58 PM, "Alex Harui" <aha...@adobe.com> wrote:

> Update:  I've adjusted this plan a bit.  There were issues like the
> installer.xml wants a basedir.  I could copy it into the destination
> directory and run it from there, but then I have to not overwrite it when
> expanding the package.  Also, the installer.xml wants to load some
> properties from files.
>
> However, what I want to know before the package is expanded is the
> licensing information which shouldn't rely on basedir.  So my new plan is
> to create installer-config.xml files with the licensing info and we'll put
> those next to the release packages.  Then the installer can pick that up
> early, offer up the licenses, then expand the package and run the
> installer script inside.
>
> Let me know if you see any problems with this approach,
>
> -Alex
>
> On 1/10/14 2:25 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>
> >Hi,
> >
> >> Interesting.  So we'd put the installer.xml files up separately on a
> >> server somewhere as part of release distribution?
> >
> >Could be either -  but outside the zip with the release distribution
> >seems fine to me.
> >
> >Thanks,
> >Justin
>
>

Reply via email to