Thanks for the hint... I probably wrote this too fast.
But if you consider the URL provided in project.properties
(maven.repo.remote) in place of "The url of the dependency's homepage", the
mechanism works as described bellow and my questions remain the same.
I think that :
- "The url of the dependency's homepage" is a bit confusing (but I didn't
read the new reference documentation deep enough. RTFM as people say... ;o)
- an extended download mechanism should be very usefull because the
existing one is spread accross tags as <artifactId> - <groupId> or <id> and
<type>, confusing in <type> the file-type/extension and the download
mechanism (just *download* for </type> or <type>foo</type> and
*download+expand* for <type>plugin</type>) in different locations (local
directories like $MAVEN_HOME_LOCAL/plugins or
$MAVEN_HOME_LOCAL/repository). An additionnal tag (and probably optionnal
like <type>) could allow to clarify the expected extension.
Olivier Champagne
(\(\ "Regular Expression
( ~.) are to strings what
o((")(") math is to numbers"
[EMAIL PROTECTED]
.com.au Pour : "Maven Users List" <[EMAIL
PROTECTED]>
cc :
02/02/2004 Objet : Re: Re: [2nd edition] MAVEN
dependencies' mechanism
06:56
Veuillez
r�pondre �
"Maven Users
List"
From
http://maven.apache.org/reference/project-descriptor.html#dependencies
"The url of the dependency's homepage.
This url will be provided to the user if the jar file cannot be downloaded
from the central repository. "
It's NOT used for downloads.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Alex Karasulu <[EMAIL PROTECTED]> wrote on 31/01/2004 01:41:46 AM:
> Until someone from the maven team clarifies everything is questionable
> but I had thought the URL tag is used just for the website link to the
> dependent library when generating docs.
>
> It is not used to locate or download the resource.
>
> Alex
>
> >
> > From: Daniel Bonniot <[EMAIL PROTECTED]>
> > Date: 2004/01/30 Fri AM 05:31:58 EST
> > To: [EMAIL PROTECTED]
> > Subject: Re: [2nd edition] MAVEN dependencies' mechanism
> >
> > > If I did not miss-understand the maven dependencies' mechanism in
> > > project.xml :
> > >
> > >
> > > With
> > > <dependencies>
> > > <dependency>
> > > <id>DEPEND</id>
> > > <version>1.0</version>
> > > <url>http://address/plugin/</url>
> > > </dependency>
> > > </dependencies>
> > > Maven will first try to download
"http://address/plugin/DEPEND/jars/DEPEND
> > > -1.0.jar" under
$MAVEN_HOME_LOCAL/repository/DEPEND/jars/DEPEND-1.0.jar
> >
> > (I'm new to Maven, so take this with a grain of salt)
> >
> > I first had the same impression as you, but after investigation it
seems that
> > the url tag is just used to suggest that URL to the user if the
download failed,
> > so that the user can download it manually (e.g. if the license does
not allow
> > the jar to be put in a repository).
> >
> > If you want a plugin to be downloaded from an alternate repository,
what I know
> > works is to declare it in a file build.properties in your home
directory
> > (~/build.properties on Unix, not sure about windows). Example:
> >
> >
maven.repo.remote=http://nice.sf.net/maven,http://www.ibiblio.org/maven
> >
> > (ibiblio is the default maven repository)
> >
> > Daniel
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
