+1 for looking at ProvisioningHelper. Good catch.
So the summary is that we get some simplified "API" and a command line
application in the director bundle and then the installer becomes the
UI version.
ProvsioningHelper does do some stuff that is not director related but
its not clear that it is all needed. In any event, we should review.
Jeff
Pascal Rapicault wrote:
Beyond the actual simplicity (sparness?) of it is an issue of size
and the ability to only bring down what is absolutely required.
While you are at it, I would also take a close look at the
ProvisioningHelper class and the SimpleDirector class as they seem to
have some non-trivial overlap with the code you seem to be looking at.
 Jeff McAffer
---03/09/2008 09:24:19 AM---Hey Scott,
Hey Scott,
Yes, the installer and director are very similar. IMHO these should
combined somehow. The challenge will be to keep the installer simple.
The idea there is that it is really just an example of what you could
do. We are not looking to make it be the all singing all dancing
installer to beat all installers. Having said that, the director is
also similarly simple so combining the two would make sense.
do you have a feel for the functional overlap? Are there things that
one
does that the other does?
Another option is to put the headless part of the installer in the
director app (inthe director bundle) and leave the UI part in the
Installer bundle. That way people wanting headless stuff can just use
the director app and the installer becomes a UI thing. This would
mean
pushing down a couple things like the install description etc. Not
sure
how much code that would be.
Jeff
Scott Lewis wrote:
> Hi folks,
>
> I'm working with the installer, with the notion of using it for
webapp
> update/install.
>
> I'm aware of the director application and have used it in the
past.
> Are there any plans to merge the director application and
installer
> application? In some ways they seem simila...i.e. specifying
> artifact, meta-data repos, profiles, etc via command line
[director]
> or a properties file [installer]...or both using p2 underneath.
> Is there any plan/thought/desire to merge them into one
> application...or do they have different use cases and/or
functionality?
>
> Thanks,
>
> Scott
>
>
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
|
