Assuming the servletbridge jar is in your repo and dependency list, try
something like this:
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<phase>process-resources</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<excludeArtifactIds>servletbridge</excludeArtifactIds>
<outputDirectory>${project.build.directory}/${
project.build.finalName}/WEB-INF/eclipse</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<warSourceIncludes>WEB-INF/lib/servletbridge*.jar</warSourceIncludes>
</configuration>
</plugin>
You can find the details of these plugins, but above is one way to do it:
http://maven.apache.org/plugins/
Please, let me know how it works out!
Eric
On 7/30/07, George Stragand <[EMAIL PROTECTED]> wrote:
>
> With Eclipse 3.3, the temptation to use the osgi plugin framework is huge,
> and we would really like to utilize the osgi framework within our web app.
> Differences exist between the classic layout of a web app and where the
> osgi
> bundles exist (the Eclipse plugin jars existing under WEB-INF/eclipse
> instead of WEB-INF/lib, etc.). The only jar in the WEB-INF/lib is
> servletbridge.jar (OK, that makes me twitch that there isn't a version on
> that jar out of Eclipse; guess I am too used to the logical approach of
> Maven).
>
> Main question is how to create the same war from an automated Maven build
> as
> Eclipse does. The PDE Maven plugin doesn't appear to do this. Anyone
> else
> attempting to create an osgi war from Eclipse and Maven at the same time?
>
> I'd rather not leave the "build" in Eclipse (IDE's doing builds also makes
> me twitch!). The ability for the build machine to have unexpected
> versions
> of plugins is a risk, and we would really like the ability to recreate a
> build from source control and Maven as we do with other war deliverables.
>
> Thanks.
>
--
Eric Redmond
http://blog.propellors.net
