Many thanks for your answer, it was exactly what I was looking for !!!!
I just works perfectly !!!!!

Manu

PDE/Build has an extension point where different map file entry format can be contributed. (This is where the support for SVN comes from).

Build provides a “COPY” extension. Your map file entry would look like:
plugin@org.eclipse.foo=COPY, ,
which results in a copy from root/element, if element is not specified, then you end up with copy from root/org.eclipse.foo

For any additional details, you’ll probably need to take a peek at the generated fetch script which results from using this.

Yes I looked at this property, but it seems Eclipse is building things directly in the pluginpath directory and doesn’t copy plugins found other there in the build directory. Do you confirm

More over we had troubles to have things working correctly for several heterogeneous environements (linux/windows, different paths) when using pluginpath, that is why we decided to copy all needed plugins in the build directory the same way Eclipse projects do by fetching from CVS ….

#pluginPath is a list of locations in which to find plugins and features. This list is separated by the platform file separator (; or
#a location is one of:
#- the location of the jar or folder that is the plugin or feature : /path/to/foo.jar or /path/to/foo
#- a directory that contains a /plugins or /features subdirectory
#- the location of a feature.xml, or for 2.1 style plugins, the plugin.xml or fragment.xml
pluginPath=