Jason- As I commented on your blog entry, what I think would be most useful is to handle the currently deployed javax.* artifacts. Don't get me wrong, dealing with the current/new releases will be helpful.
Would Sonatype be willing to accept a list of artifact submissions from the community and then proactively work with the responsible project teams? For anyone running an caching MRM, it should be trivial to look in the cache for the java.net repo. Culling this list should be fairly straight forward. If the goal is to eliminiate (not just reduce) the dependency on the java.net repo, I'm pretty sure something like the above will need to be done. Justin On 2/25/10 10:15 AM, Jason van Zyl wrote: > As Maven users if you care about the quality of the Maven Repositories at > Java.net then please help support us in our effort to get Snorcle to help fix > the situation. > > Sonatype is going to try and help by dedicating staff on March 5th to help > Java.net projects transition over to a healthy Maven repository > infrastructure: > > http://www.sonatype.com/people/2010/02/java-net-maven-repository-rescue-mission-on-march-5th/ > > We already have support from Jean-Francois Arcand: > > http://weblogs.java.net/blog/jfarcand/archive/2010/02/25/pain-over-javanets-maven-artifacts > > Please show your support by voting on the DZone article here, which seems to > draw attention: > > http://www.dzone.com/links/javanet_maven_repository_rescue_mission_on_march.html > > It's all about visibility and if we have enough users in the Maven community > raise this as a concern then maybe we'll get somewhere this time. > > And if you're a project at Java.net please let us help you on March 5th! > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > ---------------------------------------------------------- > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
