>> Is there someone taking ownership of getting a working CI on p.a.o? > > It's a bit more than that, since two of the snapshots are from codehaus and > wouldn't be deployed there anyway. A better thing to do is not depend on > snapshots for so long :)
Agreed. I was hoping to make a quick change when this caused me more work than was needed. I'm hoping someone from the plexus group will take ownership of building the snapshots automatically. If the plexus snapshot repo isn't going to be http://snapshots.repository.codehaus.org then wherever it is going to be needs to be well publicized and preferably in the maven developers setup guide. Admittedly I haven't rechecked there before starting this mail thread... Having just rechecked http://maven.apache.org/developers/index.html it doesn't even list the snapshots I've previously posted. I vaguely remember getting them via email a long time ago. I'll update that doc once something is decided upon. > However, for the ones internal to the project, there is no reason we can't > get this done. [del] > I've definitely been slack on this... because Maven is really the project I > need it most for, and setting it up in that way has been contentious to say > the least. I'm more than happy to set it up on vmbuild (even just for a > subset of shared components) if there's already some agreement that should > be done, but don't think it's worth causing any further arguments over. I'm interested in removing the barrier for the casual tweaker (like me) who feels some pain and would like to fix it and get out again. So if we can get each of the owners of the Related Projects listed at http://maven.apache.org/guides/development/guide-m2-development.html to continuously deploy snapshots then we can publicize where they are for easy consumption that would be the ideal. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
