Re: [platform-update-dev] Non plug-in data that is part of a feature

["Foster, Susan B" <susan.b.foster@xxxxxxxxx>]

Dejan,

I have the following in my feature.xml file:

 <data
         id="zipFiles/somefile.zip"
         download-size="0"
         install-size="0"/>

And I have the following in my feature's build.properties file:

bin.includes = feature.xml,\
               zipFiles/


And I have a features directory in my com.xyz.update.  When I create
com.xyz.feature_1.0.1\zipFiles\somefile.zip under that directory, the
update works fine.

If you export the same feature to a zip file instead of a JAR file, and
then unzip it into eclipse, the /zipFiles/somefile.zip is created
without any extra effort.  In _either_ case, the zipFiles directory is
in the archive, JAR or zip; when I when include the zipFiles directory
in the feature the resulting JAR file is 3987 Kb and when I don't
include it is 2 Kb

So you are saying that when you export the feature to a JAR file you
must then manually go into the  com.xyz.update/features directory and
create the directory structure and files there, as well as creating them
in the com.xyz.features project (which you need to do to incude them in
the feature)?  Isn't that inconsistent with the way you include non
source file in a plugin project (example icons that need to be available
to wizards and the like)?  If you have extra files in there that you
want to be in the resulting plugin you add them to the plugin's
build.properties file:

bin = icons/,\ 
      plugin.xml

and they are included in the feature without any extra effort on the
developer's part. 

It would seem to me that you wouldn't want to have to do things
differently when you export a feature via zip file and JAR file.

Susan
email: susan.b.foster@xxxxxxxxx
phone: 480-552-0927