Why does it require the JAR? Wher eit goes depends on what you want to do with it. We could vote to have it as part of the Maven SVN, but that would require that the existing committers are willing/able to work on it. For independantly run plugins, or licensing that is open source but not ASF friendly we offer easy hosting at mojo.codehaus.org.
- Brett On 12/21/05, Torsten Curdt <[EMAIL PROTECTED]> wrote: > Ok ...got the plugin working! > > Here is the output for commons-jci :-D > > [INFO] jakarta-commons-jci-1.0-SNAPSHOT.jar classes:44 dependencies: > 130 => 100.0% (58798->59159) > [INFO] commons-collections-3.1.jar classes:446 dependencies:518 => > 2.0% (559366->13901) > [INFO] core-3.1.0.jar classes:1255 dependencies:1469 => 31.0% > (3555707->1116189) > [INFO] groovy-all-1.0-jsr-03.jar classes:915 dependencies:1220 => > 47.0% (1587529->746634) > [INFO] janino-2.3.7.jar classes:333 dependencies:414 => 64.0% (351643- > >227840) > [INFO] commons-logging-api-1.0.4.jar classes:13 dependencies:57 => > 45.0% (26202->11936) > [INFO] commons-io-1.1.jar classes:41 dependencies:98 => 48.0% (61562- > >29818) > [INFO] commons-lang-2.1.jar classes:110 dependencies:161 => 2.0% > (207723->5730) > > It requires to be called after jar:jar as it also > needs the final artifact that got built. So I've > added "@phase package" and expected a simple "mvn > minijar:minijar" would also build the jar. > > What am I missing? > > Ah... and the next question - where to put that plugin? :) > > cheers > -- > Torsten > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
