Bugzilla – Full Text Bug Listing
| Summary: | Document (or update?) "how to set up IDE dev env" for our current code base | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Dirk Fauth <dirk.fauth> |
| Component: | Releng | Assignee: | Platform-Releng-Inbox <platform-releng-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | daniel_megert, david_williams, Lars.Vogel |
| Version: | 4.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 422762 | ||
|
Description
Dirk Fauth
We only update the BREE on a per-bundle basis as needed. PW Dirk, is what you are seeing due to you simply not having all the "Installed Java Runtimes" defined in your preferences (and/or "execution environments" associated with one?) ... or, do you have all that defined, and you still see "compliance inconsistencies". I know occasionally I see cases where people update that bundle's BREE but they forget to update the .classpath and/or project compliance settings. If you are seeing the latter, I think this is a valid bug since is a "barrier to entry" ... but, if you are just thinking all BREEs should be the same level then that won't happen (and, in that case I think this would be a "won't fix" bug, since we do it that way intentionally). Though I suppose we could also "transform" this bug into enhancement on better documenting "how to" set up development environment. Thanks! I don't have all the JREs installed and configured. I don't see a need for configuring a 1.4 nowadays. :) I thought having a baseline for all projects would be a good idea. If that matches not the project baseline, then close this bug as WONT FIX. I will contribute an update if I see that it is necessary like it was for core.services. And yes, some documentation on how to setup an environment would be great. Cost me quite a while to get things running. Instead of literal "won't fix" (though that's true for original issue) I'll transform this into a "document" enhancement and move to releng. (Just thought it'd be nice to have a record of the motivation). We might already have something on the wiki, but I know a lot of that is now obsolete ... so we'll be sure to track the need. It would be reassuring if the instructions started from a blank slate, i.e. no Java installed, no Eclipse installed, and then built upon that to set up a fully functional development environment that can compile the code without errors. In addition, having the answers to questions like these would have been helpful: - How many versions of Eclipse are needed? (at least 2, 1 older for API Baseline and 1 for developing on) - How many Eclipse installations should you make? (at least 3, 1 for API Baseline, 1 for all your plugins, 1 as Target Platform) - How to properly sandbox your workspaces setup so that changes to files and folders that tests make stay inside it? - How many Java versions are needed? (not sure about the answer to this one, 1.7, 1.6?, ...?) - How to recover your old Sun account from Oracle to unlock the Java 6 download? (didn't succeed with this one) - Is this old Java 6 installer that I just downloaded from some website safe to run? (SmartScreen didn't complain so I guess it was) (In reply to Dirk Fauth from comment #0) > IMHO this should be updated to use Java 1.6. Most of the e4 plug-ins have been upgrade to Java 1.6. If you see platform plugins which still should be upgraded, please open a separate bug from them. Paul also updated our "How to contribute wiki". I mark this bug as FIXED. |