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
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
Justin,
Yes we would but obviously the license on those binaries is important.
Some of the original binaries couldn't be redistributed which is why
they were pulled from central years ago.
On Thu, Feb 25, 2010 at 10:28 AM, Justin Edelson
justinedel...@gmail.com wrote:
Jason-
As I commented on
Hi,
On Thu, Feb 25, 2010 at 10:36 AM, Brian Fox bri...@infinity.nu wrote:
Justin,
Yes we would but obviously the license on those binaries is important.
Some of the original binaries couldn't be redistributed which is why
they were pulled from central years ago.
Well, one thing that could
On 2/25/10 10:36 AM, Brian Fox wrote:
Justin,
Yes we would but obviously the license on those binaries is important.
Some of the original binaries couldn't be redistributed which is why
they were pulled from central years ago.
...obligatory IANAL...
My understanding, and I could be wrong
On Feb 25, 2010, at 10:56 AM, Justin Edelson wrote:
On 2/25/10 10:36 AM, Brian Fox wrote:
Justin,
Yes we would but obviously the license on those binaries is important.
Some of the original binaries couldn't be redistributed which is why
they were pulled from central years ago.
On 2/25/10 10:47 AM, Jesse Farinacci wrote:
Hi,
On Thu, Feb 25, 2010 at 10:36 AM, Brian Fox bri...@infinity.nu wrote:
Justin,
Yes we would but obviously the license on those binaries is important.
Some of the original binaries couldn't be redistributed which is why
they were pulled from
