Don't worry - you aren't the only person annoyed by the inconsistencies of the repos.
Alex On 9/10/06, Brill Pappin <[EMAIL PROTECTED]> wrote:
Sorry for the tone... it's both an ongoing problem (which sounds like it's being delt with) and a short fuse :) It may be that I'm having to use a lot of plugins that are not as "mainstream" as most people are using, but I have had the same problem with others that say they are public. Until now, I've just chaulked it up to a delay in deployment by the plugin developers and went about finding a solution... however the "short fuse" comes from having it happen several times in the last few months. Admittedly, codhaus itself has this problem much more often but this time is was the main m2 site documentation. Thanks for paying attention, - Brill Pappin On 9/10/06, Brett Porter <[EMAIL PROTECTED]> wrote: > Is this a general problem, or just a short fuse? > > The dependency plugin is a known problem, which I *thought* had been > fixed documentation wise recently. I was pushing for it to be moved > back to the sandbox since it hasn't seen a release since it was moved > to Apache (originally put together at mojo). > > You probably want to use mojo's last release, dependency-maven-plugin, for now. > > If there are other problems, bring them up and they'll get fixed. > > - Brett > > On 10/09/06, Brill Pappin <[EMAIL PROTECTED]> wrote: > > 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] > > > > > > > -- > Apache Maven - http://maven.apache.org > "Better Builds with Maven" book - http://library.mergere.com/ > > --------------------------------------------------------------------- > 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]
