Re: [jbosscache-dev] Migration to Subversion and Maven

Can we still run tests individually? I am getting failures.... C:\work\repos\jboss-cache-trunk>mvn test -Dtest=*StateTransfer200Test [INFO] Scanning for projects... WAGON_VERSION: 1.0-beta-2 [INFO] ---------------------------------------------------------------------------- [INFO] Building JBoss Cache - Core Edition [INFO] task-segment: [test] [INFO] ---------------------------------------------------------------------------- [INFO] [enforcer:enforce {execution: enforce-java}] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] Copying 32 resources [INFO] [compiler:compile] [INFO] Compiling 290 source files to C:\work\repos\jboss-cache-trunk\target\classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] [compiler:testCompile] [INFO] Compiling 292 source files to C:\work\repos\jboss-cache-trunk\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: C:\work\repos\jboss-cache-trunk\target\surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- [Parser] Running: Command line suite Running org.jboss.cache.statetransfer.StateTransfer200Test *** in tearDown() *** in tearDown() *** in tearDown() *** in tearDown() *** in tearDown() *** in tearDown() *** in tearDown() *** in tearDown() *** in tearDown() *** in tearDown() Tests run: 10, Failures: 10, Errors: 0, Skipped: 0, Time elapsed: 0.422 sec <<< FAILURE! Results : Failed tests: testBuddyBackupExclusion(org.jboss.cache.statetransfer.StateTransfer200Test) testBuddyIntegration(org.jboss.cache.statetransfer.StateTransfer200Test) testCacheLoaderFailure(org.jboss.cache.statetransfer.StateTransfer200Test) testLoadEntireStateAfterStart(org.jboss.cache.statetransfer.StateTransfer200Test) testInitialStateTransfer(org.jboss.cache.statetransfer.StateTransfer200Test) testInitialStateTferWithLoader(org.jboss.cache.statetransfer.StateTransfer200Test) testInitialStateTferWithAsyncLoader(org.jboss.cache.statetransfer.StateTransfer200Test) testPartialStateTransfer(org.jboss.cache.statetransfer.StateTransfer200Test) testPartialStateTferWithLoader(org.jboss.cache.statetransfer.StateTransfer200Test) testPartialStateTferWithClassLoader(org.jboss.cache.statetransfer.StateTransfer200Test) Tests run: 10, Failures: 10, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] There are test failures. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 12 seconds [INFO] Finished at: Wed Aug 15 15:57:19 EDT 2007 [INFO] Final Memory: 13M/49M [INFO] ------------------------------------------------------------------------ C:\work\repos\jboss-cache-trunk> Manik Surtani wrote: > Everyone, this is now complete and ready for business. A brief update > on a few things: > > * core [1] and pojo [2] are now separate modules in the subversion > repository - this announcement pertains to 'core' only. Jason will > probably announce 'pojo' later. > * Read the JBoss Cache Dev [3] wiki page for details on connecting. > * We're now using Maven2 to build (see the README-maven.txt [4] file > in the src tree for details) > * We've switched to TestNG for the unit tests. While the test > migration is still WIP, I thought this is still worth mentioning > here. Any new tests written should use TestNG and not JUnit. > * See sample conversion from JUnit to TestNG - o.j.c.FqnTest [5] > * The 'recommended' way of using JBoss Cache in your code is to use > Maven2. From 2.1.0, JBoss Cache will reside in JBoss.org's maven > repository [6] and snapshots will be available in the JBoss.org > snapshot repository [7]. > * Maven2 groupId = org.jboss.cache, artifactId = jbosscache-core or > jbosscache-pojo > > Please let me know if you have any issues with these changes. Commit > privileges should have been moved across, let me know if there are any > issues. > > Cheers, > Manik > > > > [1] https://svn.jboss.org/repos/jbosscache/core/ > [2] https://svn.jboss.org/repos/jbosscache/pojo/ > [3] http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheDevelopment > [4] > http://fisheye.jboss.com/browse/~raw,r=4259/JBossCache/core/trunk/README-... > > [5] > http://fisheye.jboss.com/browse/JBossCache/core/trunk/src/test/java/org/j... > > [6] http://repository.jboss.org/maven2/org/jboss/cache > [7] http://snapshots.jboss.org/maven2/org/jboss/cache > > On 14 Aug 2007, at 17:36, Manik Surtani wrote: > >> Ok, this has finally happened, and the old CVS repo is frozen. >> >> I'm still in the process of reorganising the new SVN repo, and will >> send out an email once this is done, probably tomorrow morning (GMT + >> 1). >> >> Cheers, >> -- >> Manik Surtani >> >> Lead, JBoss Cache >> JBoss, a division of Red Hat >> >> >> >> _______________________________________________ >> jbosscache-dev mailing list >> jbosscache-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosscache-dev > > -- > Manik Surtani > > Lead, JBoss Cache > JBoss, a division of Red Hat > > > > _______________________________________________ > jbosscache-dev mailing list > jbosscache-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosscache-dev _______________________________________________ jbosscache-dev mailing list jbosscache-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosscache-dev