Bugzilla – Full Text Bug Listing
| Summary: | External tool builder link instead of copy | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Holger Machens <machens> |
| Component: | Debug | Assignee: | Platform-Debug-Inbox <platform-debug-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | chris, mober.at+eclipse, sarika.sinha, sven.koehler |
| Version: | 4.3 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=59289 | ||
| Whiteboard: | stalebug | ||
|
Description
Holger Machens
I understand the desired workflow, but I think the general design principle of Eclipse projects so far is, that they are always self-contained. The idea of a project referencing a tool from "somewhere on the outside" seems counter that design principle IMO. Therefore I would expect that the external tool builders must be copied/included in the respective projects. I would suggest that the Platform team finally fixes bug 59289 , and this one as WONTFIX. Disagree. It is not somewhere in the outer space. It is defined as globally available tool inside your workspace and can be referenced from projects for the universes best outcome! There is a way to define different JREs which are external too. Why would it not work for any type of external tool/library/whatever. It is one of the most basic functionalities of an IDE to integrate external tools - in a generic manner if done right. This issue (referring to the bug 59289) exists since I know Eclipse .. which is a long time. The actual problem is, that there is no one, who will ever implement it as you can see if you have a look at the CC list. There is you, some "chris" guy, someone who stalks me (SVEN! Why do you follow my feature requests?!) and finally me. No one who is in charge or willing to fix it .. it's just a lack of man-power. Thus, it is already on WONTFIX :P Cheers! (In reply to Holger Machens from comment #2) > (SVEN! Why do you follow my feature requests?!) Why not? I found this to be an interesting feature and I believe that at the time we discussed this, I had an issue that could be solved by this if it was implemented. Strong arguments :) Have you considered contributing a patch yourself ? - If, for example, you extend the dialog behind the "Import" button to offer a checkbox "Copy" which is on by default, then default behavior would be unchanged but you'd add your new feature. You'd also have to consider error handling during a build when your referenced builder doesn't exist in a workspace ... but over all, the complexity shouldn't be unmanageable. 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. -- The automated Eclipse Genie. If someone wants to contribute to the feature, we can look into it. This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag. |