Eclipse Community Forums: Plugin Development Environment (PDE) » Question about buildDirectory and pluginPath

Help

Home

Home » Eclipse Projects » Plugin Development Environment (PDE) » Question about buildDirectory and pluginPath

Show: Today's Messages :: Show Polls :: Message Navigator

Question about buildDirectory and pluginPath [message #493648]

Tue, 27 October 2009 13:21

Matthias Kohles

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

Report message to a moderator

Re: Question about buildDirectory and pluginPath [message #493681 is a reply to message #493648]

Tue, 27 October 2009 14:24

Andrew Niefer

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

Report message to a moderator

Re: Question about buildDirectory and pluginPath [message #493821 is a reply to message #493681]

Wed, 28 October 2009 08:06

Matthias Kohles

Messages: 71
Registered: July 2009

Member

Thanks for your reply Andrew,

Consider the following Directory structure:

<buildDirectory>/plugins
<buildDirectory>/features
<buildDirectory>/plugins_test
<buildDirectory>/features_test

For default, the plugins in "plugins" will be built, which is case 1 in your post. Now if i set the pluginPath property it will have no effect or will it? because if case 1 is "executed", it will never goes to case 3??? Or will it built both plugin directories???

Sorry, i don't understand it right now.

Matthias

Report message to a moderator

Re: Question about buildDirectory and pluginPath [message #493875 is a reply to message #493821]

Wed, 28 October 2009 10:50

Matthias Kohles

Messages: 71
Registered: July 2009

Member

update:

i just tried it out and everything worked fine.

Thank you andrew for your help Smile

best regards

Matthias

Report message to a moderator

Re: Question about buildDirectory and pluginPath [message #493975 is a reply to message #493821]

Wed, 28 October 2009 15:56

Andrew Niefer

Messages: 990
Registered: July 2009

Senior Member

We are working on a list of directories, if you have
buildDirectory=<buildDirectory>
pluginPath=<buildDirectory>/plugins_test;<buildDirectory>/features_test
(use ':' on linux)
Then the list has 3 entries, <buildDirectory> gets the plugins &
features, and the 2 pluginPath entries get the other folders.

-Andrew

Matthias Kohles wrote:
> Thanks for your reply Andrew,
>
> Consider the following Directory structure:
>
> <buildDirectory>/plugins
> <buildDirectory>/features
> <buildDirectory>/plugins_test
> <buildDirectory>/features_test
>
> For default, the plugins in "plugins" will be built, which is case 1 in
> your post. Now if i set the pluginPath property it will have no effect
> or will it? because if case 1 is "executed", it will never goes to case
> 3??? Or will it built both plugin directories???
>
> Sorry, i don't understand it right now.
>
>
> Matthias

Report message to a moderator