Bummer about the potential for a bug. I know that the group working on maven 2 things have submitted a "repository" directory in the perforce project (kinda exactly the opposite to what this feature in maven is supposed to provide).
But theirs works, but it seems to have to be a local copy. I'll try to bring up apache on that machine and see what happens. I kind of don't want to do this to an already complicated build environment though. -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, April 07, 2006 12:33 AM To: Maven Users List Subject: Re: Internal (intranet) repositories Can you perhaps load that repository on a local Apache server and modify the <repository> to reflect the HTTP repo, and see if it still fails to attempt to access the local repo? Might be a bug in how Maven deals with file:/// repos. I know most of us on the list are using simple HTTP repos, so you might have just stumbled into a new bug. Wayne On 4/6/06, EJ Ciramella <[EMAIL PROTECTED]> wrote: > 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]
