On Tue, Mar 23, 2010 at 08:05, Jean-Philippe Caruana < [email protected]> wrote:
> Le 23/03/2010 15:44, Antoine Toulme a écrit : > > It's a bit delicate: we can't know for sure that nothing changed. >> > > But, if nothing changed (no file changed on other projects, so tests are > always ok), I don't need to rerun tests, as I don't need to re compile. > > When i do "buildr compile test=no", the 1st time it does compile every > project. The 2nd time I launch "buildr compile test=no", it does not compile > any of them since nothing changed. > I thought it would be the same behaviour for testing, otherwise I don't see > the point. Let me quote the online documentation about projects : > "In reality, it does the right thing. A simple rule to remember is that > each project definition is executed before you need it, lazy evaluation of > sort. The reason we do that? So you can write projects that depend on each > other without worrying about their order." > What did I miss ? How can compile be different from testing ? > > > You could have changed the version of a dependency in your Buildfile > > How can I detect a change on my buildfile ? > Can I add a file task dependency on the buildfile ? A Buildfile is a dynamic object - meaning it can fetch the dependency numbers from somewhere else, an other file, or using some mechanism. No, that won't cut it. > > > > or the tests require internet access. > > not in my project : we just do unit testing ( > http://www.artima.com/weblogs/viewpost.jsp?thread=126923). we use CI for > other testingm purposes (acceptance, integration etc) OK, but as a rule of thumb, we won't know about it for sure. > > > To avoid running tests, you can do: >> buildr package test=NO >> > > That's not what I want : I want to run tests for my artifact and not for > the other projects, so I can't use "test=no". > You can run tests for a particular project. Here for example: buildr myProject:artifactToBuild:test HTH Antoine > > -- > Jean-Philippe Caruana - [email protected] > Tel : 01 53 90 85 33 / 1533 - Projet AVSP > ******************************** > Ce message et toutes les pieces jointes (ci-apres le "message") sont > confidentiels et etablis a l'intention exclusive de ses destinataires. > > Toute utilisation ou diffusion non autorisee est interdite. > Tout message electronique est susceptible d'alteration. Multimedia Business > Services decline toute responsabilite au titre de ce message s'il a ete > altere, deforme ou falsifie. > > Si vous n'etes pas destinataire de ce message, merci de le detruire > immediatement et d'avertir l'expediteur. > ********************************* > This message and any attachments (the "message") are confidential and > intended solely for the addressees. Any unauthorised use or dissemination is > prohibited. > Messages are susceptible to alteration. Multimedia Business Services shall > not be liable for the message if altered, changed or > > falsified. > If you are not the intended addressee of this message, please cancel it > immediately and inform the sender. > ******************************** > >
