Hello again. So I've gone through a release cycle for all of my modules, which was a long process, and ironed out a few cycles that had crept into the dependencies. Now I am at the stage where I have two modules that create WAR files and I have pursued my original suggestion of creating another SVN / Maven2 module to package that up. I would be happy with just a zip of some form as a first draft; I can worry about integrating it with an installer at a later date.
So, I have a POM like this: <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";> <parent> <groupId>com.example</groupId> <artifactId>master-pom</artifactId> <version>1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>com.example.installer</groupId> <artifactId>the-installer</artifactId> <packaging>pom</packaging> <version>1.0-SNAPSHOT</version> <name>My Company Platform Installer</name> <url>http://maven.apache.org</url> <dependencies /> <dependencyManagement> <dependencies> <dependency> <groupId>com.example.someGroup-A</groupId> <artifactId>webapp-A</artifactId> <type>war</type> <version>1.2</version> <scope></scope> </dependency> <dependency> <groupId>com.example.someOtherGroupId-B</groupId> <artifactId>webapp-B</artifactId> <type>war</type> <version>1.3</version> </dependency> </dependencies> </dependencyManagement> <build> <plugins> <plugin> <artifactId>maven-assembly-plugin</artifactId> <configuration> <descriptor>src/main/assembly/dep.xml</descriptor> </configuration> </plugin> </plugins> </build> </project> I have a simple assembly configuration - src/main/assembly/dep.xml: <?xml version="1.0" encoding="UTF-8" ?> <!-- maven-assembly-plugin assembly configuration for pulling together the assembly for the installer --> <assembly> <formats> <format>zip</format> </formats> <includeBaseDirectory>false</includeBaseDirectory> <fileSets> <fileSet> <directory>/</directory> <excludes> <!-- Exclude Eclipse meta-data file. --> <exclude>.project</exclude> <!-- Don't include the assembly itself. --> <exclude>src/main/assembly/**</exclude> <exclude>target/archive-tmp/**</exclude> </excludes> </fileSet> </fileSets> <dependencySets> <dependencySet> <outputDirectory>/</outputDirectory> <unpack>true</unpack> <scope>runtime</scope> </dependencySet> </dependencySets> </assembly> The two WARs are installed into our internal repository (and in my local repository), but no request is made to retrieve them. What am I missing? Cheers, James On 25/04/07, James Abley <[EMAIL PROTECTED]> wrote:
Thanks for that link, that does seem very useful to know. Any comments on my suggested approach of releasing content? I'm trying to understand what Maven buys me by using the mvn release:prepare approach. Cheers, James On 25/04/07, Damien Lecan <[EMAIL PROTECTED]> wrote: > > I'm fairly new to Maven2 and haven't used it much in situations more > > complex than those described in the documentation. But now I have hit > > an issue that I haven't been able to find much documentation on this > > subject[1] > > http://docs.codehaus.org/display/MAVENUSER/How+to+handle+releases+with+multiple+SNAPSHOT+dependents > > Use version range ? > http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution > > Damien > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
