Geir Magnusson Jr <[EMAIL PROTECTED]> writes:

>On Nov 30, 2004, at 8:23 AM, Henning P. Schmiedehausen wrote:

[...]
>> I tried to get exactly that point across (Project X does rely on
>> Version n of Project Y, not the HEAD) but failed. Maybe you are more
>> successful...

>This has been the basic issue since Gump was started.  It's good at 
>showing when someone breaks an API contract, such as this case.  What 
>it can't seem to handle is the legitimate case of API breakage in major 
>revisioning.

Yep.

>If log4j was doing this going from 1.2.9 to 2.0, then I'd probably have 
>to wave off any complaints.  But 1.2.9 to 1.3?  sorry - I can't see why 
>they are doing this, as they have historically been so good about 
>smooth, manageable changes in the log4j API.

>This further supports my belief that you always want to minimize 
>dependencies.

This is why I tried to lobby for commons-logging here a while
ago. Using commons-logging, this change would have been invisible
because c-l separates the library from the logging API.

>My strategy here is to try and get them to at least give us a 
>deprecated o.a.l.RFA for 1.3.0 so we can switch to a released version, 
>and then immediately we switch to using the RFA in the rolling package.

+1

>The other option is to play classpath wack-a-mole and just no have any 
>hard imports, do everything via classloader discovery, and wait until 
>this is over...

/me barfs. Please not. In Turbine, we used commons-logging with great
success. All the log4j stuff disappeared into the log4j.properties
file. Ok, you would have to adjust this.

        Regards
                Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
[EMAIL PROTECTED]        +49 9131 50 654 0   http://www.intermeta.de/

RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
   Linux, Java, perl, Solaris -- Consulting, Training, Development

What is more important to you...
   [ ] Product Security
or [ ] Quality of Sales and Marketing Support
              -- actual question from a Microsoft customer survey

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to