Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Problem with pluginPath (headless build)
Problem with pluginPath (headless build) [message #49223] Wed, 04 March 2009 17:55 Go to next message
Eclipse UserFriend
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 Go to previous messageGo to next message
Eclipse UserFriend
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 #49351 is a reply to message #49223] Thu, 05 March 2009 09:36 Go to previous messageGo to next message
Manuel Selva is currently offline Manuel SelvaFriend
Messages: 189
Registered: July 2009
Location: Grenoble, France
Senior Member
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


Re: Problem with pluginPath (headless build) [message #49381 is a reply to message #49351] Thu, 05 March 2009 11:20 Go to previous messageGo to next message
Eclipse UserFriend
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
>
Re: Problem with pluginPath (headless build) [message #50081 is a reply to message #49381] Tue, 10 March 2009 19:25 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=157375

The problem is basically that the java compiler can't compile against
nested jars. So they will need to be extracted first.
PDE/Build doesn't (yet) do this extraction automatically.
-Andrew

Chris wrote:
> 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
>>
Re: Problem with pluginPath (headless build) [message #592769 is a reply to message #49223] Thu, 05 March 2009 07:35 Go to previous message
Chris is currently offline ChrisFriend
Messages: 97
Registered: July 2009
Member
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 #592794 is a reply to message #49223] Thu, 05 March 2009 09:36 Go to previous message
Manuel Selva is currently offline Manuel SelvaFriend
Messages: 189
Registered: July 2009
Location: Grenoble, France
Senior Member
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


Re: Problem with pluginPath (headless build) [message #592808 is a reply to message #49351] Thu, 05 March 2009 11:20 Go to previous message
Chris is currently offline ChrisFriend
Messages: 97
Registered: July 2009
Member
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
>
Re: Problem with pluginPath (headless build) [message #593093 is a reply to message #49381] Tue, 10 March 2009 19:25 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=157375

The problem is basically that the java compiler can't compile against
nested jars. So they will need to be extracted first.
PDE/Build doesn't (yet) do this extraction automatically.
-Andrew

Chris wrote:
> 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
>>
Previous Topic:Versioning on dependent features?
Next Topic:headless p2 director application
Goto Forum:
  


Current Time: Wed Jun 16 14:52:32 GMT 2021

Powered by FUDForum. Page generated in 0.01957 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top