I suggest looking at Perforce. It is the best SCM I've used (cvs, svn, vss, clearcase, pvcs, starteam, and a couple other no-names I can't remember).
-----Original Message----- From: eyal edri [mailto:eyal.e...@gmail.com] Sent: Tuesday, December 29, 2009 12:11 PM To: Maven Users List Subject: Re: Maven + JUnit, what's the best approach? I ran away from starteam into accurev.... :( is there any other good managed (commerical) SCM out there that works with linux? Eyal. On Tue, Dec 29, 2009 at 6:31 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > 2009/12/29 eyal edri <eyal.e...@gmail.com> > > > thanks, > > > > actually i've already setup a few things: > > > > - artifactory > > - hudson > > - scm (tesing accurev) > > > > IMHO, accurev is a pile of ____ esp if you want to use Maven. There are > some architectural decisions that they made which make use with Maven a > pain. > > Subversion is great with Maven, and it's free too.... > > Also having migrated our 11 years worth of source control from Accurev to > Subversion (including writing a tool [which my employers will not let me > publish] to extract the full history into Subversion) I would not > personally > touch Accurev with a 1000 foot barge pole. > > I know others feel differently, and these are my personal opinions, but > anywho, just thought you'd appreciate the feedback > > -Stephen > > P.S. > 1. You cannot export a tree into a subfolder of a workspace (makes using > the maven release plugin a nightmare) > 2. You cannot have a workspace as a subfolder of another workspace (makes > aggregator style projects a pain... You can solve this by using > include/exclude rules and some partial view stuff... but that only works if > you only use one depot...) > 3. Snapshot/workspace names must be unique at any point in time... and you > cannot delete snapshots... makes tagging a pain... try re-rolling a release > with maven-release-plugin > 4. AFAIK, Maven release plugin does not work yet with Accurev (as the SCM > support for maven was not where it needed to be before we ditched Accurev) > I > had written an SCM implementation [which I cannot share] but it was > impossible to get it to work with the release-plugin's workflow > > > - maven2 > > - issue tracking is currently bugzilla, but might be jira > > > > i'm looking at the default test classes maven creates, are they obsolete? > > i saw that maven added junit 3.8.1 instead of 4.x as a dependency and > > auto generated this code: > > > > *import junit.framework.Test; > > import junit.framework.TestCase; > > import junit.framework.TestSuite; > > > > /** > > * Unit test for simple App. > > */ > > public class DbUtilTest > > extends TestCase > > { > > /** > > * Create the test case > > * > > * @param testName name of the test case > > */ > > public DbUtilTest( String testName ) > > { > > super( testName ); > > } > > > > /** > > * @return the suite of tests being tested > > */ > > public static Test suite() > > { > > return new TestSuite( DbUtilTest.class ); > > } > > > > /** > > * Rigorous Test :-) > > */ > > public void testApp() > > { > > assertTrue( true ); > > } > > > > }* > > > > > > should i change the junit in the pom to 4.7? > > in some junit examples they use annotations (@Test), which doesn't work > > with > > that code.. > > > > i'm a bit confused... > > > > > > > > On Tue, Dec 29, 2009 at 3:58 PM, Ognjen Blagojevic <ogn...@etf.bg.ac.rs > > >wrote: > > > > > eyal edri wrote: > > > > > >> I'm new to Java and maven and currently in the process of building the > > >> entire infrastructure for java development in the company. > > >> > > >> i'm not quite familiar with JUnit, but i know maven makes it easy for > > you > > >> by > > >> creating default test tree and test classes in each project. > > >> > > >> where can i read about best practices regarding writing unit tests for > > my > > >> java apps using JUnit with MAVEN? > > >> > > >> thanks. > > >> > > > > > > Start with: > > > > > > http://maven.apache.org/guides/getting-started/index.html > > > http://code.google.com/p/t2framework/wiki/JUnitQuickTutorial > > > > > > I you are building an infrastructure, aside from JUnit and Maven > > knowledge, > > > you will (probably) need to install, in order of importance: > > > > > > 1. Version control system such as Subversion > > > 2. Maven ropository, such as Apache Archiva, Artifactory or Nexus > > > 3. Mailing list manager, such as Mailman > > > 4. Issue tracking system, such as Trac > > > 5. Continuos integration system, such as Apache Continuum > > > > > > Regards, > > > Ognjen > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > > > -- > > Eyal Edri > > > -- Eyal Edri --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
