On 1/15/07, Steinar Bang <[EMAIL PROTECTED]> wrote:
>>>>> "Barrie Treloar" <[EMAIL PROTECTED]>:
> See http://docs.codehaus.org/display/MAVENUSER/Eclipse+Plugin
> For steps on how to:
> * Build an internal repository containing the plugins from an Eclipse
> installation
> * Add the Eclipse RCP artifacts to your internal repository
A question: why is this step (adding RCP artifacts) needed? Won't the
RCP artifacts be copied together with the rest of the eclipse platform?
You may need to explain what you mean, I'm not understanding.
The PDE build (since it just uses the Eclipse Ant PDE build under the
covers) will find your local installation of the Eclipse jars and
correctly create a zip file with everything your RCP application
requires.
The PDE Build will work with an Eclipse Target Platform, which is a
separate directory than your Eclipse installation, that contains just
the RCP base platform and any plugins that your RCP application
depends upon.
The question is: How do you automate creating an Eclipse Target Platform?
Without deploying the Eclipse RCP artifacts into a maven repository
there is no easy way to do this. With them deployed you follow the
instructions at "Create an Eclipse RCP Target" to automate creation.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
