I don't know of a way to configure Maven this way, other than the -o option to tell Maven to run in offline mode, where nothing ever gets downloaded. We haven't really had this problem come up. The un-committed changes for any given developer is usually limited to one or two projects.
Plus, most of our developers use an IDE for doing their own builds of projects while developing instead of using Maven. When they are ready to commit their changes, they'll do a Maven build to make sure that build still works. ..David.. -----Original Message----- From: Jose Gonzalez Gomez [mailto:[EMAIL PROTECTED] Sent: Saturday, September 03, 2005 3:16 AM To: Maven Users List Subject: Re: Best practices for release and version management? David, I understand that you're deploying your snapshot versions for your projects in your internal repository, but I don't fully understand your environment (or maybe Maven's way of working)... let me explain: I understand that you can publish snapshot versions of artifacts under development that are used across projects using a checked out source tree of those artifacts. The problem comes when you have several developers working on a project and using artifacts that are private to that project, and where several developers may be changing the same artifact (think of two different developers working on two different EJBs in the same artifact, or two different parts of a web interface). In this case you cannot publish that artifact until changes are comitted, and every developer must use her own snapshot copy of the artifact with her local changes that must be taken from her local repository. It's in this case that I don't want those artifacts to be taken from any other repository. How do you handle this, or how do you configure Maven to tell that those artifacts should only be taken from the developer local repository? Best regards Jose 2005/9/2, David Jackman <[EMAIL PROTECTED]>: > We're pretty much doing what Jose is doing, but we don't see these timeouts. > I think it's because the Maven properties are set up to look in our internal > repository first and then go global from there. Just about everything is in > the internal repository (certainly the artifacts for our projects are there), > so the download time isn't much at all. > > My maven.repo.remote property lists the internal repository first, and > ibiblio second. > > As far as the approach to take when releasing and incrementing versions, the > process you describe is essentially what we're doing. In fact, I just wrote > up a document outlining our internal process for releasing projects for our > developers (since we're about to release the big project soon), so I know the > details very well. > > ..David.. > > > -----Original Message----- > From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] > Sent: Friday, September 02, 2005 4:14 AM > To: Maven Users List > Subject: Re: Best practices for release and version management? > > On Fri, Sep 02, 2005 at 11:46:49AM +0200, Jose Gonzalez Gomez wrote: > > Hi there, > > > > How do you use to manage your project version among releases? I > > mean... what do you exactly put in currentVersion in your pom and > > how do you change it among releases? > > > > I'm currently using the following approach: > > > > 1. Developing version 0.1 - currentVersion = 0.1-SNAPSHOT 2. V0.1 > > release: commit all pending changes, change currentVersion to 0.1, > > commit pom, tag/branch repository, make release. > > 3. Developing version 0.2 - change currentVersion to 0.2-SNAPSHOT, > > commit pom, update and continue developing > > This is the way that we're recomending and using ourselfs. > > > What do you think about this? This approach has one annoying thing: > > maven tries to download SNAPSHOT versions from remote repositories, > > although they're only locally installed in the developer repository. > > After some timeout maven uses the local version, but in case of > > large projects the sum of the timeouts may be big. Do you use any > > other approach? > > The easiest solution to this problem is to either configure a proxy so > it doesn't time out (but rather get a 404 response from the HTTP > server) or just run Maven in off-line mode (by using the -o switch) > > -- > Trygve > > --------------------------------------------------------------------- > 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]
