I assume that "<version>[1.2.2]</version>" works in <plugin>, <dependencyManagement>, and <pluginManagement> to accomplish the same effect for plugin versions and inherited version information.
-----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, April 07, 2006 00:31 To: Maven Users List Subject: Re: Internal (intranet) repositories Unfortunately, ibiblio is "super busy" most hours of the day as it is a shared resource. This is the price we pay for using it. You can use a Central mirror instead by configuring your settings.xml. The occasional 503 on ibiblio is really no big deal imo. Especially considering that you can run offline with -o once your dependencies are all downloaded into your repo. For 90% of maven builds, you really don't need to go out to the net to check for updates of dependencies etc. In fact, I might even suggest you use [x.y.z] to lock in versions for dependencies just to prevent Maven from having to go out to ibiblio etc to find updates, and also to prevent changes in new versions of dependencies from breaking your build. Especially when you are dealing with code that's in production -- the last thing you'd want is for Maven to autodownload the latest JDO files which might not be 100% compatible with the version you were running before. Enabling this can be as simple as tweaking your dependencies as follows: <dependency> ... <version>[1.2.2]</version> </dependency> This "locks" the dependency version to 1.2.2 so Maven does not check ibiblio for updates. When you just use <version>1.2.2</version>, Maven will go out and check ibiblio for updates and pull them down automatically for you. Go here to read more about configuring versions: http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict +Resolution Wayne On 4/6/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: > For the record, this is why I want to avoid going to remote server for > the repository: > > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > Error transferring file > commons-io:commons-io:jar:1.0 > > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > snapshots (http://snapshots.maven.codehaus.org/maven2) > Path to dependency: > 1) > org.apache.maven.plugins:maven-resources-plugin:maven-plugin:2.1 > 2) commons-io:commons-io:jar:1.0 > > > > Caused by I/O exception: Server returned HTTP response code: 503 for > URL: > http://www.ibiblio.org/maven2/commons-io/commons-io/1.0/commons-io-1.0. > jar.sha1 > > Re-running produces a working build. > > > > -----Original Message----- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 06, 2006 6:16 PM > To: Maven Users List > Subject: RE: Internal (intranet) repositories > > Here is my pom file. The directory in the url below is a shared folder > on a different machine. > > <project xmlns="http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > <modelVersion>4.0.0</modelVersion> > <groupId>com.ejstools.tool1</groupId> > <artifactId>tool1</artifactId> > <packaging>jar</packaging> > <version>1.0-SNAPSHOT</version> > <name>EJs Tools</name> > <url>http://build2.corp.upromise.com:8080</url> > <description>This project is simply here to lean about maven > and eventually will be used to build EJs Java tools.</description> > <repositories> > <repository> > <id>local</id> > <name>Upromise Maven Repository</name> > <url>file:///<servernamehere>/mavenrepository</url> > </repository> > </repositories> > <dependencies> > <dependency> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > <version>3.8.1</version> > <scope>test</scope> > </dependency> > </dependencies> > <build> > <resources> > <resource> > <directory>src/main/resources</directory> > <filtering>true</filtering> > </resource> > </resources> > </build> > </project> > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 06, 2006 6:12 PM > To: Maven Users List > Subject: Re: Internal (intranet) repositories > > Where exactly were you putting that repository section? In your > pom.xml? Or in another configuration file? > > Wayne > > > On 4/6/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > None of this explains why it didn't use my repo and simply ignored it > completely. > > > > This is the more important part of the puzzle. > > > > --------------------------------------------------------------------- > 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]
