It is indeed seriously strange. That URL should correspond to: <groupId>eclipse.org.eclipse.core</groupId> which is probably why the maven build isn't finding it.
But that's a very weird groupId. And it doesn't match what is in the metadata files in the repository. Looks like the eclipse group have screwed up their 3.2.x uploads to me, replicating their data to the wrong directory within the maven repo. In addition, not finding a dependency during a build should be an error. So I don't understand why this build is succeeding at all. Regards, Simon Dennis Lundberg schrieb: > Right. > > Now that's a seriously strange repo. Are they in the middle of a > reorganisation? > > I'm out of clues now... > > manish wrote: >> Hi Dennis, >> >> The dependency is declared as >> <dependency> >> <groupId>org.eclipse.core</groupId> >> <artifactId>org.eclipse.core.resources</artifactId> >> <version>3.2.0</version> >> </dependency> >> >> So, unless I'm missing something, maven should look for it at >> http://repo1.maven.org/eclipse/org/eclipse/core/org.eclipse.core.resources/3.2.0/ >> >> >> where it does exist. >> Cheers, >> Manish >> >> >> Dennis Lundberg-2 wrote: >>> [EMAIL PROTECTED] wrote: >>>> Hi, >>>> >>>> I was hoping someone could help explain this observed behaviour (maven >>>> 2.0.4). >>>> >>>> We have setup an internal repository (using Codehaus proxy >>>> repository). >>>> We have a large number of dependencies in our maven build. However, >>>> for >>>> a particular subset of these dependencies, maven performs an update >>>> check once per day on both our internal repository (te-uk) and the >>>> maven >>>> central repository. Here is the logging from maven - >>>> >>>> [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for >>>> updates from te-uk >>>> [INFO] artifact org.eclipse.ant:org.eclipse.ant.core: checking for >>>> updates from central >>>> Now, this only happens for this one particular set of jar >>>> dependencies. >>>> An exmple of one of the culprits is - >>>> >>>> <dependency> >>>> <groupId>org.eclipse.core</groupId> >>>> <artifactId>org.eclipse.core.resources</artifactId> >>>> <version>3.2.0</version> >>>> </dependency> >>>> >>>> There are 20 other dependencies that are all from the org.eclipse.core >>>> group. These are fetched from the repository at >>>> http://repo1.maven.org/eclipse. Every one of these gets the update >>>> check >>>> once per day. However, they are declared exactly the same way as >>>> any of >>>> our other versioned dependencies which never get an update check. >>> I went looking in that repo for the dependency you specified above >>> and it doesn't exist at >>> http://repo1.maven.org/eclipse/org/eclipse/core/resources/ >>> >>> So what I think is happening is that Maven tries to download version >>> 3.2.0 once a day because you said you wanted that version. But since >>> it will never find it, it will retry every day. >>> >>> >>>> It is a problem because once per day our build takes 5 mins longer >>>> than >>>> necessary. I explicitly do not want an update check on any of our >>>> versioned dependencies (if I did, I would use snapshots). Hence, our >>>> repository is configured as follows - >>>> >>>> <repositories> >>>> <repository> >>>> <id>te-uk</id> >>>> <name>TE-UK Repository</name> >>>> <url>http://us000099.pun.dom:9999/repository</url> >>>> <releases> >>>> <enabled>true</enabled> >>>> <updatePolicy>never</updatePolicy> >>>> <checksumPolicy>warn</checksumPolicy> >>>> </releases> >>>> <snapshots> >>>> <enabled>false</enabled> >>>> </snapshots> >>>> </repository> >>>> </repositories> >>>> <pluginRepositories> >>>> <pluginRepository> >>>> <id>te-uk</id> >>>> <name>TE-UK Repository</name> >>>> <url>http://us000099.pun.dom:9999/repository</url> >>>> <releases> >>>> <enabled>true</enabled> >>>> <updatePolicy>never</updatePolicy> >>>> <checksumPolicy>warn</checksumPolicy> >>>> </releases> >>>> <snapshots> >>>> <enabled>false</enabled> >>>> </snapshots> >>>> </pluginRepository> >>>> </pluginRepositories> >>>> >>>> I've tried playing around with the updatePolicy on the repository, but >>>> it has absolutely no effect whatsoever. >>>> >>>> Any help to explain this behaviour would be appreciated. >>>> >>>> Thanks, >>>> Manish >>>> >>> >>> -- >>> Dennis Lundberg >>> >>> --------------------------------------------------------------------- >>> 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]
