>
> On 10/17/07, *Felix Knecht* <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
> Pierre-Arnaud Marcelot schrieb:
> > Hi Felix,
> >
> > Well, the answer is: both...
> >
> > At the beginning at the project, when we started the build
> system, we
> > tried to use Maven first. Maven is really great for building
> jars but
> > building Eclipse plugins is very special. We couldn't find a way for
> > Maven to resolve the Eclipse dependencies of the plugins (like
> Eclipse
> > Core, Eclipse SWT for example).
>
For the dependencies stored in svn you can define a local repository to
use for maven. The directory structure would be equal to a remote maven
repo.
Definition of a local maven repo within the project.
<repositories>
<repository>
<releases>
<checksumPolicy>ignore</checksumPolicy>
</releases>
<snapshots>
<checksumPolicy>ignore</checksumPolicy>
</snapshots>
<id>provided.local</id>
<name>Locally Provided Repository</name>
<url>file:${project.basedir}/../dependencies</url>
</repository>
> >
> > It became even more difficult when we tried to build the RCP
> > application for each environment (Mac OS X Intel & PPC, Linux i386,
> > PPC, AMD64, and Windows i386) and incorporate the plugins in it.
> >
> > So, we turned to Ant+Ivy instead.
> >
> > I've already tried to move to Maven our build system several times,
> > but I could not find a way to make it work.
> >
> > For the 1.0 release, we've simplified the Ant+Ivy build system to be
> > easier to use to define a new Plugin, Feature, Help Plugin, or
> simple
> > utility Jar.
> > A common Ant script is inherited from each project specific
> build.xml
> > file. This common Ant script defines base tasks for building,
> > packaging, generating documentation, etc., that each project
> specific
> > build.xml file can override if it needs a special behavior.
> >
> > For a simple Eclipse Plugin, the build.xml file could look as simple
> > as this:
> > <project default="plugin">
> > <import file="../studio-build/build.xml"/>
> > </project>
> >
> > Since, the build system works well now, I think we'll stay like that
> > for a little while. But if you have links for building Eclipse
> plugins
> > and Eclipse RCP applications with Maven, I would love to read
> them... ;)
>
> Not yet, but I hope to find some time to figure it out.
> First I need to understand how the ant/ivy build works in detail. Can
> you give me a hint where Ivy has the configuration for dependencies?
>
> Felix
>
>
