The goal of the Maynstall incubator project, pronounced May-install, is to provide extensible frameworks and an exemplary application to enable automated deployment of Eclipse-based product installations by building on services within Equinox and content exposed via update sites. The platform will be highly extensible, thus allowing it to be leveraged in multiple deployment modes, such as commercial software distribution, beyond those directly implemented within the project. Maynstall was formerly known as Maya.
Maynstall provides for automated distribution of the Eclipse platform as well as tooling and products built on top. The flow for Maynstall allows the user to launch a bootstrap which brings up a launcher. The launcher walks the user through a series of steps to allow them to choose a profile. The profile is then resolved to a series of instructions which the Maynstall server supplies to the launcher. The launcher executes the instructions thereby instantiating the desired target Eclipse environment.
Prior to having a release or milestone available for experimentation, contributors or developers can access Maynstall from it's CVS repository (once IP review complete). To facilitate getting started with Maynstall, we have setup some example plug-ins and provided instructions that leverage Derby in setting up a working installation of Maynstall. In addition, since the native bootstrap for Maynstall is not EPL friendly, while we work on an EPL version of the native bootstrap we have provided a Java version of the bootstrap to allow the full end-to-end experience to be tried by the user. Click Getting Started to try out Maynstall.
Detailed information on Maynstall can be found on the Maynstall Wiki as well as by reviewing the Maynstall Proposal. In preparation for creation review conference calls, an Architectural write-up is available off of the wiki.
