Return-Path: 
 <users-return-8498-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: (qmail 65635 invoked from network); 9 Sep 2003 01:42:06 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 9 Sep 2003 01:42:06 -0000
Received: (qmail 78485 invoked by uid 500); 9 Sep 2003 01:40:48 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 78318 invoked by uid 500); 9 Sep 2003 01:40:46 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Subscribe: <mailto:users-subscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 78127 invoked from network); 9 Sep 2003 01:40:43 -0000
Received: from unknown (HELO adslgateway.multitask.com.au) (202.44.167.185)
  by daedalus.apache.org with SMTP; 9 Sep 2003 01:40:43 -0000
In-Reply-To: <bji0ua$61k$1@sea.gmane.org>
To: "Maven Users List" <users@maven.apache.org>
Subject: Re: Is there any reason we have to resolve dependencies all the time?
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.2CF2 July 23, 2003
From: dion@multitask.com.au
Message-ID: 
 <OFA274F78E.80AD8B33-ONCA256D9C.0004691C-CA256D9C.0004ACE5@multitask.com.au>
Date: Tue, 9 Sep 2003 10:55:54 +1000
X-MIMETrack: Serialize by Router on ADSLGateway/Multitask
 Consulting/AU(Release 6.0|September
 26, 2002) at 09/09/2003 11:45:43 AM,
	Serialize complete at 09/09/2003 11:45:43 AM
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

How many different <depType>s do you see.

>From what you've described before, it looks like almost one per plugin.
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/


news <news@sea.gmane.org> wrote on 08/09/2003 11:41:30 PM:

> dion@multitask.com.au wrote:
> 
> > Yes, resolving dependencies all the time is a PITA.
> > 
> > What's your suggested alternative?
> > 
> > Do plugins declare whether they need the dependencies?
> > Some other method of us guessing?
> 
> If the project dependencies list had a clue as to which
> type of dependency they are, then they can be resolved
> occordingly.
> 
> As one person rightfully pointed out, there are runtime,
> build time, and test time dependencies.  There may be more,
> (possibly a packaging time?), but for the sake of simplicity/
> discussion that should be enough.
> 
> The java:compile and test:compile would resolve all the
> dependencies necessary for it at that time.  That can either
> be done by having different dependencies sections like this:
> 
> <buildDependencies/>
> <testDependencies/>
> <runtimeDependencies/>
> 
> Or it can be done something like this:
> 
> <dependencies>
>    <dependency>
>       <depType>build</depType>
>       <!-- ... -->
>    </dependency>
> </dependencies>
> 
> Either way, the project specific dependencies would not
> need to be resolved until the proper plugin needed them.
> The **:compile plugins would grab the build dependencies
> plus whatever else it needed (like test dependencies for
> the test:compile).
> 
> In the end, it is (conceptually speaking) not difficult.
> Not having messed with much of the code, I cannot vouch
> for the technical aspects of it.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org