No, there's no need to "fork" for different unit tests. JUnit 4 will run the 
old tests just fine, along with the new. All I have done is update my 
dependency, like so:


    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>4.8.1</version>
        <scope>test</scope>
    </dependency>

Existing tests run, and I can also create and run unit tests using new features 
(@Test annotation and such).

~Daniel

-----Original Message-----
From: Martin Gainty [mailto:mgai...@hotmail.com] 
Sent: Wednesday, June 09, 2010 10:11 AM
To: dev@maven.apache.org
Subject: RE: Re : Moving to TestNG JUnit4?


Dan and crew

i have seen junit configured as a Resource in the process phase by 
maven-remote-resources-plugin as in:

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-remote-resources-plugin</artifactId>
                <executions>
                    <execution>
                        <goals>
                            <goal>process</goal>
                        </goals>
                        <configuration>
                            <resourceBundles>
                            <resourceBundle>junit:junit:4.7</resourceBundle>
                            </resourceBundles>
                            
<outputDirectory>${project.build.directory}/${build.finalName}</outputDirectory>
                            <attached>false</attached>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

is this what you are referring or is there an alternate forking mechanism?


Martin Gainty 
______________________________________________ 
Jogi és Bizalmassági kinyilatkoztatás/Verzicht und 
Vertraulichkeitanmerkung/Note de déni et de confidentialité


 
Ez az üzenet bizalmas.  Ha nem ön az akinek szánva volt, akkor kérjük, hogy 
jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának készítése 
nem megengedett.  Ez az üzenet csak ismeret cserét szolgál és semmiféle jogi 
alkalmazhatósága sincs.  Mivel az electronikus üzenetek könnyen 
megváltoztathatóak, ezért minket semmi felelöség nem terhelhet ezen üzenet 
tartalma miatt.

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.



 

> Subject: RE: Re : Moving to TestNG JUnit4?
> Date: Wed, 9 Jun 2010 15:52:24 +0200
> From: daniel.siegm...@fja-us.com
> To: dev@maven.apache.org
> 
> I have similar experience. I upgraded a couple of projects to JUnit 4.8.1 
> (from 3.x) in the past few months. Leaving the old tests as-is has worked 
> fine, while allowing me to write new tests in the new style, just as you 
> propose.
> 
> Seems like the best approach to me.
> 
> ~Daniel Siegmann
> 
> -----Original Message-----
> From: Julien HENRY [mailto:henr...@yahoo.fr] 
> Sent: Wednesday, June 09, 2010 8:29 AM
> To: Maven Developers List
> Subject: Re : Moving to TestNG JUnit4?
> 
> > JUnit 4 apparently runs JUnit 3 tests out of the box
> 
> I can confirm that (starting from JUnit 4.7 if I remember correctly). I 
> usually upgrade all my projects to JUnit 4. This way I can write new tests 
> using JUnit 4 style and keep old tests with JUnit 3 style.
> 
> My 2 cts
> 
> ++
> 
> Julien
> 
> 
> 
> ----- Message d'origine ----
> > De : Mark Derricutt <m...@talios.com>
> > À : Maven Developers List <dev@maven.apache.org>
> > Envoyé le : Mer 9 juin 2010, 14h 24min 56s
> > Objet : Re: Moving to TestNG JUnit4?
> > 
> > JUnit 4 apparently runs JUnit 3 tests out of the box, so one could 
> > feasibly
> change the dependencies to JUnit 4 at least. I understand the 
> > reasons for
> not physically changing old tests for the sake of change 
> > tho.
> 
> Mark
> 
> -- 
> Pull me down under...
> 
> On Tue, Jun 8, 2010 
> > at 6:29 AM, Jason Chaffee <
> > href="mailto:jchaf...@ebates.com";>jchaf...@ebates.com> wrote:
> 
> > 
> > FYI, JUnit now supports concurrent running of tests.
> >
> 
> 
> 
> 
> ---------------------------------------------------------------------
> 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
> 
                                          
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your 
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to