Having consistency is definitely in ours and Maven's best interest. We (us and the Maven guys) need
to examine how people manage their versions. Derby is clearly a case where 4 elements is standard.
I also agree with David that more dots isn't necessarily good but I've also noticed on the user
cc
PM
Subject
Re: Repository version precedence
Re: Repository version precedence
Please respond to
[EMAIL PROTECTED]
Joe Bohn wrote:
Am I the only one concerned about this?
I am also concerned, just been a bit busy to respond. See comments
inline below.
I think this is an important issue for our users. They won't have the
luxury to wait for a completely new Geronimo image to fix a problem
with an embedde
David,
I understand your point about potential confusion if we extend the maven
capabilities. However, I have to wonder how many of our users are
familiar with maven and if this is important to them.
If we are to stay closely aligned with Maven, then I agree with you that
need to pursue som
On May 30, 2006, at 10:49 AM, Joe Bohn wrote:
Am I the only one concerned about this?
I think this is an important issue for our users. They won't have
the luxury to wait for a completely new Geronimo image to fix a
problem with an embedded component. They will also face these
issues w
Am I the only one concerned about this?
I think this is an important issue for our users. They won't have the
luxury to wait for a completely new Geronimo image to fix a problem with
an embedded component. They will also face these issues with their own
versioned application modules. I woul
I'm trying to get my head around the way that we make a version
selection when multiple versions of a package are available. This will
be important as users need to include different versions of packages
beyond what geronimo bundles or if they need to override a package with
a local version.
