Using Nexus already. Any advices what needs to be configured (differently)? Currently in .m2/settings.xml a nexus repository is configured to be mirror of central, while another project specific repository (group) is defined in projects aggregator/parent pom.
Nevertheless, dependencies report plugin messes up metadata in my local repository. It seems to query directly (not via repository manager) all the repositories (project's own and from dependencies) for existence of dependencies on them (hanging build, single very small module took about 18min to build a site with only project info reports - index, summary, dependencies, dependency convergence, dependency management, and plugin management reports); temporary workaround was to set dependencyLocationsEnabled to false. Not sure why does dependencies report plugin even use these repositories defined in dependencies pom's; I'm guessing because of transitive dependencies, as they probably might be resolved from repository defined in dependency. Since build of a module wouldn't pass validate phase if dependencies weren't resolved, IMO it would be more efficient if dependencies report instead of querying repositories again would just reuse dependency resolution info, from where given dependency was resolved from, assuming these info are available and shareable between dependency plugin and dependencies report plugin. If it's not available and/or shareable, then maybe dependencies report could just use same strategy to resolve dependencies location as dependency plugin uses to resolve dependencies, instead of "query all repositories" strategy. Regards, Stevo. On Thu, Nov 5, 2009 at 8:56 PM, Brian Fox <bri...@infinity.nu> wrote: > You need a repository manager. > > On Thu, Nov 5, 2009 at 4:22 AM, Stevo Slavić <ssla...@gmail.com> wrote: > > I'm experiencing similar issue. maven2-repository.dev.java.netrepository is > > not defined in any of my project modules, but it is in project's 3rd > party > > dependencies. These dependencies were uploaded on central repo with rule, > > that dependencies on central aren't allowed to reference external > > repositories, not obeyed (create > > issue<http://jira.codehaus.org/browse/MEV-643>for this). When I > > install project Maven seems to generate these > > maven-metadata-%external-repo%.xml files. But if build includes site > > generation with maven-project-info-reports-plugin:dependencies:2.1.2 > report > > generation, these metadata files seem to be updated in a way which makes > > every next build to fail with "Reason: Error getting POM for...", "Unable > to > > read local copy of metadata: Cannot read metadata from ..." error > messages. > > > > Regards, > > Stevo. > > > > On Wed, Aug 12, 2009 at 8:03 PM, Brian Fox <bri...@infinity.nu> wrote: > > > >> Actually it looks like you're using a bad url to the repository. You > >> should instead use: > >> http://download.java.net/maven/2 > >> > >> On Wed, Aug 12, 2009 at 1:51 PM, Arrowx7<aluminum3...@yahoo.com> wrote: > >> > > >> > Ok I reached something that I feared with maven: unable to get > >> dependency. > >> > > >> > When I try to build my project, i get this: > >> > > >> > Project ID: org.apache.maven.plugins:maven-site-plugin > >> > > >> > Reason: Error getting POM for > >> 'org.apache.maven.plugins:maven-site-plugin' > >> > from the repository: Unable to read local copy of metadata: Cannot > read > >> > metadata from > >> > > >> > '/home/usr/.m2/repository/org/apache/maven/plugins/maven-site-plugin/maven-metadata-maven2-repository.dev.java.net.xml': > >> > end tag name </body> must match start tag name <hr> from line 7 > >> (position: > >> > TEXT seen ...</address>\n</body>... @9:8) > >> > org.apache.maven.plugins:maven-site-plugin:pom:LATEST > >> > > >> > for project org.apache.maven.plugins:maven-site-plugin > >> > > >> > I checked > >> > > >> > /home/usr/.m2/repository/org/apache/maven/plugins/maven-site-plugin/maven-metadata-maven2-repository.dev.java.net.xml > >> > file and it gives me: > >> > > >> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > >> > <html><head> > >> > <title>301 Moved Permanently</title> > >> > </head><body> > >> > <h1>Moved Permanently</h1> > >> > <p>The document has moved > >> > > >> > http://download.java.net/maven/2/org/apache/maven/plugins/maven-site-plugin/maven-metadata.xml > >> > here .</p> > >> > <hr> > >> > <address>Apache Server at maven2-repository.dev.java.net Port > >> 443</address> > >> > </body></html> > >> > > >> > > >> > If I go to the specified link it says "Page cannot be found". Am I > >> > permanently stuck? I searched my project for maven-site-plugin and > did > >> not > >> > find anything. Why is it trying to get that anyway? Is the > repository > >> down > >> > and I can NOT compile until it reopens? Please advise me how to fix > it. > >> I > >> > am a maven newbie. However, I do know for a fact that this same build > >> > worked a month ago! Please advise me on what to do. > >> > -- > >> > View this message in context: > >> > http://www.nabble.com/Suck%2C-cannot-build%2C-repository-down---tp24941611p24941611.html > >> > Sent from the Maven - Users mailing list archive at Nabble.com. > >> > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: users-h...@maven.apache.org > >> > > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
