Login   I   Sitemap   I   Contact Us   I   Sales: (US) 1-866-468-5210   (EU) +49-711-67400677
Intland Software - Collaboration Begins Here
Download or Try the fully functional version of codeBeamer. It's free, simple and secure.
codeBeamer is the award winning Collaborative Application Lifecycle Management (ALM) solution for distributed software development.
Project management, wiki, document management, issue tracking, ITIL, continuous integration, version control, source code analysis and forums.

Links

Feeds

Editor Menu

codeBeamer Eclipse Studio: Collaborative workspaces can now go offline

In 2010 public network access is still far from ubiqutous, making the continuous work impossible for many knowledge workers. Managers, consultants, programmers waste so many valuable time sitting on the plane, working on-site disconnected from the outside world, or just not having access to any wifi hotspot. Intland Sofware now allows doing your work anywhere, even offline.

We are happy to annouce the 2.0 release of codeBeamer Eclipse Studio (CBES). codeBeamer Eclipse Studio takes all your information offline (including source code, version control of any file, and tasks), and enables you to continue your work remotely and securely. It also helps to synchronize with your "web-based data" at a later time.

How does it work? Let's compare the old and the new ways.

Increased productivity through mobility

The nineties way

  1. Check out a working copy from Subversion hosted on some corporate server, and create a project in Eclipse.
  2. Open your browser, navigate to your intranet based task management system, and activate your next set of tasks.
  3. Stay online, CHAINED to your cubicle.
  4. Work on the code. Commit to Subversion. Update your tasks in the task management system. (Make sure network connection is fine.)
  5. Goto 2.
You know this one very well, for sure.

The mobile knowledge-worker way

  1. Clone a repo from Mercurial with MercurialEclipse's Clone Wizard, and let it create the corresponding Eclipse project.
  2. Create a new task query with CBES's Query Builder, and import your tasks to Mylyn.
  3. Now you can go offline. Get on the plane, visit your customer, or go to your favourite coffee shop.
  4. Work on the code as you normally do. Commit your changes to Mercurial. Update your tasks in Mylyn. (You can do all this offline.)
  5. If still offline, goto 4.
  6. Online again? Push your outgoing changes to the central Mercurial repository conveniently, using MercurialEclipse's Synchronization View. In the background, your tasks will be automatically synchronized with the remote task repository.
The question is: which one are you?

Links

Comments:

Post a Comment:
Comments are closed for this entry.