You've also just lost decent autocomplete in IDEs, etc.
I think the URIs make sense for when you're in a context where such a
thing might make sense (the PAX / ServiceMix Kernel example comes to
mind), but to force people to mentally translate a model to a URI when
they are thinking in terms of separate pieces is unnecessary just to
save a few bytes.
- Brett
On 28/05/2009, at 12:24 PM, Brian Fox wrote:
The problem with this is two-fold actually,
The url representation currently doesn't encapsulate the other parts
of the
dependency declaration like optional or scope. Further, it is
difficult to
deterministically reverse a url like that back to the GAV
components... we
struggle with this often in Nexus when people have unusual artifact
or group
ids that make it hard for example to separate the group from the
artifact,
or the version from the classifier.
On Wed, May 27, 2009 at 2:06 PM, Jorg Heymans
<jorg.heym...@gmail.com>wrote:
On Wed, May 27, 2009 at 3:55 PM, Christian Edward Gruber
<christianedwardgru...@gmail.com> wrote:
Anyway, I'm +1 on this. It is clear, unambiguous, and terse.
Those work
for me.
My thoughts exactly !
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
