I may be out to lunch here, but the m2 public repositories seem to be getting worse.
the one that finally got me to write this was the dependency plugin, which is listed on the main maven plugin list. http://maven.apache.org/plugins/maven-dependency-plugin/ Now I don't know if the documentation is wrong for this particular plugin or is it wasn't published, but as far as I can see org.apache.maven.plugin:dependency-maven-plugin doesn't exist. I did check repo1.maven.org and found something under maven:maven-dependency-plugin:1.0 but who knows what the heck that is! This is not the first time I've had to do some fancy footwork to deal with plugins that should be available but are not (it usually requires me finding it's origin and manually installing it). A lot of them come from the Codehaus Mojo project and appear to be moving to repo1 (with new groupId's) and are documented as standard plugins. Would the powers that be *please* validate what is supposed to be published with what is/is not published. This is getting very annoying. Of course, I may have missed some "special announcement" or something but I shouldn't have to be doing funky configuration or manual installs for my "build anywhere" m2 projects! I hope I haven't offended anyone, but being the loud-mouth that I am, I thought I'd start making some noise. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
