Once multiple resolution strategies start appearing, life will be
infinitely more complicated. If you use a different strategy and I
consume your artifacts, I need to be able to interpret your strategy and
use it when calculating your part of the tree. (and someone else's etc).
That means the
Which is why I think that the rules need to be defined at the
repository, and per groupId
2009/2/10 Brian E. Fox bri...@reply.infinity.nu:
Once multiple resolution strategies start appearing, life will be
infinitely more complicated. If you use a different strategy and I
consume your
On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
Which is why I think that the rules need to be defined at the
repository, and per groupId
That's just a nightmare. What's wrong with just settling on something
that works for everyone. I really and truly can't honestly see how the
OSGi
Stephen Connolly schrieb:
What I'm thinking is that if we had some metadata associated with the
groupId, it could specify what the version comparison rule is for that
groupId (and all it's child groupIds)...
It would be very cool to have some general purpose grouplevel metadata!
Various things
Christian Schulte schrieb:
Stephen Connolly schrieb:
What I'm thinking is that if we had some metadata associated with the
groupId, it could specify what the version comparison rule is for that
groupId (and all it's child groupIds)...
It would be very cool to have some general purpose
2009/2/10 Jason van Zyl jvan...@sonatype.com:
On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
Which is why I think that the rules need to be defined at the
repository, and per groupId
That's just a nightmare. What's wrong with just settling on something that
works for everyone. I really
Brian E. Fox wrote:
Once multiple resolution strategies start appearing, life will be
infinitely more complicated.
yes :( I think Mercury has a pretty decent potential to cover majority
of the reasons to change version comparisons. For example - there is a
notion of version quality and
On 10-Feb-09, at 11:33 AM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl jvan...@sonatype.com:
On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
Which is why I think that the rules need to be defined at the
repository, and per groupId
That's just a nightmare. What's wrong with just
2009/2/10 Jason van Zyl jvan...@sonatype.com:
On 10-Feb-09, at 11:33 AM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl jvan...@sonatype.com:
On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
Which is why I think that the rules need to be defined at the
repository, and per groupId
On 10-Feb-09, at 1:06 PM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl jvan...@sonatype.com:
On 10-Feb-09, at 11:33 AM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl jvan...@sonatype.com:
On 10-Feb-09, at 8:37 AM, Stephen Connolly wrote:
Which is why I think that the rules need to
Sent from my [rhymes with myPod] ;-)
On 10 Feb 2009, at 19:05, Jason van Zyl jvan...@sonatype.com wrote:
On 10-Feb-09, at 1:06 PM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl jvan...@sonatype.com:
On 10-Feb-09, at 11:33 AM, Stephen Connolly wrote:
2009/2/10 Jason van Zyl
11 matches
Mail list logo
