ProjectViewer's "archive project" action only supports compressing projects into a
jar file, including options to add a manifest and ignore .java files. This is very
java-centric and not terribly useful.
I think PV should scrap the name "archive project" and provide several different methods to "export" a project, possibly as a service provider for other plugins, but not necessarily. A standard "compress to zip" option would be more universal than archiving as a jar, and then two jar options could be supported: a standard one, and an executable one.
As one possible scenario, PV could come with just a "compress to zip" export option and provide exporting as a service. Then a number of different java-specific export options could be defined by JavaSideKick or a new plugin (e.g. JavaProject), such as jar, executable jar, javadoc, etc.
As a counterpart to exporting, being able to import an archived project would also be handy. As an example, right-clicking on a group would provide an "import project here" action that would prompt for the archived project and a target directory. PV would then unzip the project to that location and import all the files into a new project.
|Submitted||kog13 - 2010-10-28 - 00:25:22z||Assigned||nobody|
|2010-10-29 - 02:52:00z
|This is the kind of functionality that can be completely developed outside of PV,
and plugged into the PV UI through its extension mechanism. In fact, that's the preferred
way of doing this kind of stuff.
The current "archive" functionality in PV only exists because years ago, when I added it, I couldn't find the owner of the JarMaker plugin (which was broken), so I integrated it into PV. I wouldn't mind at all if it was taken out again, the same way that I'd prefer to have the app association stuff in its own separate plugin (Launcher? was supposed to be it but I don't think it's ready yet).