Home » Eclipse Projects » Eclipse Platform » deploying plugin
| deploying plugin [message #29720] |
Sat, 10 May 2003 20:33  |
Eclipse User |
|
|
|
Originally posted by: christian.sell.netcologne.de
Hello,
next question: my plugin has a few additional jars it depends on, which
I have registered both in the java build path and in the plugin runtime
page. I can build my project, and run/debug it in the runtime workbench.
However, when I try to deploy it as a zip file (either via export or by
generating the ant file and executing the ant tasks), the generated zip
file only contains the jar file generated from compiling my source code.
None of the other resource directories (docs and such), nor the required
additional jars are included. Needless to say the resulting file is not
deployable as anything. I spent quite a while looking through the
options, and reading the docs (that didnt take long) - no clue. Anyone?
thanks,
Christian
|
|
|
| Re: deploying plugin [message #29724 is a reply to message #29720] |
Sun, 11 May 2003 01:41  |
| Eclipse User |
|
|
|
Originally posted by: cgoss..nixspam.madriver.com
I believe the answer to your question is the same one Richard Kulp suggested
in response to my recent "Deployable plug-ins and fragments" thread. I
quoth:
> You need to have in your build.propertise file something like:
> bin.includes = plugin.xml,jar1.jar,jar2.jar
> Where you list all of the files (relative to the root of the project)
> that should be copied other than the jar that is built from the source.
"Christian Sell" <christian.sell@netcologne.de> wrote in message
news:b9jnnn$dlc$1@rogue.oti.com...
> Hello,
>
> next question: my plugin has a few additional jars it depends on, which
> I have registered both in the java build path and in the plugin runtime
> page. I can build my project, and run/debug it in the runtime workbench.
>
> However, when I try to deploy it as a zip file (either via export or by
> generating the ant file and executing the ant tasks), the generated zip
> file only contains the jar file generated from compiling my source code.
> None of the other resource directories (docs and such), nor the required
> additional jars are included. Needless to say the resulting file is not
> deployable as anything. I spent quite a while looking through the
> options, and reading the docs (that didnt take long) - no clue. Anyone?
>
> thanks,
> Christian
>
|
|
|
| Re: deploying plugin [message #29740 is a reply to message #29724] |
Sun, 11 May 2003 11:06 |
 Christian Sell
Messages: 77
Registered: July 2009 |
Member |
|
|
erm, do you mean I have to manipulate the file by hand? Is this
documented anywhere? This looks like a rather broken concept.
thanks anyway,
Christian
Craig Goss wrote:
> I believe the answer to your question is the same one Richard Kulp suggested
> in response to my recent "Deployable plug-ins and fragments" thread. I
> quoth:
>
>
>>You need to have in your build.propertise file something like:
>> bin.includes = plugin.xml,jar1.jar,jar2.jar
>>Where you list all of the files (relative to the root of the project)
>>that should be copied other than the jar that is built from the source.
>
>
>
> "Christian Sell" <christian.sell@netcologne.de> wrote in message
> news:b9jnnn$dlc$1@rogue.oti.com...
>
>>Hello,
>>
>>next question: my plugin has a few additional jars it depends on, which
>>I have registered both in the java build path and in the plugin runtime
>>page. I can build my project, and run/debug it in the runtime workbench.
>>
>>However, when I try to deploy it as a zip file (either via export or by
>>generating the ant file and executing the ant tasks), the generated zip
>>file only contains the jar file generated from compiling my source code.
>>None of the other resource directories (docs and such), nor the required
>>additional jars are included. Needless to say the resulting file is not
>>deployable as anything. I spent quite a while looking through the
>>options, and reading the docs (that didnt take long) - no clue. Anyone?
>>
>>thanks,
>>Christian
>>
>
>
>
|
|
|
| Re: deploying plugin [message #29744 is a reply to message #29740] |
Sun, 11 May 2003 12:11 |
| Eclipse User |
|
|
|
Originally posted by: cgoss..nixspam.madriver.com
Yes its documented if well hidden. Look at PDE Guide / Deploying a plugin /
Deploying a feature / Build Configuration ... or just search your docs for
"bin.includes".
And yes, you have to modify build.properties more or less by hand. I say
'more or less' because there's an editor for the build.properties file that
allows you to click an 'Add' button to include any one of a fixed set of
properties, one of which is bin.includes. That isn't much help since you
still need to know what to do with bin.includes once you add it to the file.
In my opinion, editing by hand is easier and less error prone. Broken?
Maybe not 'broken' exactly since it works, but compared to other Eclipse
features that are well documented and easily manipulated via the UI,
bin.includes and its compatriots are at best oblique. Sounds like an issue
to take up with the Eclipse development team.
On the other hand, modifying bin.includes is simple. For example, the
following includes plugin.xml, the contents of a directory containing a
number of third-party jars, and a directory containing a series of
resources. You can get more specific if you wish and include individual
files. Easy, once you know what to do.
bin.includes = plugin.xml, myJars/, myResources/
"Christian Sell" wrote in message news:b9lasb$614$2@rogue.oti.com...
> erm, do you mean I have to manipulate the file by hand? Is this
> documented anywhere? This looks like a rather broken concept.
>
> thanks anyway,
> Christian
|
|
|
| Re: deploying plugin [message #29756 is a reply to message #29744] |
Sun, 11 May 2003 20:37 |
Christian Sell
Messages: 77
Registered: July 2009 |
Member |
|
|
to add a little more (probaly this should be a bug report in bugzilla)
1. the build.properties stuff is described, as you pointed out, under
"deploying a feature". I am mot deploying a feature, but only a plugin
2. the documentation says "This information can be indirectly updated in
the Runtime page of the manifest editor.". I had my additional libraries
registered in the runtime classpath - that did NOT have any effect on
the build.properties file.
Christian
Craig Goss wrote:
> Yes its documented if well hidden. Look at PDE Guide / Deploying a plugin /
> Deploying a feature / Build Configuration ... or just search your docs for
> "bin.includes".
>
> And yes, you have to modify build.properties more or less by hand. I say
> 'more or less' because there's an editor for the build.properties file that
> allows you to click an 'Add' button to include any one of a fixed set of
> properties, one of which is bin.includes. That isn't much help since you
> still need to know what to do with bin.includes once you add it to the file.
> In my opinion, editing by hand is easier and less error prone. Broken?
> Maybe not 'broken' exactly since it works, but compared to other Eclipse
> features that are well documented and easily manipulated via the UI,
> bin.includes and its compatriots are at best oblique. Sounds like an issue
> to take up with the Eclipse development team.
>
> On the other hand, modifying bin.includes is simple. For example, the
> following includes plugin.xml, the contents of a directory containing a
> number of third-party jars, and a directory containing a series of
> resources. You can get more specific if you wish and include individual
> files. Easy, once you know what to do.
>
> bin.includes = plugin.xml, myJars/, myResources/
>
>
> "Christian Sell" wrote in message news:b9lasb$614$2@rogue.oti.com...
>
>>erm, do you mean I have to manipulate the file by hand? Is this
>>documented anywhere? This looks like a rather broken concept.
>>
>>thanks anyway,
>>Christian
>
>
>
|
|
| |
Goto Forum:
Current Time: Fri Apr 19 17:04:08 GMT 2024
Powered by FUDForum. Page generated in 0.02086 seconds |
] 
Search
Help
Register
Login
Home
