where to store jars?

[Wes Freeman]

So, I liked the idea of storing poms in a github repo that you'd clone initially and fetch the latest stuff periodically.

Do we leave legacy jars where they are? On maven central, etc.? Or is that not good enough... Mark talked about new ways of publishing--but is that only for the new stuff?

Just throwing this out there to continue the conversation.

Wes

[Mark Harrah]

On Wed, 20 Feb 2013 15:08:54 -0500
Wes Freeman <freem...@gmail.com> wrote:

> So, I liked the idea of storing poms in a github repo that you'd clone
> initially and fetch the latest stuff periodically.
>
> Do we leave legacy jars where they are? On maven central, etc.? Or is that
> not good enough... Mark talked about new ways of publishing--but is that
> only for the new stuff?

I added all of my notes here:

https://github.com/sbt/adept/wiki/NEScala-Proposal

The Compatibility section lists one idea I had after the question after the talk about whether it would be possible to avoid converting poms. I had answered that I thought that conversion was necessary at some point, but it might be possible to avoid that, at least for an initial implementation.

In the case where poms are pulled and converted, I would say there are two options. One is to proxy them in the hash-based repository. The other option is probably more practical and that is to have a fallbackURL attribute that specifies where to get an artifact if it isn't present in a hash-based repository. This would still verify the hash of the jar when retrieved.

-Mark