Community
Participate
Working Groups
Creators of a given type of project should be able to "hook into" its checkout. Use case: User create a J2EE project (using, e.g., the Dynamic Web Project in Corona) named "foo". The creation wizard offers (default=accept) to create an EAR project=fooEAR referencing foo. This allows the user to deploy/test foo more easily. After completion, user checks foo in. Some time later, user checks out foo for maintenance into a blank workspace. User makes changes, and seeks to test the changes, but cannot deploy/test without an EAR project. User must run the EAR project wizard. It Would Be Nice if checkout was sufficiently extensible that, on checkout of a J2EE project, the user could be offered to create an EAR. It Would Be Nicer if the checkout process' view and control code was sufficiently extensible that folks who write extensions to project-creation wizards could just "hook in" appropriate project-creation-extension pages/operations to the checkout UI/operations.
The CVS checkout is currently extendable in the following situation only: - there is no .project in the repository - the user performs a Checkout As on a single project and chooses the option to configure the project using the new project wizard. This will bring up the New project wizard and allow the user to create a new project of any type. Once the project is created and configured, the contents from the repository are checked out into the project. I'll admit that this isn't ideal but any improvements would require support from the UI for configuring existing projects. Moving to UI for comment.
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
