Our current stack: - maven - Java 6 - hibernate - spring - Wicket - svn - hudson - artifactory (though we might switch to another one) [ - sonar (icing on the cake) ]
Wendy Smoak taught me an valuable lesson: use a company repository manager for maven, and a local one on your machine. This way you can run maven offline as well (after downloading the internet first). Martijn On Wed, Apr 29, 2009 at 5:13 PM, Dane Laverty <danelave...@gmail.com> wrote: > My boss has asked me to manage development for a Java project. I'm going to > be working with two other programmers and one designer. > > This is the first time that our organization has tried to formally > coordinate several programmers on a project together, and it is also the > first Java project we've done here (I'm the only programmer with extensive > Java experience). I chose to use Wicket for this project because it seemed > to be the most intuitive framework, and because I hope it will make it easy > for the designer and programmers to work together without stepping on each > others toes. > > At my previous job, we used CVS for managing code contribution and Ant for > deployment. Is that still a good solution, or should I be looking at other > tools? Also, how do you coordinate the designer's work with the programmers' > work? > > My goal is to find a few tools that > - work well with Wicket > - make it easy for programmers to check code in and out > - manage project dependencies > - are easy to set up > - are easy to use > - are free > > I appreciate any and all suggestions. Thanks for your help! > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org