Let me just say that maven rules, and I suck.  Turns out that maven WAS
picking up the ~/build.properties file, but the maven.repo.remote property
was wrong.  I had ONE TINY EXTRA SPACE at the end of the property, and this
hosed my connection.  It wasn't until I looked at the url maven was trying
to download that I figured it out.

While on this topic, I think I might have a suggestion for the messages
displayed when downloading from the remote repository.  
1.  attempt to grab all dependencies from one repository at a time.  I think
the current display is confusing since it goes through all remote sites for
each dependency.  Here's an example of the output:
attempting to download resources from http://a.b.com/maven
xxx-1.1.jar - resource not found.
yyy-2.3.jar - ........................................

attempting to download resoures from http://c.d.com/maven
xxx-1.1.jar - ................................
yyy-2.3.jar - resource not found.

2.  reduce verbosity of error messages.  It's extremely confusing for users
to see this error message for one site, when it succeeds for the other.
Error retrieving artifact from
[http://www.ibiblio.org/maven/net.sourceforge.xdoclet/jars/xjavadoc-1.0.jar]
: java.lang.Exception: Can't get xjavadoc-1.0.jar to C:\Documents and
Settings\RyanS\.maven\repository\net.sourceforge.xdoclet\jars\x
javadoc-1.0.jar

I think it should simply display - resource not found.  Any comments on
these?


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 24, 2003 7:29 PM
To: Maven Users List
Subject: Re: beta 10 on win2k

Nope, they're pretty much the same.....
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/


"Sonnek, Ryan" <[EMAIL PROTECTED]> wrote on 24/07/2003 11:57:46 PM:

> Has anyone out there had issues with beta 10 on win2k picking up 
properties
> files?  I've just gone through and updated all of our developers from 
beta 9
> to beta 10, and there were five pc's running win2k that wouldn't pick up
> ~/build.properties.  it also wouldn't pick up 
PROJECT_HOME/build.properties.
> this was a major problem for us, but I created a temporary hack by 
creating
> a batch file to pass in the properties to maven.  Has something changed
> since beta 9?
> 
> Ryan
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to