Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Question about buildDirectory and pluginPath
Question about buildDirectory and pluginPath [message #602923] Tue, 27 October 2009 13:21 Go to next message
Matthias Kohles is currently offline Matthias KohlesFriend
Messages: 71
Registered: July 2009
Member
Hey everyone,

i'm currently writing ant scripts to run a feature based headless build on a rcp application.

Now I have a small question about the properties "buildDirectory" and "pluginPath".

First, the buildDirectory specifies the location of the plugins/features, so they have to be located in buildDirectory/plugins and buildDirectory/features.

The problem now is, that i have splitted up the plugins and features in my buildDirectory. The core plugins/features are in the normal plugins/features directories and the plugins for testing are located for example in "plugins_test". Now i want to build all of the features/plugins, but to do this, i currently have to copy the plugins/features from "plugins_test" to "plugins" and so on, in order to get them built. Is there an easier way to do this and avoiding those copy operations???

Second question: For what exactly is the pluginPath property? I read the description but i don't get it. Can i specify the location of my plugins in "plugins_test" for example with this property to get them built?

regards

Matthias
Re: Question about buildDirectory and pluginPath [message #602928 is a reply to message #602923] Tue, 27 October 2009 14:24 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
pluginPath is a File.pathSeparator (';' or ':') separated list of paths.
This, together with buildDirectory forms a list of paths, where we
consider plugins found like this:

1) if <path>\plugins exists, then <path>\plugins\* are plugins
2) else if <path>\META-INF\MANIFEST.MF, or <path>\plugin.xml or
<path>\fragment.xml exit, then <path> is a plugin.
3) else if <path> is a folder, then <path>\* are plugins
4) else if <path> is a file ending in .jar, it is a plugin.

There is similar logic for features.

In your case, you want case (3), set pluginPath=plugins_test and
plugins_test/* will be found. This is comparable to setting pluginPath
to point to a workspace folder.

-Andrew

Matthias Kohles wrote:
> Hey everyone,
>
> i'm currently writing ant scripts to run a feature based headless build
> on a rcp application.
>
> Now I have a small question about the properties "buildDirectory" and
> "pluginPath".
> First, the buildDirectory specifies the location of the
> plugins/features, so they have to be located in buildDirectory/plugins
> and buildDirectory/features.
>
> The problem now is, that i have splitted up the plugins and features in
> my buildDirectory. The core plugins/features are in the normal
> plugins/features directories and the plugins for testing are located for
> example in "plugins_test". Now i want to build all of the
> features/plugins, but to do this, i currently have to copy the
> plugins/features from "plugins_test" to "plugins" and so on, in order to
> get them built. Is there an easier way to do this and avoiding those
> copy operations???
>
> Second question: For what exactly is the pluginPath property? I read the
> description but i don't get it. Can i specify the location of my plugins
> in "plugins_test" for example with this property to get them built?
>
> regards
>
> Matthias
Previous Topic:Override Variables Views on Debug Perspective
Next Topic:p2.gathering causing target does not exist error
Goto Forum:
  


Current Time: Fri Aug 14 02:18:47 GMT 2020

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

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

Back to the top