The general consensus is that Martin is a bot. The idea is that we write tests that cover all the functionality of plexus-utils (preference is to write tests without looking at the plexus-utils code so that the tests are somewhat clean-room, but there is no hard requirement in this case... the desire is more to ensure that they are good tests)
That will give us a good test coverage of plexus-utils... Then we implement a new plexus-utils that passes all the tests but has a completely different implementation (one which just calls through to the commons-* code that does similar/same) When all the tests pass on our new implementation, we have a drop in replacement for plexus-utils. We can then work on replacing plexus-utils with the commons-* code directly (IntelliJ IDEA can really help here if you just take a copy of the shim and request to inline each of the statics and remove intermediates from your delegation chains... when done you remove the now defunct copy of the shim) So the real aim is to get the replacement for all the legacy code (and in so doing we work out how to replace it) and then once we are there we can rip out plexus-utils from the trunk and leave the shim for any old versions of plugins. -Stephen On 24 May 2011 12:15, Mark Struberg <strub...@yahoo.de> wrote: > Hi Martin! > > The idea is about doing a misture between Test Driven Development and > BlackBox Testing / Unit Testing. > > LieGrue, > strub > > --- On Tue, 5/24/11, Martin Gainty <mgai...@hotmail.com> wrote: > >> From: Martin Gainty <mgai...@hotmail.com> >> Subject: RE: Anyone want to help? >> To: dev@maven.apache.org >> Date: Tuesday, May 24, 2011, 10:29 AM >> >> isnt the job of the software engineer to write test-cases >> to prove their software works? >> >> Martin >> ______________________________________________ >> Verzicht und Vertraulichkeitanmerkung/Note de déni et de >> confidentialité >> >> Diese Nachricht ist vertraulich. Sollten Sie nicht der >> vorgesehene Empfaenger sein, so bitten wir hoeflich um eine >> Mitteilung. Jede unbefugte Weiterleitung oder Fertigung >> einer Kopie ist unzulaessig. Diese Nachricht dient lediglich >> dem Austausch von Informationen und entfaltet keine >> rechtliche Bindungswirkung. Aufgrund der leichten >> Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer >> den Inhalt uebernehmen. >> Ce message est confidentiel et peut être privilégié. Si >> vous n'êtes pas le destinataire prévu, nous te demandons >> avec bonté que pour satisfaire informez l'expéditeur. >> N'importe quelle diffusion non autorisée ou la copie de >> ceci est interdite. Ce message sert à l'information >> seulement et n'aura pas n'importe quel effet légalement >> obligatoire. Étant donné que les email peuvent facilement >> être sujets à la manipulation, nous ne pouvons accepter >> aucune responsabilité pour le contenu fourni. >> >> >> >> >> > Date: Tue, 24 May 2011 10:28:13 +0100 >> > Subject: Anyone want to help? >> > From: stephen.alan.conno...@gmail.com >> > To: dev@maven.apache.org >> > >> > I'm working on providing a compatibility layer for >> plexus-utils that >> > uses the commons-* stuff to provide the >> implementation. >> > >> > If anyone is interested in helping please shout out. >> > >> > Most of the work is actually writing the crazy test >> cases, everything >> > else should be simple shims through to existing >> commons functionality. >> > >> > You can join in here if you are an Apache Committer >> (sandbox is open >> > to all Apache Committers) >> > https://svn.apache.org/repos/asf/maven/sandbox/trunk/plexus-utils-commons-bridge >> > >> > Pick a plexus-utils class, and start creating tests... >> better still >> > write the tests black box (that's what I am doing!) >> > >> > Then when you have some tests written in the TCK >> module, create the >> > implementation class with all the methods: >> > >> > { throw new UnsupportedOperationException("Not >> implemented yet!"); } >> > >> > and then you can knock off implementations and see >> your test pass rate >> > rise in the bridge module. >> > >> > I'm tackling IOUtil first and then PropertyUtils. >> > >> > To stake your claim, commit the test case class first >> and then unless >> > you tell us otherwise you are working on that class! >> > >> > -Stephen >> > >> > >> --------------------------------------------------------------------- >> > 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
