> -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Monday, December 04, 2006 2:15 PM > To: Maven Users List > Subject: Re: MAVEN_INSTALL_DIR/conf/settings.xml > > On 12/4/06, Marilyn Sander -X (marilysa - Digital-X, Inc. at > Cisco) <[EMAIL PROTECTED]> > > Perhaps I mis-stated a bit. There is not a time dependency. There > > are two ways that we invoke maven. The first is with the > mvn command, > > to do the java build. > > The second is later, after the mvn build has created the local > > repository, where we invoke a maven <copy> ant task to fetch some > > artifacts from the local repository. > > The fetching from the local repository is so we can build > an install > > file using a commercial tool for building a GUI installer. > > The local repository is intended to be used by a single > developer. If you need to share artifacts, then deploy them > to a "remote" internal corporate repository. > > The snapshot and release deployment urls are set in > <distributionManagement> for each project.
The point here is that a single developer who works on multiple products or product releases may need one local repository per product or release. This is particularly true if the different releases need to be built simultaneously, because the build puts artifacts compiled/created during the build into the local repository. Simultaneous builds using the same local repository would clobber each others' files. This is all run under a single top-level ant script, and therefore all in one run by the same user. The top ant script runs maven for the java build. Then it runs some Makefiles for modules written in C/C++. Then it runs another ant script, build_installer.xml, which collects artifacts from the build and creates an install file for shipment to customers. It is build_installer.xml that uses the <copy> ant task from antlib to fetch artifacts from the local repository for inclusion in the install file. One solution we've contemplated, and probably will implement, is that build_installer.xml will no longer use antlib nor the local repository, but will fetch artifacts from the source directories where they were created. Please note, the documentation for antlib specifically calls out the authors' desire to be able to share the local repository between Maven and ant. They just overlooked the fact that, just as Maven has provision for alternative settings.xml files, so should antlib. --Marilyn > > -- > Wendy > > --------------------------------------------------------------------- > 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]
