preventing plugin jar files from being expanded without using features [message #443610] |
Wed, 01 February 2006 21:24 |
Francis Upton IV Messages: 472 Registered: July 2009 Location: Oakland, CA |
Senior Member |
|
|
I have some JAR files that contain only data.
I would like these to be deployed in their unpacked state.
The only way I can find to do this is to use a feature to wrap the JAR file.
However, I don't want to use features because I want more granularity in
controlling the composition of my product. I use several of the Eclipse
plugins, but the plugins I use are in different Eclipse features, and I
don't want to get *all* of the plugins in all of these features. For
example, I use the base EMF plugin, but not the editing plugins, so I
don't want the entire EMF feature.
Actually, in typing this I realize I can just create a feature that
contains all of the eclipse plugins I use, so that's fine.
However, it would be nice to be able to specify somewhere at the plugin
level that you prefer the plugin to be packaged as a JAR.
Is this possible, or shall I make an enhancement request?
Thanks,
Francis
Platform UI Committer for Common Navigator
http://wiki.eclipse.org/index.php/Common_Navigator_Framework
http://help.eclipse.org/galileo/topic/org.eclipse.platform.d oc.isv/guide/cnf.htm
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03283 seconds