So hopefully I didn't turn off Mr. Syer entirely... but it did get me thinking. Does Maven need a new packaging type to do what he's talking about?
Something like this... <?xml version="1.0" encoding="UTF-8"?> <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> <groupId>com.mycompany.maven</groupId> <artifactId>3rdparty</artifactId> <packaging>3rdparty</packaging> <name>My Company's 3rdparty Jars</name> <version>1.0-SNAPSHOT</version> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-3rdparty-plugin</artifactId> <configuration> <basedir>lib</basedir> <jarFiles> <jarFile> <generatePom>true</generatePom> <artifactId>jconnect</artifactId> <groupId>com.sybase</groupId> <version>5.5.EBF11656</version> <fileName>jConnect5.5.EBF11656.jar</fileName> </jarFile> <jarFile> <generatePom>true</generatePom> <artifactId>jai-core</artifactId> <groupId>javax.media</groupId> <version>1.1.2</version> <fileName>jai-1.1.2/jai_core.jar</fileName> </jarFile> </jarFiles> </configuration> <extensions>true</extensions> </plugin> </plugins> </build> </project> This new packaging type is only configured for deploy and install phases (maybe verify as well). Thoughts? Although I'm perfectly happy with my shell scripts, I can see the virtue in doing this with a pom. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
