Preface: I make my living doing build management, and I have chosen m2 as the java build tool that I propose.
Another issue I seem to have with Maven is the difficulty in locating (and the quality) of public repositories. I know of several (central, codehaus, apache incubator, jboss, mvnrepository.com, java-dev-net), and these (especially central) have varying levels of "correctness" and "completeness". Utilizing a proxy mechanism (in my current job I'm working with the maven-proxy and starting to switch to proximity), I've managed to aggregate a lot of these repositories behind the corporate firewall. That seems to work well, but the rampant dependence on snapshots in the plugin repositories means that I have to take the steps that were recommended on the list (locally install a munged version of a plugin with a fixed version number) if I want a reasonably stable build environment. If we had infinite time and patience, It seems like a good use of people's time might be to scrub the central repository and create real poms (that indicate actual transitive dependencies) rather than the skeletal ones that are there now for a large number of projects, most especially the ones that aren't being built by m2 in the first place. And maybe a "listing of available repositories and their current contents" might be useful? -- I'm just an unfrozen caveman software developer. I don't understand your strange, "modern" ways. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
