| Export Feature produces empty bin directory [message #465236] |
Mon, 26 March 2007 11:23  |
Eclipse User |
|
|
|
I am implementing a plugin, and need to:
1)Build the plugin in our batch developer builds.
2)Create a software update site in our product kit (that includes
many other stuff). This way, our users would install our kit, and
then point the Eclipse update manager to the software update
site/directory in the installation, and update the plugin from there.
The above two things have one thing in common. I need to build the plugin
into a jar file.
So, from reading various things, I concluded that the way to do this is to
create a feature that includes my plugin, and then export the feature.
This would give me the jar file and some build file that I can stick into
our build scripts.
But, when I do this, I get an empty bin directory in the plugin
subdirectory of the build directory!! I do have the bin directory checked
off in the plugin project as a directory to include in a binary build.
Also, the "Save as Ant script" in the Export dialog (of the feature),
produces this ant script:
<project default="feature_export" name="build">
<target name="feature_export"/>
</project>
What do I do with this ant script?
Thank you.
|
|
|
|
| Re: Export Feature produces empty bin directory [message #465245 is a reply to message #465236] |
Mon, 26 March 2007 15:19  |
| Eclipse User |
|
|
|
Never mind... sigh.
Once I edited the plugin's build.properties to include the bin directory,
exporting the feature did produce a jar with all the plugin's stuff.
Also, don't forget to enumerate in bin.includes everything that you want
in the jar file. So, if you have .jar files, have a *.jar in the list.
Sorry for the false alarm.
|
|
|
Powered by
FUDForum. Page generated in 0.04531 seconds
Home