Community
Participate
Working Groups
I was writing an export wizard which had a zip file as output. I wanted to control the contents that were going into this file. I found the following class that did exactly what I needed to do: org.eclipse.ui.wizards.datatransfer.ZipFileExportOperation However, the above class has package level visibility, so I could not use it from my plug-in. In the end, I needed to copy the above code, plus the following classes which were also package protected: org.eclipse.ui.wizards.datatransfer.Base64Encoder org.eclipse.ui.wizards.datatransfer.DataTransferMessages org.eclipse.ui.wizards.datatransfer.ZipFileExporter The only class I really need to be public is the ZipFileExportOperation, but other people might find one of more of the above classes useful as well.
Looks like the class ZipFileExportOperation is now called ArchiveFileExportOperation in Eclipse 3.1 and above. But it's still not public. Hopefully we can do something to help out here. The Base64Encoder class was removed for 3.1 and the ZipFileExporter class was re-written: there is now TarFileExporter and ZipFileExporter classes, both of which are internal as of right now. It's tough to justify making an entire message class API. Is there a particular subset of the messages that you think should definitely be exposed or is it just a general thought that some of the messages could possibly come in handy for someone writing an export wizard?
It was just a general thought. All I really need is a simple API for writing resources from the workspace to a zip. In Eclipse 3.0.2, that class is ZipFileExportOperation. I would be comfortable with just having the high-level APIs public and leaving the internal implementation classes protected. I can just imagine other developers wanting even more control than myself, hence I suggested making some of the other APIs public as well.
"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.
