Bugzilla – Full Text Bug Listing
| Summary: | Allow to save export actions in a "launch" config | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Aaron Digulla <digulla> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | curtis.windatt.public, remy.suen |
| Version: | 4.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
|
Description
Aaron Digulla
I don't see the export wizard ever becoming a launch configuration. Typically people create pde build ant scripts to do regular building/publishing tasks. Note that the export wizard has an option to "Save as Ant script" which will create an ant build file you can use to repeat the process from an ant launch configuration. Then let me put this into a new context: If I wanted to build a new version of the Eclipse IDE (or maybe the BIRT designer), where would I have to look for this script? Does it have a fixed name? Or does the containing project have a fixed name? My goal is to make it more simple for newbies to build Eclipse projects. In the past, I've fixed bugs in Eclipse plug-ins by downloading the source and the JAR, unpacking the JAR, compiling the patched classes against the JAR, packaging the JAR with the same name and copying the result into the plugins/ directory of Eclipse. That was the only reliable way I found to do this. Is it possible to add a task to the release train which says "every product that you can download from eclipse.org must contain everything necessary to build it from scratch"? (In reply to comment #2) > Then let me put this into a new context: If I wanted to build a new version of > the Eclipse IDE (or maybe the BIRT designer), where would I have to look for > this script? Does it have a fixed name? Or does the containing project have a > fixed name? You select a location to put the ant script in the export wizard. > My goal is to make it more simple for newbies to build Eclipse projects. In the > past, I've fixed bugs in Eclipse plug-ins by downloading the source and the > JAR, unpacking the JAR, compiling the patched classes against the JAR, > packaging the JAR with the same name and copying the result into the plugins/ > directory of Eclipse. Exporting a project from the workspace with the default options should get you a built, jarred plug-in. Because Eclipse uses p2 to manage the installed bundles, it is now much more difficult to replace bundles in the running Eclipse. The steps you described are a hack that others have used. You can also create a Feature Patch project to replace one version of a plug-in with another. To make it easier for users to patch Eclipse in this fashion, PDE added a new option in the export. We also added an awesome feature to help get source for Eclipse bundles. The steps for patching your own Eclipse install are now: 1) Have the necessary plug-ins in your target platform (the default target platform has everything you have installed in your IDE) 2) Go to Import > PDE > Plug-ins and Fragments 3) Select the last radio button, "Projects from a Repository" 4) Find the plug-ins you want, they will be checked out from the CVS repository (assuming your installed bundles have the special EclipseBundleSource header) 5) Edit the code, use PDE launching to self host and test. 6) Go to Export > PDE > Deployable Plug-ins and Fragments 7) Choose the last destination "Install into host." This will export your modified plug-in, create a feature patch and install them into your current Eclipse instance. > Is it possible to add a task to the release train which says "every product > that you can download from eclipse.org must contain everything necessary to > build it from scratch"? It would be great if the typical user could build Eclipse locally, but this has proven to be difficult (though I don't know the technical limitations). You can try filing a bug against Community / Cross-Project. 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. If the bug is still relevant please remove the stalebug whiteboard tag. |