Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 37457 invoked from network); 17 Nov 2005 04:50:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Nov 2005 04:50:32 -0000 Received: (qmail 47252 invoked by uid 500); 17 Nov 2005 04:50:31 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 47196 invoked by uid 500); 17 Nov 2005 04:50:31 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 47183 invoked by uid 99); 17 Nov 2005 04:50:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Nov 2005 20:50:30 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of trustin@gmail.com designates 64.233.184.199 as permitted sender) Received: from [64.233.184.199] (HELO wproxy.gmail.com) (64.233.184.199) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Nov 2005 20:52:04 -0800 Received: by wproxy.gmail.com with SMTP id i28so322979wra for ; Wed, 16 Nov 2005 20:50:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=YfURTusyhwzkgwlUOGqvC/JUwz2rppxvOIbRp2QGFcdNaNGkim4AfoRF+ZvEGRppZGQ5Nul5xJHzGu5XHOXXTVqgBr0ytkSrvAOxHqz2HnaqW/2r39E8sIOxKcnH3EHR/LIhBYEO03BTpaA0KqDZ8hUPX95kLHdhOQ9elUrLFKU= Received: by 10.54.76.9 with SMTP id y9mr6006839wra; Wed, 16 Nov 2005 20:50:09 -0800 (PST) Received: by 10.54.127.2 with HTTP; Wed, 16 Nov 2005 20:50:09 -0800 (PST) Message-ID: <768dcb2e0511162050t52c1bd91y@mail.gmail.com> Date: Thu, 17 Nov 2005 13:50:09 +0900 From: Trustin Lee To: Apache Directory Developers List Subject: [mina] Using Maven multiproject (Was: Using Ant + Forrest like Tapestry team does) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_29876_13785457.1132203009307" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_29876_13785457.1132203009307 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Brett, 2005/11/15, Brett Porter : > > > I'd like to generate the five JARs when I run 'mvn package': > > > > * mina-all-.jar, which contains classes from all subprojects > > * mina-core-.jar > > * mina-extension-ssl-.jar > > * mina-integration-spring-.jar > > * mina-integration-netty-.jar > > all can be done with the assembly plugin (descriptorId > jar-with-dependencies) - an example is maven-artifact-ant in the maven > repository. I know the assembly plugin, but why should I specify assembly descriptor file name when I run maven and not just 'jar'? Am I missing something here? > Plus 'mvn dist' will have to generate two tarballs: > > > > * mina-.tar.gz > > * mina-src-.tar.gz > > Also the assembly plugin -the default should suite (descriptorId of > bin and src respectively). I still have to specify descriptorId. It should be as simple as 'mvn dist'. > For documentation, running 'mvn site' will have to generate one site > > documentation that provides: > > > > * A single site like we ran 'mvn' site for one project; one JavaDoc, on= e > > coverage report, ... > > Aggregation in the site is where we need to improve support (though m1 > didn't do it either). Custom solution or working with us on it will be > required here. Each plugin needs some extra support to do this I think > - eg clover needs to merge databases, javadoc needs to pull in > multiple source directories. So aggregation is not supported yet, and we'll need it soon. That specific feature is planned for maven 2.1, but the way you do it now > is: > > > ... > spring-core > > > commons-logging > commons-logging > > This is great. Thanks for the info. > PS: BTW I've found a bug that an eclipse project file generated by 'mvn > > eclipse:eclipse' didn't include all JARs in the JRE such as jsse.jar. > That > > causes some build errors in Eclipse unfortunately. I did work fine with > M1. > > I'm not familiar with that issue - can you ensure it has been reported? It seems like it will be included in Maven 2.0.1: http://jira.codehaus.org/browse/MNG-937 Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ ------=_Part_29876_13785457.1132203009307 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Brett,

2005/11/15, Brett Porter = <brett.porter@gmail.com>= ;:
> I'd like to generate the five JARs when I run 'mvn package':
>> * mina-all-<version>.jar, which contains classes from all subp= rojects
> * mina-core-<version>.jar
> * mina-extension-ss= l-<version>.jar
>  * mina-integration-spring-<version>.jar
> *= mina-integration-netty-<version>.jar

all can be done with the= assembly plugin (descriptorId
jar-with-dependencies) - an example is ma= ven-artifact-ant in the maven
repository.

I know the assembly plugin, but why sh= ould I specify assembly descriptor file name when I run maven and not just = 'jar'?  Am I missing something here?

> Plus 'mvn dist' will have to generate two tarballs:
>
> * = mina-<version>.tar.gz
> * mina-src-<version>.tar.gz
Also the assembly plugin -the default should suite (descriptorId of
bin and src respectively).

I still have to specify des= criptorId.  It should be as simple as 'mvn dist'.

> For documentation, running 'mvn site' will have to generate one site> documentation that provides:
>
> * A single site like we= ran 'mvn' site for one project; one JavaDoc, one
> coverage report, = ...

Aggregation in the site is where we need to improve support (though= m1
didn't do it either). Custom solution or working with us on it will = be
required here. Each plugin needs some extra support to do this I thin= k
- eg clover needs to merge databases, javadoc needs to pull in
multi= ple source directories.

So aggregation is not supporte= d yet, and we'll need it soon.

That specific feature is planned for maven 2.1, but the way you do it now i= s:

<dependency>
  ...
  <artifact= Id>spring-core</artifactId>
  <exclusions>
&= nbsp;   <exclusion>
     &= nbsp;<groupId>commons-logging</groupId>
      <artifactId>commons-logging&l= t;/artifactId>
    </exclusion>
 &n= bsp;</exclusions>

This is great.  Thanks fo= r the info.

> PS: BTW I've found a bug that an eclipse project file generated by 'mv= n
> eclipse:eclipse' didn't include all JARs in the JRE such as jsse.= jar.  That
> causes some build errors in Eclipse unfortunat= ely.  I did work fine with M1.

I'm not familiar with that issue - can you ensure it has been repor= ted?

It seems like it will be included in Maven 2.0.1:=

http://jira.cod= ehaus.org/browse/MNG-937

Trustin
--
what we call human nature is act= ually human habit
--
http://gleamy= node.net/ ------=_Part_29876_13785457.1132203009307--