On Thu, Sep 02, 2010 at 09:37:04AM -0500, Tim Donohue wrote: > I agree with Robin's point. We need to change our Committer practices > so that we make sure to run through the Unit Tests *before* committing > code (and we also need to be updating the Unit Tests when adding new > code/methods). I'll write myself a note to bring this up at our next > Developers Meeting.
I think we need to change the way the tests are activated. As long as
this is subject to a manual operation I'm very likely to forget it.
It's wrapped in a profile now, but that only replaces:
mvn -DsomethingIAlwaysForget
with:
mvn -PsomethingIAlwaysForget
I'd like to see this profile activated by something which can be
persistent, like a flag file:
<profile>
<id>skiptests</id>
<activation>
<activeByDefault>false</activeByDefault>
<file>
<missing>development.flag</missing>
</file>
</activation>
<properties>
<maven.test.skip>true</maven.test.skip>
</properties>
</profile>
or the absence of an environment variable:
<profile>
<id>skiptests</id>
<activation>
<activeByDefault>false</activeByDefault>
<property>
<name>!env.DEVELOPMENT</name>
</property>
</activation>
<properties>
<maven.test.skip>true</maven.test.skip>
</properties>
</profile>
Comments?
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your desire for bells and whistles with the reality that only a
little more than 2 percent of world population has broadband.
-- Ledford and Tyler, _Google Analytics 2.0_
pgp980dKC0s36.pgp
Description: PGP signature
------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
