[pde-dev] Re: does "dependencies not satisfied" just relate to plug-in-p

[Steinar Bang <sb@xxxxxx>]

>>>>> Steinar Bang <sb@xxxxxx>:

> I get the following message when doing a PDE build on a .product with
> plugin-dependences:

> generateScript:
> [eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.

> ...and then noting more.  Ie. no list of plug-ins with unsatisfied
> dependencies. 

The pdeProductFilename setting of pde-maven-plugin, eg.
     <configuration>
      <pdeProductFilename>plugins/com.somecompany.myproj.studio.app/myapp.product</pdeProductFilename>
      ...
     </configuration>
was not enough.  It must be specified in the 
buildConfiguration/build.properties file as well, like this:
 product=/com.somecompany.myproj.studio.app/myapp.product

The pde-maven-plugin requires that the file is there, that it is
non-empty, and that it is a well formed XML file.  If not, the
pde-maven-plugin denies that the project is a PDE project.

But but the pde-maven-plugin does not actually read the values the PDE
build needs from that file.  For that the product file must be specified
in build.properties.