"Olivier CHAMPAGNE" <[EMAIL PROTECTED]> wrote on 04/02/2004 12:21:00 AM:
> > 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. Which questions? > I think that : > - "The url of the dependency's homepage" is a bit confusing (but I didn't Got a suggestion for a better description? We'll use it. > 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. There already is a <type>....??? -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
