This was one of the most heavily discussed project creation reviews.
The EPP project expects to have downloads for Java developer (J2SE), Java
Enterprise developer (J2EE), C/C++ developer and RCP developer.
We discussed relationship between the EPP and Eclipse Update Manager
(EUM). EPP is to help create smaller downloads that are relevant to
different user profiles. The EUM is to enable upgraded features to
download to user and / or to add new features. EPP will provide a
framework to make it easier to create smaller targeted downloads, e.g.,
report developer. So, even if EUM was perfect, without EPP we would not
have the capability to download a bootstrap / minimal set of relevant
modules and will need to download the entire monolithic package.
EUM is different from installer that will be provided as part of EPP.
Currently, users new to Eclipse need to follow step-by-step instructions
to download relevant projects (e.g., C/C++ developers). The installer that
is part of EPP will automate the installation of relevant projects for the
new user.
The philosophy is: smaller is better. So, no optional packages will be
included, e.g., a stripped down download for Java developers that 80% of
Java developers would want. However, given the packaging framework that
will be developed as part of EPP, customized downloads for other targets
(e.g., report developer) could be developed.
EPP will not add new capabilities to existing projects; merely package the
relevant ones into a meaningful download for the target user.
There?s a potential issue in that a Java developer could download one
package and decide at a later time that they need the C/C++ package also.
The developer may expect that C/C++ download installs into his existing
version of Eclipse / Java but that will likely not work due to version
issues. This problem is out of scope for EPP. We need to bite off one
problem at a time and not bite off more than we can chew.
Could the emphasis on small targeted downloads result in too many
confusing options for new users? Downloads will be shown on second level
after a user has chosen processor / OS combination ? so, there will only
be a few options at that level. In addition, good descriptions of
downloads can reduce confusion.
How does EPP relate to EasyEclipse? At some level, they both help with
download ? so, they are competing solutions. EasyEclipse packages projects
from outside Eclipse; EPP does not plan on doing that. For example, C/C++
developers may want Eclipse, compiler, runtime but Eclipse cannot do that
for legal reasons (if the compiler is GPL, e.g.) Doug Schafer (CDT lead)
thought that EPP creates a confusion for C/C++ developers and plans to
work with EasyEclipse.
What is the decision making for what targeted profiles and which projects
are included in the download. The committers will decide this initially.
Once the package creation framework is in place, broader adoption will
hopefully result. The expectation is that downloads will be aligned with
yearly releases (Europa, etc.)