The maven-assembly-plugin throws an error when it can't find a pom, more so a valid 4.0.0 pom.
It fails at the very first error. So I had to sift thro each error by commenting out the artifact that depends on that pom. I got till tranql-1.4-SNAPSHOT. I gave up sifting further because, for one, tranql's groupId has changed to org.tranql but that is not published yet. I hope there aren't any more bad/missing poms after tranql. Here are the missing/invalid poms along with the geronimo artifacts that I had to comment out in ( ) - ( geronimo-directory ) Project: directory-protocols:ldap-protocol POM Location: C:\Documents and Settings\Administrator\.m2\repository\directory-p rotocols\ldap-protocol\0.9.2\ldap-protocol-0.9.2.pom Reason: Not a v4.0.0 POM. ( geronimo-tomcat ) File C:\Documents and Settings\Administrator\.m2\repository\tomcat\catalina\5.5. 15\catalina-5.5.15.pom does not exist ( geronimo-tomcat ) ( geronimo-jetty ) ( geronimo-jetty-builder ) File C:\Documents and Settings\Administrator\.m2\repository\tomcat\jasper-compil er\5.5.15\jasper-compiler-5.5.15.pom does not exist ( geronimo-axis ) ( geronimo-axis-builder ) File C:\Documents and Settings\Administrator\.m2\repository\commons-discovery\co mmons-discovery\0.2-dev\commons-discovery-0.2-dev.pom does not exist ( geronimo-connector ) ( geronimo-connector-builder ) Project ID: tranql:tranql POM Location: C:\Documents and Settings\Administrator\.m2\repository\tranql\tran ql\1.4-SNAPSHOT\tranql-1.4-SNAPSHOT.pom Reason: Not a v4.0.0 POM. Cheers Prasad On 7/4/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Ooops. Sorry Jason. I was trying to keep up with the emails on my vacation and ended up misreading your question. You do clearly ask why the d-m-p not be used to install car files. The geronimo-assembly-plugin (g-a-p) deploys a car artifact. I believe that this is a lot more than just unpacking a dependency that the d-m-p does. The former also takes care of all the car's dependencies too by reading its plan. I don't think the latter could have done it. Cheers Prasad On 7/2/06, Jason Dillon <[EMAIL PROTECTED]> wrote: > I was never suggesting to not use the assembly plugin, but to use the > dependency plugin instead of a custom car installer plugin. > > --jason > > > On Jul 2, 2006, at 8:25 AM, Prasad Kashyap wrote: > > > Inline - > > > > On 7/1/06, Jason Dillon <[EMAIL PROTECTED]> wrote: > >> >> Why can't the dependency plugin be used to install the car files? > >> > > >> > I'm not sure what you mean by the dependency plugin. > >> > >> http://mojo.codehaus.org/dependency-maven-plugin/ > >> > >> It basically handles copying (or unpacking) artifacts and their > >> dependencies to somewhere other than the repo cache. > >> > > > > The depenency-maven-plugin (d-m-p) does not meet all our requirements > > like the m-a-p does. And for those few requirements that m-a-p > > doesn't, it's committers were willing to work with me to take my > > patches in and make it suit our requirements. > > > > The assembly descriptor in the m-a-p has the following features. You > > can't find an equivalent functionality in the d-m-p. > > > > 1. <repositories> can be used to copy into a m2 repo structure. > > 2. <fileset> and <file> can be used to copy other files like > > var/config/xml which are not in any dependency artifact. > > 3. <unpack> will have include/exclude. (my patch) > > 4. mapper functionality will introduce some 6 ANT built-in mappers. > > Custom mappers can be specified using a classname. We need this to > > copy schema files in a flattened structure. (my patch) > > 5. The final archive is created in many formats we specify. > > 6. Assembly descriptor is a cleaner way of specifying how and where > > the different jars are to be copied. (lib, ext, endorsed, repository, > > bin, docs etc). Then 2-3 plugin executions are all we need. With the > > d-a-p, we woud need a lot more plugin executions, one for each > > directory atleast. > > 7. In the d-m-p, the artifacts to be copied/processed have to be > > specified inside the plugin execution in the long format > > <group><artifact>. This will make our pom.xml a very very long one. > > In the assembly descriptor of m-a-p, the artifact to be copied is > > specified as a groupid:artifactid one liner. > > > > I'm sure there a few more. > > > > Cheers > > Prasad > > > > > > > >> > >> --jason > >> > >
