Eric, Here is a trimmed down POM with the basic elements used to facilitate the assembly, along with the Maven assembly descriptor.
Keep in mind that this is based upon a POM I created to build uPortal 2.5.3 with its directory structure unchanged, so that it could be incorporated into a larger Maven2 build. It should at least be a decent example to get you started. Feel free to ping me if you have any questions. The Assembly plugin can be a bit tricky, although they have improved the documentation recently. Good luck, Brad On Thu, 2007-08-16 at 20:51 -0500, Eric Dalquist wrote: > That would be wonderful, could you just attach them to an email in this > thread? That sounds like a good approach to generating the final > artifact to deploy. > > -Eric > > Brad Szabo wrote: > > Hi Eric, > > > > I utilize the Maven Assembly plugin to create a Tomcat overlay archive > > (zip file in my case) which allows for easy extraction of items into > > various Tomcat directories as needed... webapps, common, conf etc... > > > > I can contribute the POM configuration and the assembly descriptor if > > you are interested. > > > > Thanks, > > Brad > > > > On Thu, 2007-08-16 at 17:15 -0500, Eric Dalquist wrote: > > > >> I'm working on mavenizing the trunk of uPortal and have run into a few > >> questions I'd like to pose to the group. > >> > >> The big one is packaging. Using maven for build management really lends > >> itself to generating an EAR since it allows multiple WARs (uPortal and > >> each portlet app) and shared libraries. For uPortal 3 sandbox > >> development we already have an EAR -> Tomcat deployer tool which puts > >> the WARs and JARs in the correct locations. > >> > >> The problem with the EAR approach is it does not (as far as I can tell) > >> allow for differentiation of what libraries are shared by just the WARs > >> (pluto) and what libraries need to be shared with the servlet container > >> (jdbc driver for JNDI datasource). > >> > >> I'm not quite sure what to do about this. We don't really need to use > >> JNDI for the DataSource in the quickstart / out of the box configuration > >> but providing a way to do it without having to come up with a custom > >> development process would be very good. > >> > >> Discussion and suggestions are both welcome. > >> -Eric > >> > > > > > > -- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <modelVersion>4.0.0</modelVersion> <!-- | This stripped down POM file contains an example of elements | needed to use the Maven Assembly plugin to generate a Tomcat | overlay archive. +--> <properties> <uportal.webapp.context>uPortal</uportal.webapp.context> <uportal.webapp.contextFile>uPortal55.xml</uportal.webapp.contextFile> <build.artifact.name>${pom.artifactId}-${pom.version}</build.artifact.name> </properties> <build> <plugins> <plugin> <artifactId>maven-assembly-plugin</artifactId> <executions> <execution> <id>tomcat-overlay-assembly</id> <phase>package</phase> <goals> <goal>single</goal> </goals> <configuration> <appendAssemblyId>true</appendAssemblyId> <attach>false</attach> <outputDirectory>${project.build.directory}</outputDirectory> <descriptors> <descriptor>src/main/assembly/tomcat-overlay-assembly.xml</descriptor> </descriptors> </configuration> </execution> </executions> </plugin> </plugins> </build> <dependencies> <dependency> <groupId>javax.portlet</groupId> <artifactId>portlet-api</artifactId> <version>1.0</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.apache.pluto</groupId> <artifactId>pluto</artifactId> <version>1.0.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>xalan</groupId> <artifactId>xalan</artifactId> <version>2.6.0-up-patch-1.0</version> <scope>provided</scope> </dependency> </dependencies> </project>
tomcat-overlay-assembly.xml
Description: application/xml
