Home » Eclipse Projects » Eclipse Platform » building update site
| building update site [message #323168] |
Wed, 12 December 2007 16:57  |
Eclipse User |
|
|
|
Originally posted by: hammer.fmi.uni-passau.de
Hi,
I've got a problem when building the update site: I get errors which
are obviously due to the build path, though the plugins build without
problems in eclipse and running them in a runtime workbench works
perfectly. I've set up the plugin build path with the PDE Tools.
Any ideas?
Thanks,
Christian
|
|
| |
| Re: building update site [message #323181 is a reply to message #323173] |
Thu, 13 December 2007 08:47  |
| Eclipse User |
|
|
|
Originally posted by: aboehlke.vitras.de
> Hi,
> You can create an update site project in your workspace, and associate
> all features (feature projects) to the update site projects. When you
> do an export on the update site project, things will be taken care for
> you automatically.Hello AL,
Thanks for providing this simple solution! There is one little problem:
Eclipse extracts some features and plugins and modifies them (Why?). This
raises the problem, that some of the JARs generated by the Update Site
Builder are not signed correctly, so the features/plugins cannot be
installed!
As a quickfix, I just deleted all ECLIPSE.RSA/ECLIPSE.SF files. But
perhaps, we should tell the Update Site Builder, how to handle this?
Thanks again.
Greetings,
André Böhlke
|
|
|
| Re: building update site [message #323182 is a reply to message #323173] |
Thu, 13 December 2007 09:16 |
| Eclipse User |
|
|
|
Originally posted by: hammer.fmi.uni-passau.de
Hi,
Thanks for your proposal, however, the problem arises when I let
eclipse build the update site (and thus the feature and the plugins
within). I get build path errors in the logs.zip that I do not get
during the build process in eclipse. Does the build path differ during
feature building?
Eclipse Version: 3.3.1.1
Build id: M20071023-1652
Thanks,
Christian
On 2007-12-12 22:05:02 +0100, AL <unbonnevie@yahoo.com> said:
> Christian Hammer wrote:
>> Hi,
>>
>> I've got a problem when building the update site: I get errors which
>> are obviously due to the build path, though the plugins build without
>> problems in eclipse and running them in a runtime workbench works
>> perfectly. I've set up the plugin build path with the PDE Tools.
>>
>> Any ideas?
>> Thanks,
>> Christian
>>
> Hi,
>
> You can create an update site project in your workspace, and associate
> all features (feature projects) to the update site projects. When you
> do an export on the update site project, things will be taken care for
> you automatically.
|
|
|
| Re: building update site [message #323192 is a reply to message #323182] |
Thu, 13 December 2007 18:31 |
 Alex Le
Messages: 649
Registered: July 2009 |
Senior Member |
|
|
Christian Hammer wrote:
> Hi,
>
> Thanks for your proposal, however, the problem arises when I let eclipse
> build the update site (and thus the feature and the plugins within). I
> get build path errors in the logs.zip that I do not get during the build
> process in eclipse. Does the build path differ during feature building?
>
> Eclipse Version: 3.3.1.1
> Build id: M20071023-1652
>
> Thanks,
> Christian
>
> On 2007-12-12 22:05:02 +0100, AL <unbonnevie@yahoo.com> said:
>
>> Christian Hammer wrote:
>>> Hi,
>>>
>>> I've got a problem when building the update site: I get errors which
>>> are obviously due to the build path, though the plugins build without
>>> problems in eclipse and running them in a runtime workbench works
>>> perfectly. I've set up the plugin build path with the PDE Tools.
>>>
>>> Any ideas?
>>> Thanks,
>>> Christian
>>>
>> Hi,
>>
>> You can create an update site project in your workspace, and associate
>> all features (feature projects) to the update site projects. When you
>> do an export on the update site project, things will be taken care for
>> you automatically.
>
>
Can tell what the errors in the logs are? There is a 90% chances that
errors are due to a plugin (in one of your features) that references a
*.jar; that is, that plug-in has an embedded jar file, if you were to
export out that plug-in.
That was my experience in the past, and it was painful. But not impossible.
If that is the case, try first to export out that plug-in itself and
test it by putting it in your eclipse installation "plugins" directory.
If the plug-in works, then you're fine. If not, somewhere in this
newsgroup there is a thread on how to make sure the plug-in manifest
recognizes embedded jar files.
|
|
|
| Re: building update site [message #333392 is a reply to message #323192] |
Tue, 09 December 2008 01:19 |
John J. Barton
Messages: 311
Registered: July 2009 |
Senior Member |
|
|
AL wrote:
> Christian Hammer wrote:
>> Hi,
>>
>> Thanks for your proposal, however, the problem arises when I let
>> eclipse build the update site (and thus the feature and the plugins
>> within). I get build path errors in the logs.zip that I do not get
>> during the build process in eclipse. Does the build path differ during
>> feature building?
>>
>> Eclipse Version: 3.3.1.1
>> Build id: M20071023-1652
>>
>> Thanks,
>> Christian
>>
>> On 2007-12-12 22:05:02 +0100, AL <unbonnevie@yahoo.com> said:
>>
>>> Christian Hammer wrote:
>>>> Hi,
>>>>
>>>> I've got a problem when building the update site: I get errors which
>>>> are obviously due to the build path, though the plugins build
>>>> without problems in eclipse and running them in a runtime workbench
>>>> works perfectly. I've set up the plugin build path with the PDE Tools.
>>>>
>>>> Any ideas?
>>>> Thanks,
>>>> Christian
>>>>
>>> Hi,
>>>
>>> You can create an update site project in your workspace, and
>>> associate all features (feature projects) to the update site
>>> projects. When you do an export on the update site project, things
>>> will be taken care for you automatically.
>>
>>
>
> Can tell what the errors in the logs are? There is a 90% chances that
> errors are due to a plugin (in one of your features) that references a
> *.jar; that is, that plug-in has an embedded jar file, if you were to
> export out that plug-in.
I added an embedded jar file to a plugin and now my site.xml fails to
build.
Ignore this next paragraph and skip down....
The errors in logs.zip are nonsense on so many levels. logs.zip wow??
why compile to build the site at all? how can you have errors if the
plugin builds in the IDE?
>
> That was my experience in the past, and it was painful. But not
> impossible.
>
> If that is the case, try first to export out that plug-in itself and
> test it by putting it in your eclipse installation "plugins" directory.
> If the plug-in works, then you're fine. If not, somewhere in this
> newsgroup there is a thread on how to make sure the plug-in manifest
> recognizes embedded jar files.
What does it mean "export out that plug-in itself"?
|
|
| | | | |
Goto Forum:
Current Time: Thu Apr 25 10:41:40 GMT 2024
Powered by FUDForum. Page generated in 0.03630 seconds |
] 
Search
Help
Register
Login
Home
