Re: [CLI] two different versions of commons-cli-1.0.jar?

[Torsten Curdt]

As noted in a separate email, an RC is up for review.

Awesome! Thanks, Simon!

There is one question still to be decided though: do we *delete* the
existing 1.0 jar from ibiblio, or replace it with the right one.

I've argued for deleting it because otherwise projects that declare
dependencies on 1.0 will work differently when compiled on different
systems depending on what version (if any) is in the maven cache.

Yepp ...that's the problem :-/

So person A can compile (getting the snapshot) and see a certain

behaviour. Person B can compile the same software on a different machine (getting the correct 1.0) and see different behaviour. Very confusing.

Yes ...I think you are right we should avoid
that. Sounds like people could end up spending
quite some time finding the cause for it.

I would rather see person B get an error message saying that
commons-cli-1.0.jar cannot be found on ibiblio.

Otherwise his build is interrupted for nothing.

No. If B already has the wrong one in his local cache, it will be used.

I think you missed the point that A has it
...B does not. And B is tearing his hair out
why it does not work for him.

Replacing the bad 1.0 with the good one at this point is probably not a good idea either. Again, we have the issue where someone has a working

product based on the snapshot (under the illusion it is the real
release). By replacing this with the "real" 1.0 we could potentially

to resolve the issue by hand.

break their product if they depend on behaviour present in the snapshot but not the real release. Instead, removing the bad 1.0 will alert them

commons-io homepage.

No. Since they already have it, they will never recognize on their own. If they get alerted by their customers, they will find out anyway. Just put a readme in the repo as it is done for the XML APIs and some prominent hint on

Actually, we should probably continue to make the bad 1.0 available but under a different name for the use of people who want to continue using

it. I'd be happy to go in and rename the jar right now, to something
like
  commons-cli-1.0-snapshot.jar
if there is agreement on that.

1.1-alpha-1 ?

Are we sure of the exact version?
Otherwise some 1.0-mixup might do it.

So to summarise, here are the options I see:
  A: replace bad 1.0 jar with good 1.0 jar
  B: rename bad 1.0 jar, do NOT provide any commons-cli-1.0.jar
  C: leave bad 1.0 jar as-is


Here's my opinion:
 A: -0
 B: +1
 C: -0

I think we should...

rename commons-cli-1.0.jar to commons-cli-1.0-bad.jar
provide commons-cli-1.0.1.jar
maybe provide commons-cli-1.0-proper.jar

cheers
--
Torsten

PGP.sig
Description: This is a digitally signed message part