<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Efficient Java tools- Code Versioning</title><link>http://www.javaperformancetool.com/Code_Versioning/</link><description>JavaPerformanceTool.com is a directory listing the Java tools, libraries and plug-ins for productive development of robust Java/J2EE products. </description><item><title>AccuRev</title> <link> http://www.accurev.com/</link><description>&lt;p&gt;&lt;strong&gt;Visualize and dynamically manage your software  development process: &lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Software development today is more complex than at  any time in the relatively brief history of computing. New technologies mature  faster, product delivery cycles are shorter, teams are working in parallel in  multiple locations, and customers are more demanding. Building quality software  at reasonable cost requires a balance between hiring and retaining talented  engineers, gathering meaningful product requirements from customers, choosing a  development toolset, and orchestrating the engineering activities via the  software development process.&amp;nbsp; These  tools include:&lt;/p&gt;
&lt;p&gt;&amp;bull;Software  Configuration Management (SCM), Issue Tracking (ITS), and Build Management  (including continuous integration and unit test)&lt;br /&gt;
&amp;bull;Agile  project management (where applicable) &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;strong&gt;The &amp;quot;right-sized&amp;quot; Application Lifecycle Management  (ALM) solution:&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;Software development organizations today  are wrestling with many critical decisions regarding selection of development  tools, and none may be as important as whether to select a single-vendor  application lifecycle management (ALM) solution, or to go with a best-of-breed  approach. These choices are often difficult because each group within the  organization may have different criteria on which they are basing their answer  to this question, and both have their advantages. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The analysts&amp;rsquo; choice for replacing ClearCase: &lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Getting by with ClearCase. Our  development process is generally stable and working today, but of course it  could be improved to meet your current development requirements if you only had  the time to write the necessary scripts. Developers basically know how to get  their job done with ClearCase and generally follow the documented software  development process, yet they wouldn't describe ClearCase as something they  truly like using, or even fully understand how to use. There may  be some level of integration between ClearCase and your issue/defect tracking  solution; however, it is not what you would consider to be an optimally  efficient workflow.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Quickly adopt continuous integration and other agile processes: &lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Continuous integration, one of the  foundational aspects of Agile software development methodologies, is defined by  Martin Fowler to be &amp;quot;a fully automated and reproducible build, including  testing, that runs many times a day.&amp;nbsp;  This allows each developer to integrate daily, thus reducing integration  problems.&amp;quot;&amp;nbsp; By extending the idea of  a nightly build, where code changes are built and tested nightly, continuous  integration helps reduce integration problems and identify and resolve problems  more quickly. With continuous integration, developers are encouraged to update  the shared source code repository frequently, ideally several times per day.&lt;/p&gt;</description><pubDate>Sun, 08 Nov 2009 20:38:58 GMT</pubDate></item><item><title>SourceAnywhere</title> <link> http://www.dynamsoft.com/Products/SAW_Overview.aspx</link><description>&lt;p&gt;&lt;strong&gt;&amp;bull;Enhanced Security&lt;/strong&gt;&lt;br /&gt;
It uses SSL and Blowfish encryption to  protect code while in transit and the client/server architecture eliminates the  need to expose the file system to remote users. The security of the password is  the frontline of any system. The built-in password policy of SourceAnywhere for  VSS can be enforced to protect your SourceSafe password.&lt;br /&gt;
&lt;strong&gt;&amp;bull;Up to 100 Times Faster than Visual  SourceSafe (VSS) remotely &lt;/strong&gt;&lt;br /&gt;
VSS web access is too slow. SourceAnywhere  for VSS features &amp;quot;delta transfers&amp;quot; to transmit only the incremental  changes between files, fast transfer compression, plus a Cache Server to reduce  file transfer over the internet.&lt;br /&gt;
&amp;bull;Visual Studio, Eclipse, Dreamweaver and  other MSSCCI Compatible IDE integration&lt;br /&gt;
SourceAnywhere for VSS can be fully  integrated with Microsoft Visual Studio 6/2003/2005/2008. It also supports  Eclipse integration on Windows and other operating systems. Integration with  Dreamweaver, Flash, Flex and other MSSCCI compatible IDEs are supported.&lt;br /&gt;
&lt;strong&gt;&amp;bull;Cross-platform&lt;/strong&gt;&lt;br /&gt;
Besides native Windows client, the Java  client extends Visual SourceSafe (VSS) to other platforms, such as Linux, Max,  Solaris and AIX.&amp;nbsp; &lt;strong&gt;&lt;/strong&gt;&lt;br /&gt;
&lt;strong&gt;&amp;bull;Build Automation&lt;/strong&gt;&lt;br /&gt;
SourceAnywhere for VSS integrates with  CruiseControl.NET and ANT to provide continuous integration and automatic build  support.&lt;br /&gt;
&lt;strong&gt;&amp;bull;Less Database Corruption&lt;/strong&gt;&lt;br /&gt;
During lengthy remote operations, one  network glitch can leave your SourceSafe database corrupted. SourceAnywhere for  VSS significantly reduces the database corruption by transferring the files to  the server first then operating on your Visual SourceSafe (VSS) database in  LAN.&lt;/p&gt;
&lt;p&gt;Features are:&lt;/p&gt;
&lt;p&gt;&amp;bull;High  performance SourceSafe remote/internet access &lt;br /&gt;
&amp;bull;Windows GUI  client and command line client&lt;br /&gt;
&amp;bull;Cache Server  for your geographically distributed teams&lt;br /&gt;
&amp;bull;128-bit SSL and  Blowfish encryption &lt;br /&gt;
&amp;bull;Java SDK and  COM SDK&lt;br /&gt;
&amp;bull;Password policy  to protect your password &lt;br /&gt;
&amp;bull;Eclipse plug-in &lt;br /&gt;
&amp;bull;Java client for  cross platform&lt;br /&gt;
&amp;bull;Macromedia  Dreamweaver and Flash plug-in&lt;br /&gt;
&amp;bull;Ant and  CruiseControl.NET plug-in &lt;br /&gt;
&amp;bull;Delta transfer  technology for high performance &lt;br /&gt;
&amp;bull;Visual Studio  plug-in &lt;/p&gt;
&lt;p&gt;SourceAnywhere for VSS is a client/server  application. It consists of a Server, Cache Server (optional) and several types  of Client. They communicate over any standard TCP/IP connection, including a  PPP connection over a modem, an ISDN line, or an Ethernet connection on the  same LAN as the Server. SourceAnywhere for VSS does not require Windows Remote  Access Service (RAS). The client-server architecture eliminates many problems  of Visual SourceSafe, which is file-system based, in remote access. For Visual  SourceSafe (VSS), to share Visual SourceSafe (VSS) documents, you have to share  the whole Visual SourceSafe (VSS) database folder, even if you only wish to  share a single file in the database. Sharing the database folders totally  exposes your valuable data to the outside, which may potentially cause the data  to be copied or damaged. Especially in remote access, it is almost  unconceivable. Also, accessing the file system in a remote environment is very  slow. In Dynamsoft SourceAnywhere for VSS, the Visual SourceSafe (VSS) database  folder is only exposed to the SourceAnywhere for VSS Server. The client sends  requests to the server and gets the result back. The security and performance  are greatly improved. Dynamsoft SourceAnywhere for VSS 5 introduces Cache  Server for distributed developments.&lt;/p&gt;</description><pubDate>Sun, 08 Nov 2009 20:36:21 GMT</pubDate></item></channel></rss>