Steve Loughran wrote:
Stephane Bailliez wrote:
You will change the metadata. If you want reproductability (and you
will want that) then version your repository.
ahh, now there's a thought.
Rather than seek stability, let you say you want to build against last
month's version of the metadata. We could do this if the public
repository were actually a viewsvn front end to an SVN repo.
Of course, this gets complex fast. You dont want to depend on the
2006-11-08 repository for one artifact, and the 2006-11-03 for another...
Does not need to be complex unless you want it to be and not observing
rules. It is all about having one unique configuration parameter saying
"I depend on that". If you are on a team and people are not following
that and doing there own stuff, sure problem will happen, but it is not
as different as people developing module A using third party 1.1 and
people developing B using third party 2.0 while they are incompatible
and that these modules are bound to join in the future... you would very
much prefer everybody to use the same version 90% of the time, the 10%
remaining time being for emergency case, where simply put, you depend on
another third party which depends on 1.1.
