Problem with pluginPath (headless build) [message #49223] |
Wed, 04 March 2009 17:55 |
Eclipse User |
|
|
|
Originally posted by: birt.lewold.at
I have a very strange problem:
I have multiple plugins. To keep it simple assume PluginA depends on PluginB
Because of various reasons I don't want to build them in the same buildDirectory. (main
reason is, that two running headless builds conflict with each other if they use the same
buildDirectory).
So I build them in separate build directories and copy the resulting plugins into
/MyBuildResults/plugins
in build.properties i specify
pluginPath=/MyBuildResults
When building PluginB it seems to find PluginA (during "generateScript" it checks for
missing plugins, and PluginA is not listed there .... if I delete PluginA it gets listed).
But .... I get "the import cannot be resolved" ERRORs for all my classes in PluginA.
If I would build everything in the same plugin directory things work correct.
Can anyone out there enlighten me what I am doing wrong?
Chris
|
|
|
Re: Problem with pluginPath (headless build) [message #49232 is a reply to message #49223] |
Thu, 05 March 2009 07:35 |
Eclipse User |
|
|
|
Originally posted by: birt.lewold.at
First of all I want to correct a simple thing:
Of course I meant that PluginB depends on PluginA.
I found out some otherr thing ....
This does not work .....
/MyBuildResults/plugins/PluginA_1.1.0.20080303.jar
If I unpack the plugin so that it looks like
/MyBuildResults/plugins/PluginA_1.1.0.20080303 (folder containing the JARs contents)
Then everything works as expected.
Please please someone tell me I am doing something severely wrong.
Why does pluginPath not pick up plugin JAR files ??????
Chris
Chris wrote:
> I have a very strange problem:
>
> I have multiple plugins. To keep it simple assume PluginA depends on
> PluginB
>
> Because of various reasons I don't want to build them in the same
> buildDirectory. (main reason is, that two running headless builds
> conflict with each other if they use the same buildDirectory).
>
> So I build them in separate build directories and copy the resulting
> plugins into
>
> /MyBuildResults/plugins
>
> in build.properties i specify
> pluginPath=/MyBuildResults
>
> When building PluginB it seems to find PluginA (during "generateScript"
> it checks for missing plugins, and PluginA is not listed there .... if I
> delete PluginA it gets listed).
>
>
> But .... I get "the import cannot be resolved" ERRORs for all my classes
> in PluginA.
>
>
> If I would build everything in the same plugin directory things work
> correct.
>
>
> Can anyone out there enlighten me what I am doing wrong?
>
> Chris
|
|
|
|
Re: Problem with pluginPath (headless build) [message #49381 is a reply to message #49351] |
Thu, 05 March 2009 11:20 |
Eclipse User |
|
|
|
Originally posted by: birt.lewold.at
I checked that ... PluginA is contained in the classpath.
I think I figured out the source of the problem .....
PluginA is a plugin wrapping a "plain old java JAR file" and exporting the classes
contained there (using the Runime page in the Manifest editor).
It seems that the eclipse build process is not able to resolve such types of plugins.
Chris
Manuel Selva wrote:
> Hi,
>
> May be you can have a look at the generated build.xml file for the
> plug-in B which doesn't compile. Mainly you should check the @dot target
> in charge of compiling the plug-in, check the classpath attribute here
> to be sure that A is there ...
>
> Manu
>
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.24633 seconds