: ruelloehr
AOL: dokoruel
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 10, 2005 10:52 PM
To: Maven Users List
Subject: Re: plugin development - extending simple plugin like jar
To use a custom plugin, you need to use a custom packaging element.
Take
On 11/12/05, Ruel Loehr [EMAIL PROTECTED] wrote:
However, in practice I received a number of errors telling me that I
needed to use the groupID:artifact:Id:goal format when defining my
phases. Changing for example, compiler:compiler to
org.apache.maven.plugins:maven-compiler-plugin:compile
I identified a need in our particular build such that many times when we
build a jar, we need to include classes from another project.
For example, in a multiproj build I have 2 submodules:
Module1
Module2
I build module1 and jar it up, then I build module2 and jar it up,
however, the caveat is
To use a custom plugin, you need to use a custom packaging element.
Take a look at the lifecycle guide on the web site (there was a thread
on this list very recently about it too).
However, I'm curious what your use case is for duplicating classes
across multiple jars. Why is this required? It
