> For the sake of documentation, note that "groupID" should be "groupId". Thanks mate - I typed the XML freehand, as opposed to copy/paste. Hopefully that little typo won't be the subject of another email some day. If so, I'll freely admit my mistake...
Thanks for the rest of the info also. Some of it I guessed, but it's nice to see it spelled out. -----Original Message----- From: Craig S. Cottingham [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 27, 2005 12:45 PM To: Maven Users List Subject: Re: How to add external libraries (first post) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 27, 2005, at 13:33, Parker, Chris wrote: > <project> > > included xml SNIPPED all the way to the end > > <dependencies> > <dependency> > <groupID>springframework</groupID> > <artifactId>spring</artifactId> > <version>1.2.2</version> > <dependency> > </dependencies> > </project> For the sake of documentation, note that "groupID" should be "groupId". > 1) groupID is described as "The project group that produced the > dependency, e.g. geronimo." I tried "spring" which failed, and then > "springframework" which worked. I surmise that the project group > corresponds to the directory name "springframework" in: > http://www.ibiblio.org/maven/springframework/jars/ . I might be nice > if > the description included a blurb saying something about each group > having it's own directory - or some such. It was a minor leap to > realize that the project group is typified by the directory ;) Unfortunately, the groupId is not always obvious. Sometimes there's even confusion -- on iBiblio, for instance, there are directories named "spring" and "springframework". The only reliable thing to do (that I'm aware of) is point your browser to <http://www.ibiblio.org/maven/> and go looking for the JAR file in which you're interested. > 2) artifactId is described as "The unique id for an artifact produced > by > the project group, e.g. germonimo-jms." I tried springframework first, > and when I saw the command window say "Attempting to download > springframework-1.2.2.jar" I knew what to do. This should be documented somewhere -- both in the sense of "it probably is" and "if it's not, it should be": Maven builds URLs to remote dependencies using the pattern http://www.ibiblio.org/maven/${groupId}/${type}s/${artifactId}- ${version}.${type} (This is a slight oversimplification, but is valid for a stock installation of Maven.) So, given a dependency declaration like <dependency> <groupId>springframework</groupId> <artifactId>spring</artifactId> <type>jar</type> <version>1.2.2</version> <dependency> Maven will build the URL http://www.ibiblio.org/maven/springframework/jars/spring-1.2.2.jar If the "type" element is omitted from the declaration, Maven assumes a value of "jar". - -- Craig S. Cottingham [EMAIL PROTECTED] OpenPGP key available from: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7977F79C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFC5+QzEJLQ3Hl395wRAuNMAKCpOZ3pnyFvK/wIPckosD3u9YHFjQCcCwww I/oP1SRQy/YstfFVt5o1bj0= =nuzj -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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]
