Looks interesting, but I think that this is causing the main plugin JAR to be replaced in the repository by the assembly. I can't do that - I must have the main plugin JAR in the repository because other projects have a compile-time dependency upon the code there.
Jim Babka Senior Software Engineer Main: (512) 334 3200 Direct: (512) 334 3237 Email: [EMAIL PROTECTED] Webify Solutions Enabling the On Demand Enterprise(tm) www.webifysolutions.com -----Original Message----- From: Darren Hartford [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 11, 2006 9:05 AM To: Maven Users List Subject: RE: [m2] Maven2 building Eclipse plugins, features, and update sites I have tried the ANT-tasks that eclipse provides, and at least for plugin-packaging they seem over-complicated. I have had success (just recently based on the mini-guide for assembly) in packaging the update-jar for an eclipse plugin as follows: Pom.xml (note I'm specifying a MANIFEST.MF file) =============== <!-- previously downloaded the eclipse jars into local repo and put in for compile-time dependency --> <build> <sourceDirectory>src</sourceDirectory> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <configuration> <archive> <manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile> </archive> </configuration> </plugin> <plugin> <artifactId>maven-assembly-plugin</artifactId> <configuration> <descriptor>src/main/assembly/dep.xml</descriptor> </configuration> </plugin> </plugins> </build> ===end pom.xml=== Src/main/assembly/dep.xml ================ <assembly> <!-- TODO: a jarjar format would be better --> <id>dep</id> <formats> <format>jar</format> </formats> <fileSets> <fileSet> <outputDirectory>/</outputDirectory> </fileSet> <!-- I think this is everyting based on eclipse workspace --> <fileset dir="${basedir}" includes="plugin.xml,META-INF/,null,icons/,pom.xml,toc.xml,html/"/> </fileSets> <dependencySets> <dependencySet> <outputDirectory>/</outputDirectory> <unpack>true</unpack> <scope>runtime</scope> <excludes> <exclude>junit:junit</exclude> </excludes> </dependencySet> </dependencySets> </assembly> ===end dep.xml=== I'm also interested in the features/update sites possibility, particuarly where I want to accomplish these tasks through autobuild instead of manually through Eclipse. I imagine something related to the :release maven plugin would come into play. P.s. I have also recently learned that the update-jar name does NOT seem to matter for Eclipse to load, so you can use the {artifactId}-{version}.jar for the eclipse-plugin-jar and deploy to repo. Again, only so-far, if there is something later that this may impact please let me know! -D --------------------------------------------------------------------- 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]
