| Deploy plugins: build errors [message #293498] |
Tue, 25 October 2005 04:10  |
Eclipse User |
|
|
|
Originally posted by: ja.fgomez.gmail.com
Hi
I've a problem with the Deploy Wizard.
My product works fine in the Eclipse IDE, but if I deploy it the build
fails.
1. ERROR in
D:\_work\GABP.Proteo.GUI.Plugin\src\bbva\gabp\gui\viewers\Fa stTreeContentProvider.java
(at line 8)
import bbva.gabp.structs.ITreeNode;
^^^^^^^^^^^^^^^^^
The import bbva.gabp.structs cannot be resolved
----------
2. ERROR in
D:\_work\GABP.Proteo.GUI.Plugin\src\bbva\gabp\gui\viewers\Fa stTreeContentProvider.java
(at line 64)
ITreeNode nodo = (ITreeNode) parent;
^^^^^^^^^
...
I've tried to create a feature and later deploy it, but also it failed.
In the feature I've sorted the plugins by build order.
Thanks
Jota
|
|
|
|
|
|
|
|
| Re: Deploy plugins: build errors [message #293581 is a reply to message #293560] |
Wed, 26 October 2005 11:54  |
| Eclipse User |
|
|
|
Originally posted by: Lamont_Gilbert.rigidsoftware.com
Mathieu Watel wrote:
> As my reply disappeared, I repaste it :P
>
> Make sure you have a manifest file for all plug-ins. Your plugin.xml
> should only contain 'extension' markups. The manifest.mf file is the one
> that contains informations about the bundle.
> Edit the manifest.mf file of each plugin and go to the 'Build' tab of
> the editor. In the section 'Runtime information', click on 'Add library'
> and for plug-in A put a name like A.jar or whatever you want. Click now
> on the 'Add folder' button, and select your source(s) folder(s).
> Then go to the runtime tab and check upon the 'Classpath' category.
> Click 'New' and enter the SAME name you entered previously. It means
> your plug-in will compile as a library into the JAR you specified and
> then it has to know this JAR for runtime.
> If the dependency between each of your plug-ins is well achieved, it
> should work. It not, explain your case in details, I would be glad to
> help (spent 3 days searching on how to do that).
>
I used to do it this way. Now on the 'Runtime information' part instead
of using plugin name I use '.'. This makes it deploy the plugin as
class files and not a single jar file. On the classpath part I leave it
blank since when deployed as classes there is no need to add jar file.
So I was doing just as you said, and was having the errors. I do
differently now, but have same errors, but errors are false as the
deploy actually works.
My case is simple as explained. Plugin B depends on plugin A. Plugin A
depends on nothing. Plugin A deploys fine. Plugin B deploys with bunch
of errors about not findine the clases that should have been provided by
plugin A, but it actually does deploy.
CL
|
|
|
|
| Re: Deploy plugins: build errors [message #293585 is a reply to message #293581] |
Wed, 26 October 2005 12:09 |
| Eclipse User |
|
|
|
Originally posted by: mathieu.watel.axlog.fr
Ohhh I forgot. Your plug-in A should list the exported packages. It is
done by opening the manifest file and working into tab 'Runtime', section
'Exported packages'. But as you don't seem to have any runtime compilation
error, you may already did that.
|
|
|
Powered by
FUDForum. Page generated in 0.09476 seconds
Home