Community
Participate
Working Groups
article at http://www7b.software.ibm.com/wsdd/library/techarticles/0309_bergschacher/bergschacher.html has been donated to eclipse, please include for Eclipse 3.0. See article for details.
Its a NICE FEATURE should be at ECLIPSE..
Due to legal reasons, the easiest way to contribute code to the Eclipse code base is to post it as an attachment to a bug report. Please ensure that the source is included in the attachment so the Eclipse team is able to migrate it into the current code base. Thanks.
I should note that this is pending time, resources, 3.0 plan, etc.
danberg@us.ibm.com (Daniel Berg) and schacher@us.ibm.com (Ritchie Schacher) have already contributed the code to Eclipse. I believe it is targeted for v3.0. They have already been in contact with the appropriate Eclipse persons etc .This bug# was was opened by me as a record of that activity.
The Eclipse contact needs to let us know if it's targeted for Eclipse 3.0 so we are able to adjust our team plans accordingly. Please have them annotate this bug report. Moving to Platform/UI for comments. Tod, let me know if this is in the plan for 3.0 and if there are any Core changes required. Thanks.
We have no plans to add any more features to Eclipse 3.0 but this is a good candidate for a contribution outside of the base Eclipse drops. We should decide on what to do in general about these sort of features.
Created attachment 7668 [details] Plugin w/Source, built from 2.1.2
This is something that we'd very much like to see in the eclipse base. We've had numerous customer requests to make this part of the platform. It makes a lot more sense for this to be owned by the platform owners in order that it will continue to work from one release to the next. It should take someone no more than a day or so to port this code to eclipse 3.0 and factor it cleanly. Note that some of the code is copied from core eclipse classes, simply because the base classes were private or because we wanted it to run in both 2.0 and 2.1.
I would stress that this get added to Eclipse 3.0 due to the very high customer appreciation of this feature. The feature greatly improves the usability of your import existing project action. This action is very limiting to many users because they want to be able to share content across workspaces without using an SCM. This feature allows a customer to export a set of projects to a zip file and then import the projects from the zip file into another workspace. This is much faster than exporting the zip to a location and then using your current action to import each project one at a time (extremely time consuming). Please see http://www7b.software.ibm.com/wsdd/library/techarticles/0309_bergschacher/bergs chacher.html for more details Again, I would strongly urge that you accept this feature into Eclipse 3.0.
Todd, is anything happening with this?
This is not currently on the 3.0 plan. Please also note that we are attempting a more lightweight set of funcationality in our plug-ins - new features that can be included as an optional upgrade (maybe through an update site) would be much more in line with what we are trying to do for 3.0
Will this optional lightweight feature provide the same functionality? What is the difference? The ability to zip up an entire workspace is important for me for 3 reasons. 1) When IBM support is resolving problems with WebSphere Studio products it is much easier to work with something that is a close as possible copy of a workspaces as possible to simulate the customer environment 2) In education classes, it is much more productive if a student can start with artifacts in the workspace rather than import in everything or create it. With a simple step of one import, a whole configured workspace could be started with and the lab exercise can spend more time focusing on what really matters. 3) Anyone who does not have a SCM between them that wants to share projects. While many customers have SCMs, there are still many times when one developer does not have access to the same code as another developer and would like to view their code and projects. They then try to copy workspaces around and this leads to all kinds of other problems. I know I already shown my desire for this feature by voting, but this an attempt to plead a case for reconsideration for inclusion in 3.0.
This is a super feature. I use it for L2 support, when a customer needs to send me a test case or when I'm developing or deliverying class material that has to be delivered to a diverse audience, either the class room or the internet. We can't always count on the student or the customer to have Clear Case or CVS and we need to get all the dependencies and meta data in one package because the applications are way beyond the Hello World with no dependencies. Jeff
Similar to Eric P's pleading I have to concur but from the perspective of our customers. Some of our major customers consider this a critical must have feature that should be part of the base Eclipse just as is the team api. How can not you see the parallelism with Team api...its just as fundamental in function. In the words of one large customer directed at me: "...please wake up and smell the roses (or coffee if you prefer :-) ..." This is practical day to day usage stuff...thats critical in a product that takes itself seriosuly. Given that you have the code..go for it. Lets please not get too carried away with the small is good philosophy and ignore what is a core requirement
I am assuming that since this is being pushed from a P3 to a P4 that it is not going to be included in Eclipse 3.0. This is a real shame especially since this request was opened on 10/15/2003. I don't know how much more lead time is required to make it into a release.
The issue is not how early you ask but if the PMC thinks this is a feature that they want in the base SDK or not. This was not on the 3.0 plan and would require PMC approval to make it into Eclipse which we are trying to reduce the size of.
Is this the correct place to take a requirement before the PMC? If not, what is the process to have this considered by the PMC and to get an outlook on when they will bring this feature in? Is there any record that indicates that this was even considered?
By marking this RESOLVED->WONTFIX, is this saying that this feature request is dead and that this will never make it into the platform? I'd like to reiterate Bob's earlier comments regarding the balance between lightweight and core functionality. I think this needs to stay open. If it is not going into 3.0, is should be considered for the next cycle.
Kevin Haaland was added to this Bug as he is a PMC member.
Reopening to mark later.
Marking for later consideration as requested.
Reopening now that 3.0 has shipped
We will not be adding this to SDK unless requested by the PMC.
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Prakash is now responsible for watching bugs in the [Wizards] component area.
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.
