Thanks, I think this covers it: latest version of each point release on
the mirrors, and an automatic decommissionning based on usage for older
ones, with redirection to archives.
P@
Nick Chalko wrote:
Good point.
I think in general mirrors should be able to choose whatever subset
they want.
Bu
Good point.
I think in general mirrors should be able to choose whatever subset they
want.
But apache should maintain at lest "the latest version of each point
release"
Mark R. Diggory wrote:
With the amount of versioning going on, eventually a release falls
into a state of non-usage, I suspect
With the amount of versioning going on, eventually a release falls into
a state of non-usage, I suspect there should be room for such a
mechanism, otherwise mirrors will become bloated with unused, outdated,
antiquated and obsolete content.
I suspect some sort of "redirect" mechanism would be s
Patrick Chanezon wrote:
Did you specify a lifecycle for artifacts, with some durations, and a
process to decommision them ?
Good question. This may be something to put to the board.
My general thought are.
"Released" version should live forever, unless a security or other fatal
flaw is found
Hi all,
I've been lurking in that list (repository) for a while, because the
topic of repositories is of interest to me.
I think that maven will have a big effect on java development and I
understand that the apache repository will be where maven stores its
jars (not sure about that but that wou
