Community
Participate
Working Groups
I was wondering if the packages being shipped should not define a product (see product extension point) thus allowing the first perspective to be opened to be controlled. I started looking into this and in order to have a similar experience to what packages have today (intro page, capabilities, etc.) the content of the org.eclipse.sdk plug-in would have to be copied into a plug-in owned by EPP.
Sounds like a good idea to me. There is another item on my list: config.ini - in the currently available packages it is the same for all of them. But I'm not sure if we should introduce such things like an own product before Europa. It would add more complexity to the package build, which is not yet as stable as I want it to be. Any opinions? How important is such a feature?
Created attachment 70587 [details] Branding plug-ins The attached archive contains 4 plug-ins each defining a package specific product thus allowing us to set the default perspective to be opened, some content intro content, activities, etc. The 4 plug-ins are a trimmed down version of the org.eclipse.sdk plug-in. A few other points - Some strings in the plugin.properties have not been adjusted to describe the package because I did not know what to put there. For example, on the welcome screen what should it say? Welcome to Eclipse 3.3 or welcome to "Eclipse Tools for Java Developer"? - The intro content is almost empty for most packages which is unfortunate. - Some packages probably do not have many activities, but this is to be verified.
This is something that we should keep in mind for future versions. For now (Europa) I changed the initial perspectives to Java, C, or J2EE in the plugin_customization.ini
*Very* old bug... since the package build changed completely and is based on the p2 it uses products internally and makes them available in the public EPP packages repository. Closing as fixed.
