Home » Eclipse Projects » Rich Client Platform (RCP) » Feature-based application export
| Feature-based application export [message #443962] |
Tue, 07 February 2006 13:32  |
Eclipse User |
|
|
|
Folks,
After reading the documentation and a couple of books, I'm still a little
confused as to how this works - and I'm not able to get it to work. I
have written a plug-in that works when run from Eclipse and now I am
trying to package/export it. I created a feature per the instructions
(rcp tutorial, D'Anjou et al. book). I then created a product file in the
plug-in that includes my feature and eclipse.rcp in the configuration.
Using a -clean eclipse start up, I synchronize and then launch the product
and get the error
!ENTRY org.eclipse.osgi 2006-02-07 11:11:05.531
!MESSAGE Bundle update@E:/JavaPg/mschmidt.PgClient/ [3] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2006-02-07 11:11:05.531
!MESSAGE Missing required bundle org.eclipse.ui.intro_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2006-02-07 11:11:05.531
!MESSAGE Missing required bundle org.eclipse.help.base_0.0.0.
Yet .intro and help.base are included in the feature dependencies and also
in the plug-in build file.
More generally, here is what I don't understand.
1. Is there documentation on what should be included in a plug-in build?
I know to include the content I created (help table of contents and html
files, intro content, icons, images, custom configuration). But what of
the various Eclipse files (manifest.mf, .classpath if it isn't customized,
build.xml, plugin.xml, .project, .product)? And you don't include the src
directory?
2. It seems odd that one does branding (about text, windows icons) in
plugin.xml and then does the same branding again in the product file. Is
this right?
3. Some of the references I have indicate to create an Ant build file but
this isn't mentioned in the on-line rcp tutorials. Is this a change from
Eclipse 3.0 to 3.1?
4. The product Export page mentions to include the RCP delta pack - is
this just eclipse.rcp?
Thanks for your continued help in reducing my ignorance. These questions
are probably pretty basic, but I always make a good-faith effort to read
documentation before asking.
|
|
| |
| Re: Feature-based application export [message #444165 is a reply to message #443962] |
Fri, 10 February 2006 03:57  |
| Eclipse User |
|
|
|
Michael Schmidt wrote:
> 1. Is there documentation on what should be included in a plug-in
> build? I know to include the content I created (help table of contents
> and html files, intro content, icons, images, custom configuration).
> But what of the various Eclipse files (manifest.mf, .classpath if it
> isn't customized, build.xml, plugin.xml, .project, .product)? And you
> don't include the src directory?
Honestly you do very much in one step, e.g. I have not a single
experience concerning intro contents and help (html) files, although we
are quite satisfied with our currently simple branding situation.
I assume that you have already read the articles:
http://www.eclipse.org/articles/Article-RCP-1/tutorial1.html
http://www.eclipse.org/articles/Article-RCP-3/tutorial3.html
http://www.eclipse.org/articles/Article-Branding/branding-yo ur-application.html
A valuable source of links and short information is provided on
http://wiki.eclipse.org/index.php/Rich_Client_Platform
Concerning your error: Please note that starting your exported app with
-clean does not a **full** clean of all persisted information - I
stumbled across this fact during Eclipse 3.0/3.1 development: To rule
out any artefacts you should definitely delete **all** subdirs and
contents of the configuration dir of your exported product (**except**
the config.ini!) and start the deployed product again.
> 2. It seems odd that one does branding (about text, windows icons) in
> plugin.xml and then does the same branding again in the product file.
> Is this right?
Unfortunately, I have not tested it, whether removing some of the
redundant parts of either .product file and the product ext. pt. do
work. AFAIK the .product file is **not** part of the exported product,
so although the information is duplicatedly hold at two places they
don't seem redundant (Someone here to correct me?). I don't like this
situation either, but I assume, that this has some historic reasons and
might be based on the way the export process works, which needs some of
these informations to create the executable and related files. Some of
the redundancy can be minimized by taking advantage of externalized
strings (for about text etc.).
> 3. Some of the references I have indicate to create an Ant build file
> but this isn't mentioned in the on-line rcp tutorials. Is this a change
> from Eclipse 3.0 to 3.1?
I'm not aware of the need of an additional ant build file. The article
http://www.eclipse.org/articles/Article-Branding/branding-yo ur-application.html
mentions a build script, but AFAIK the need for it is outdated provided
you use the new .products file, because the export mechanism uses its
information (app name, icons) to generate the properly named executable
+ incorporated .ico files (under Windows).
But my tip is: If you want to configure the built-in About dialog with
format arguments (version number etc.) you do need a about.mappings
file, which provides the proper argument mapping.
HTH,
Daniel Krügler
|
|
|
Goto Forum:
Current Time: Mon Jul 07 12:01:21 EDT 2025
Powered by FUDForum. Page generated in 0.06142 seconds |
Home