What YOU say about HgEclipse
The #Mercurial Eclipse plugin (HgEclipse) is miles ahead of the #Git plugin in both features and stability.
Neil Hartner on Twitter
#HgEclipse makes me seriously considering about switching from #git to #mercurial. The plugin is just so much better.
@woeye on Twitter
Well, all I can say is Wow! MercurialEclipse was ok, but Intland has taken it to very useable.
Mike Wilkes in his blog
...and installed the excellent HgEclipse plugin using the Eclipse "Install New Software" option.
Immo Hüneke in his blog
eclipseをtexエディターとしてしか使ってないという変な状態。Texlipse＋HGEclipse万歳
@alpha_emitter on Twitter
Loving the new HgEclipse plugin! http://javaforge.com/project/HGE -- finally a usable Team Synchronisation view, ssh push works.. #happy
@asynchronaut on Twitter
HgEclipse (http://bit.ly/8ZwUUG) лучше Mercurial Eclipse (http://bit.ly/91wtg3). Я хотя бы могу на русском писать #Eclipse #Mercurial
@mi_estas on Twitter
HgEclipse seems to be a nice successor of the MercurialEclipse plugin: http://javaforge.com/project/HGE #hg
@goeldner on Twitter
Replaced Mercurial Eclipse 1.4.2 with HgEclipse 1.5.0 RC1. And it works great. New syncronization View is fantastic. Hope they merge soon.
@slavus on Twitter
Testing HgEclipse - Mercurial plugin for Eclipse. Though Cloning wizard fails on OS X, it seems to work nicely otherwise.
@huima on Twitter
Posted at 12:47PM Feb 03, 2010 by Intland Team in Customer Stories | 0 Comments
Going Agile with Git and codeBeamer (Tutorial)
Clearvision, our terrific partner in the UK and a real expert in all things change management, generously released their Git Workshop training materials. This package was originally composed for a large telco, which is in the midst of reengineering its processes for the Android mobile computing platform. Now, the tutorial is available for the public. A sincere "thank you" goes to Gerry, Martin, and all the Clearvision team.
What is it?
This is a step-by-step tutorial that explains how to launch projects with the Git Distributed Version Control System and codeBeamer, Intland's collaboration software, and then leads you through the most common SCM tasks: cloning repositories, making and committing changes, and pushing changes. If you look beyond the obvious SCM operations, it shortly introduces you also to:- Agile planning
- Daily agile reviews
- Sharing information and collaborating in wikis
- Releasing project artifacts automatically, by using commit triggers and Ant scripts
Recommended for: developers, tech and team leads, project managers
Duration: 60 minutes (strictly speaking)
Resources
- codeBeamer & Git Workshop by Clearvision
- Clearvision company site
- Git project home
- codeBeamer product page (alternatively, see codeBeamer Managed Repositories if you look for a free tool)
Posted at 05:18PM Feb 01, 2010 by Intland Team in Tutorials | 0 Comments
HgEclipse 1.5.0 Final Released
As you might already know, the Release Candidate of HgEclipse 1.5.0 has been out since last November. Now we are happy to announce that the 1.5.0 stable release is available! If you were waiting for the stable release, don't hesistate any longer. For those who are not familiar with the project: HgEclipse is a Mercurial Distributed Version Control plugin for the Eclipse IDE, which is geared towards enterprise use.
1.5.0 is the first stable release delivered by Intland. Our ultimate goal is to evolve this plugin accompanied by our free and commercial products to a truly Enterprise-scale Distributed Version Control Solution.
You can download the plugin from JavaForge.
Changes since 1.5.0RC1
A couple of days ago, we posted the sneak preview of the change list to the Facebook page of HgEclipse. We will follow this practice in the future as well, so become a fan on Facebook if you want to keep up with the project, always know all the latest and interact with fellow users.- History View improvements:
- New features like "Compare with previous"
- Icon decorations instead of cryptical action letters
- Full set of "Open" and "Compare" context menus for the change set files
- Highlighting the base file in the changed files set
- Consistency fix: default action for double click is now "compare with the previous"
- Tags can be shown for single files
- Sigcheck analysis is optional now
- Graph view bug fixes and performance enhancements
- Merge View improvements:
- Conflict dialog changed from modal dialog to use 3-way merge editor
- New context menus: "Open merge editor", "Open default editor", "Mark resolve/unresolve" and "Show history"
- Ugly text actions from the toolbar removed
- "Compare" action now compares with the predecessor of the current version, if the file is not changed
- Enabled reverting a file (even if file is not changed) to a specific revision from the Revert dialog
- Added content assistance for the "Switch to" revision text field
- New feature to "Close" named branches
- Annotations are following file rename/move history
- Various other bug fixes
Future
The next release is scheduled by 2010 April. Currently we are planning and prioritizing worklog items for the next sprint, so we are keen to receive user feedback and would welcome your contribution. Tweet us what feature you would like to see in 1.6.0, and tell us what you think in general on LinkedIn.Hey! Still here? Now the interesting part: within a couple of weeks, we will roll out a new version of the codeBeamer Mylyn connector. This will be a great addition to your free tool set consisting of Mercurial, Eclipse, HgEclipse, Mylyn and codeBeamer Managed Repositories. Imagine this:
- you clone a repository from Mercurial easily maintained by codeBeamer MR,
- pull in issues from codeBeamer to Mylyn tasks,
- work on resolving the issues,
- commit your change sets to Mercurial,
- then push what you have done back to Mercurial, and close issue.
Finally
- Download HgEclipse via Eclipse Update in a minute.
- Watch the 4 minute tutorial video on YouTube.
- Join the project on JavaForge, get the source code and help us.
- Tweet us what you think about or what you are doing with the plugin. We would love to hear from you.
- Visit the HgEclipse Facebook page.
- Meet fellow users in the Linkedin group.
Posted at 11:29AM Jan 27, 2010 by Intland Team in Announcements | 8 Comments
Intland hits the road again: upcoming events in 2010
At Intland, we have a long tradition of meeting our customers, users of our free software, and anyone interested in what we do, personally at popular conferences, exhibitions and trade shows worldwide. This year, Intland hits the road again. Here are the first two major events we will be represented at, in the first half of the year.
embedded world 2010
Nürnberg, Germany
March 2-4, 2010
http://www.embedded-world.de
The embedded world Exhibition & Conference remains the world's undisputed biggest get-together for the international embedded community, as the figures show. The exhibition set another new record in 2009 with more than 700 exhibitors, and some 16,000 trade visitors used the opportunity to obtain an impression of the latest trends in embedded technologies.
embedded world 2010 will again prove its power of innovation for hardware, software, tools and services.
ITIL Forum 2010
Frankfurt/Germany
May 4-5, 2010
http://www.itil-kongress-iir.de
Anwenderakzeptanz für ITIL steigt!
Immer mehr ITIL-Anwender bestätigen, dass ITIL V3 die Verzahnung zwischen IT-Services und den unternehmensübergreifenden Businessprozessen entscheidend verbessert.
Auch mehr und mehr IT-Verantwortliche sind überzeugt, dass die IT-Prozesse grundsätzlich stärker auf die Geschäftsanforderungen ausgerichtet werden müssen. Vom Risikomanagement in ITIL V3 bis zu Service Validation and Testing – auf dem Weg zu Service Operation sind einige Herausforderungen zu meistern.
Unser ITIL Forum bietet Ihnen die Möglichkeit, Lösungen und Strategien erfolgreicher Unternehmen ausführlich kennen zu lernen. Hören Sie in den Expertenberichten, wie Sie sich an globalen IT-Standards ausrichten, Prozesse implementieren und diese kontinuierlich verbessern.
Die Früchte der Bemühungen sind Kosteneinsparungen in Betrieb und Entwicklung, zielstrebige Prozess-Rollouts und kontinuierliche Prozessverbesserungen in der IT-Service-Organisation.
All right, let's hook up at these events! Meet our people, ask questions or let's just chat about our products, JavaForge, our solutions, our industry, and whatever interests you. We will do our best to answer everything. Good bye until then.
In case you can't be there, you can ping us any time tweeting your questions to @intland at Twitter.
Posted at 01:46PM Jan 22, 2010 by Intland Team in News | 0 Comments
Google Code and Mercurial Tutorial for Eclipse Users
This post is a short introduction to using the Eclipse IDE and the HgEclipse plugin for projects hosted at Google Code Mercurial repositories.
HgEclipse is a free and open source Eclipse plugin that supports the Mercurial Distributed Version Control System right within the IDE, thus making these two a very convenient and efficient toolset for Java and C/C++ development. It is important to note that HgEclipse is absolutely not limited to Google Code's Mercurial repositories, it works with any Mercurial repository. We use Google Code merely because of its immediate availability and easy use.
What is Google Code? It is a popular hosting service for open source projects. It provides revision control, a rudimentary wiki, a basic issue tracker and file downloads. As for revision control, since April 2009 Google Code offers the Mercurial Distributed Version Control System as an option besides Subversion. (Git is still unsupported by Google Code. If you are a Git user, codeBeamer Managed Repositories is a compelling option for you!)
We recommend watching the guided video first, then reading the explanatory notes below. First, here is the video tutorial. Watch it in full-screen HD:
1 - Installing HgEclipse
You can easily install the plugin with the Eclipse Update Manager. Read here how.2 - Cloning a repository from Google Code
You start by making a local copy (or clone according to the right DVCS terminology) of the repository hosted at the Google servers, and import that to Eclipse as a new project.Luckily, HgEclipse offers a dedicated wizard for cloning and it makes the whole process very easy. The only thing you will need is the repository URL that is visible at the Command-line access section, under the Source tab in Google Code. You don't even need to authenticate with user name and password, since the Google Code repositories can be cloned anonymously.
3 - Working locally and committing your changes
You can add, delete and modify files just as you do it without Mercurial. The small grey stars over the regular file icons always indicate the files which have uncommitted changes.When you decide you want to commit some changes, the most convenient way to do that is switching to the Syncronization View. This view shows three types of changes:
- Uncomitted: your local changes that are waiting to be committed to your local repo.
- Outgoing: changes committed to the local repo, but not pushed to Google Code yet.
- Incoming: changes that were pushed to Google Code by other developers, but are not pulled into your local repo yet.
Don't forget that, unlike in centralized version control systems, at this point these changes are still only in your local repo, and not in Google Code! The distributed approach also has the advantage that you can commit even offline. You need to be online only when pushing to Google Code.
4 - Pushing your changes to Google Code
If you have changes that are worth to be contributed to the Google Code repo, then it's time to push them. This requires you to login to Google Code. Important: to identify yourself, you have to use your Google Code specific password, not your regular Google user account. You can see this password clicking your user name in the web interface, then switching to the Settings tab.Final words
If you are curious about the more advanced features like branching and tags, just tweet a message to @intland on Twitter, and we will be happy to write more.Posted at 04:34PM Jan 12, 2010 by Intland Team in Tutorials | 2 Comments
Enterprise mashups with codeBeamer
This post is written by a guest writer, G. Hussain Chinoy of Bespoke Systems.
Hussain is writing about his experience building an awesome timeline mash-up. His app pulls out events from Google Calendars and issues from codeBeamer's super-elastic trackers, and visualizes them along a SIMILE timeline. What makes it even more interesting from technical perspective is the mix of technologies involved: .NET in the serverside, heavy javascript magic in the clientside, Google Calendar running in the cloud, and codeBeamer running in a Java servlet container and exposing its .NET remote API. The right tool for the right job.
We are incredibly appreciative of the efforts you put into projects like this. We will be doing whatever we can to support them, and would love to see more. Do you have questions? Comments? Something to show for the codeBeamer community? Just tweet us at @intland, and we will get back to you immediately.
CodeBeamer Timeline Builder
(Please click the images for their high resolution versions.)Background
Project dashboarding - viewing the progress of a software development project from different viewpoints - has been an interest of mine ever since I started developing software. After one particularly difficult project involving issues with requirements, development and operations deployment and environmental difficulties, with no shortage of fingerpointing going on, I thought it would be good to step back and see the project from a linear timeline perspective and gain some objectivity. Additionally and especially for long running projects, viewing time linearly helps us as humans see the scope of events.
Simile Timeline + Google Calendar
I'd already had a calendar that was a great repository of significant events, which meetings I'd scheduled, etc. in Google Calendar. The data originally came from the corporate Outlook, synced up to Google Calendar with the Google Calendar Sync application. Using the Simile Timeline Javascript widget, I wrote a quick export from Google Calendar using the Google Calendar Data API to format the calendar events into the Simile Timeline json format. Since the events were hand coded Client Requirements (grey), Impediment (red) and Success (green), viewing the events linearly helped clear up the discussion around where the issues were in deploying the application. This quick web application was very well received and project managers in both development and operations, as well as other non-project related developers and managers, since they were able to see the timeline of events that occurred for this particular project. I hadn't fully automated the import from Google Calendar to the Project Timeline page, and that's what led to the next step.Dynamic Timeline Generation
The timeline view of the project was very useful and I thought it'd be a great perspective for other projects. Most of the projects at the organization use codeBeamer by Intland as an issue tracker and document repository. CodeBeamer has a much richer ability to code tasks / tracker items with statuses as well as start dates, end dates, and changed dates. Being able to dynamically pull project info via tracker lists and view them in a linear timeline looked to be a great start for a project dashboard.
The Timeline Builder was constructed with two picklists, one that displayed the lists of projects available and the second picklist that was contextual to the project's actual tracker lists. The codeBeamer repository is organized such that every project has multiple "tracker lists" such as Business Requirements, Change Requests, Production Releases, and Defects. Project administrators can also add tracker lists as needed. When a project is selected from the first picklist, an AJAX call is made to the codeBeamer services, returning the project-specific tracker lists. When a user selects a tracker list, the application issues an AJAX query and retrieves the list of tracker events and then displays them as a timeline. The timeline has three horizontally scrollable bands: a weekly view, a monthly view and a yearly view. Each of them can be dragged left or right and the display of events will be synchronized. The display is "coded" by status: tems with a status of "closed" are represented as a solid blue ribbon, individual events have a circle icon, "in progress" events are a slightly transparent blue ribbon, "open" items are represented by a slightly transparent red ribbon with a solid red circle icon. Selecting a timeline event yields a link to the original codeBeamer tracker item as well as a short description along with the open and closed/last updated information. Below the timeline is a tabular representation of all the event data.
Technology Decisions
The organization uses .NET predominantly so I decided on using WCF and the codeBeamer .NET SDK to serve up the Simile Timeline JSON and ASP.NET (without WebForms) and jQuery to make AJAX requests to the WCF codeBeamer services. Additionally, the organization is standardized on Windows 2003 and IIS6, so I passed on using ASP.NET MVC on IIS6. Each codeBeamer project can have multiple task trackers ("tracker lists"), so there were three total JSON services: GetAllProjects, GetTrackerListsForProject, and the last, GetTimelineForTrackerList, which retrieved all tracker items for a particular tracker list as Simile JSON events. Additionally, I used two jQuery plugins - jTemplates to populate portions of the page, and flexigrid to show the same events in a table below the timeline.Findings and Stumblings
Looking at the variety of projects that we have in a linear format brought some interesting insights, the first of which is that almost no two projects use Tracker lists the same way. Not every project uses codeBeamer the same way, even though we have default tracker lists for Business Requirements, Change Requests, Production Releases, and Defects. Not every Task Lead uses the default statuses the same way - some close all tracker items only when a project has deployed, and create a separate status - "development complete" - for developers to use. Tracker items stay open throughout the iteration. For long-running, multi-year projects, cyclicality was shown quite well in a linear timeline - periods of project activity were clearly mapped to variety of business cycles.With the differences in usage of codeBeamer trackers, the high level of ability to customize tracker item templates, and the variability in conforming to the SDLC in the organization, comparing project-to-project is difficult in general, not just with a linear timeline.
The decision to use .NET WCF and a jQuery-driven front-end separated the codeBeamer Tracker List JSON generation service from the UI application, creating two projects which may or may not have been a good idea - although service-oriented, it's two distinct codebases to maintain. Another interesting challenge was the codeBeamer API documentation for .NET - there isn't really any, for either Hessian C# or the codeBeamer Remote API. Using Reflector and referring to the codeBeamer Java SDK Javadocs did help, but a Sandcastle generated documentation set would've been useful. Thankfully, the Java and .NET API's are extremely similar, so it wasn't a problem interpreting what should've happened.
Project Next Steps / Directions
For the current iteration of this timeline builder I have a few minor technical issues I'd like to address. I'm planning on having better integration between the flexigrid table of events and the simile timeline so that when you select an item from the table, it scrolls the timeline to the relevant event. Another enhancement would be to allow stacking timelines of multiple projects for juxtaposition.
I'd also like to expand the data feed to other task tracker applications. The organization also uses VersionOne's on-line agile project tracking application which has similar data to codeBeamer. A future revision to this application may include pulling from VersionOne project data dynamically in a similar manner (choose a project, see a timeline). Similar "coding" issues occur with VersionOne as with codeBeamer use, but since VersionOne is more focused on an agile project management lifecycle, I expect representing the variety of task types to be somewhat easier. An initial version is pictured below (using jstree to visualize the project hierarchy, at the left). Coding (designating the display of open, closed, in progress, etc.) is a bigger issue, and relates more to the choice of software project management structure - agile, etc. - but is something that's greatly needed to get a consistent level of display. Other project tracking software, which I'm familiar with from a user standpoint, that may be usable include Redmine and Assembla/Trac.
From the technical framework, I may experiment with ASP.NET MVC next (which would remove the need for a separate WCF project) and then GWT (with the codeBeamer Java SDK) to see which one is more code-efficient.
Thanks for reading this writeup!
G. Hussain Chinoy
hussain.chinoy @ bespokesystems
Posted at 02:41PM Jan 07, 2010 by Intland Team in Customer Stories | 0 Comments
Looking back at Intland in 2009
2009 has been a busy year for Intland. Lots enhancements in our products, lots of awesome customers wordwide, lots of valueable feedback from the community, and lots of exciting changes in the collaboration space.
Let's see the most important events along our 2009 timeline:
Moving JavaForge to Amazon Elastic Compute Cloud
In the beginning of the year (pretty much during the Christmas holiday actually, so that we interfere the least with always-busy open source enthusiasts), we moved JavaForge.com, our free project hosting service, from a traditional hosting environment to the Amazon EC2 cloud infrastructure. Our motivation was a mix of enhancing availability, lowering operational costs, experimenting with the cloud, and most importantly providing higher quality service for our users.Experiences: so far so good, the story is not over yet. During the whole year, competition in the cloud computing space was fierce, and we expect major changes in 2010 as well (within months). At the moment we keep our eye primarily on Amazon EC2, Google App Engine and SpringSource Cloud Foundry.
Release of codeBeamer 5.3
This release satisfied some long time feature requests, like aggregation and distribution of issue properties, and introducing wiki pages as tracker dashboards. It also incorporated major performance improvements and an early access version of the Mercurial support.Even if the Mercurial support in codeBeamer 5.3 was considered early access, this was a major cornerstone of future codeBeamer versions (see the next item to figure out why).
Making Distributed Version Control a core strategy
High emphasis on Distributed Version Control was one of the most important decisions we made during the year, if not the most important one. We are big believers in the superiority of the distributed collaboration approach, thus:- codeBeamer, our Collaborative Application Lifecycle Management solution, now supports Git and Mercurial repositories in addition to Subversion, CVS and such.
- We launched a brand new free tool, codeBeamer Managed Repositories, that makes creating and managing Subversion, Git and Mercurial reporistories quick and easy.
- We released a Mercurial plugin for Eclipse, HgEclipse, that makes it possible to collaborate on really large projects in the Eclipse IDE.
Twitter and Facebook
We successfully launched our Twitter stream and our Facebook page. We have been fairly active on Twitter engaging with our users, spreading useful links and exciting short news, following the trends, but we were not really spending much time on Facebook. (This is something we will change in 2010.)For now, just follow @intland on Twitter and become a fan of codeBeamer at Facebook if you don't want to miss anything that matters.
Release of codeBeamer 5.4
Big new features were: editing wiki pages in Microsoft Word directly (neat!), improved support for Git and Mercurial, calculated issue properties, issue escalation, just to name a few.Looking at the download counts, 5.4 is the most popular codeBeamer version ever. Go and get a free download or free live trial.
Release of codeBeamer Managed Repositories 1.0
Later in the year we launched codeBeamer Managed Repositories (or MR in short). Learning from our own experiences, we wanted to save time and headache for Subversion, Git and Mercurial users, and to make repository management quick, easy and convenient.Despite of the festive season, more than 1000 users installed codeBeamer MR in December only. Don't miss your late Christmas present
, codeBeamer Managed Repositories is still available for free download.
Release of HgEclipse 1.5.0-RC1
Converting from Subversion to Mercurial was the biggest change in our interal development tool set and processes. (We blogged about it here, here and here.) After the initial frustration we are happy we made the change. This project was a sort of spin-off of the migration process, which we developed for our own needs and then made it publicly available.You can install HgEclipse in 5 seconds, and feel free to join the project any time.
And how about 2010?
Please wait a little for our next blog post, coming soon.Finally
Thank you so much for your support and in-sights in 2009, you are an AWESOME community!Posted at 02:47PM Jan 06, 2010 by Intland Team in News | 0 Comments
"Well, all I can say is 'Wow!'. MercurialEclipse was ok, but in one release, Intland has taken it to very useable."
Have you heard of HgEclipse, the Mercurial plugin for Eclipse that actually works?
We have released it for the public last December (see this post). Since then more than a 1000 Mercurial users installed it, and now we are receiving positive feedback all over the blogosphere and Twitter.
Mike Wilkes of Intelliware.ca writes (see his original blog post for the full review):
Well, all I can say is 'Wow!'. MercurialEclipse was ok, but in one release, Intland has taken it to very useable. They're calling their version HGEclipse to differentiate from MercurialEclipse.
2 big highlights. They synchronize view is now very useful, as it shows uncommitted changes, incoming and outgoing changesets.
They've also fixed the history/compare view. Mercurial tracks file copies, but MercurialEclipse would create an error if you tried to compare a file version with the current name to one with the old name.
HGEclipse resolves it correctly, and shows the differences.
Do you have a question, comment, suggestion or tip? Leave your feedback in the project issue trackers.
Posted at 03:30PM Jan 05, 2010 by Intland Team in Customer Stories | 2 Comments
Happy New Year
From all of us at Intland (including Adam, Andrei, Aron, Dagmar, Georg, Janos, Klaus, Laci, Laura, Roland, Zoli, Zsolt and the guys behind the scenes), we wish You a Very Happy New Year 2010! Lots of good health, successes and happiness, and efficient collaboration.
Thanks again for your support and your trust in us. 2010 is surely going to be a huge year, great things to come. More on our plans later.
Posted at 10:18AM Jan 04, 2010 by Intland Team in Business | 0 Comments
Intland now on Mercurial - Part 3: Giving new momentum to the Eclipse Mercurial Plugin
This blog post is a sequel to Intland now on Mercurial and Transforming our tool set.
As written in the most recent post of this series, we found that quite some features important for us were missing from the latest version of the Eclipse Mercurial Plugin. We really wanted to move from Subversion to Mercurial, but we decided that at that point we could't do it without major productivity losses. We also realized that we couldn't wait for all improvements to be developed and tested by the community. Hence, several weeks ago, Intland Software decided to dedicate a developer to the Mercurial Eclipse plugin project. To put it simply, his task is to complete the most important missing features, and to make sure that the plugin would not be a blocker for our team anymore.
We made one major change though. Because this project will be absolutely mission critical for us even in near term, we wanted to be able to progress at our own pace and have 100% control over our internal release schedule. That's why we cloned the original repository into a new project with a codeBeamer-managed Mercurial repository, which is hosted at JavaForge. Our clone is fully open, and we call it HgEclipse to distinguish it from the original MercurialEclipse project initiated by Zingo Andersen.
We encourage the Mercurial community to pull our changes back to the original repository, and we invite everyone to clone our repository freely. Every kind of contribution including programming, testing, writing documentation is more than welcome! If you just want our binaries, those are already available at the Eclipse Update Site at JavaForge. With this project, we follow a release early approach, so new updates might pop up frequently!
We consider the current plugin version a Release Candidate (final will be rolled out in January 2010), however we have been using this in production without major problems for several weeks. We will be continuously working on this. Most importantly, our ultimate long term goal is to provide a viable option for enterprise scale collaboration, based on the Mercurial distributed version control system, the Eclipse Platform and codeBeamer, our distributed ALM platform.
Our work on the 1.5.0 line incorporates about 300 change sets. Highlights:
- Synchronization View: - lack of a rock solid sync view has been an absolute blocker for us. In 1.5.0 it has been practically rewritten from scratch. Now it works with bi-directional synching, multiple branches, immediate push/pull operations, diff's, real change sets (not just change files) and all that jazz.
- Working with multiple branches: - previous plugin versions were pretty much limited to working on the default branch alone. Not anymore. Our team paralelly works on several branches of our core product, so we are confident to say it.
- Cloning: - detecting Eclipse projects is more stable, and the UI is more responsive.
- Self-contained packaging: - in Windows, the plugin has no additional dependencies. It is bundled with hg itself and all other required packages. That means you just install the plugin through the Eclipse Update Manager, and it works out of the box. It's that simple.
- Major performance and resource usage improvements: - long-running tasks executed in the background, agressive caching, smaller memory footprint on large projects, to name a few. (Our current benchmark is to be able to run with a project with 10,000 files.)
- Tons and tons of bug fixes: - you can follow the progress in this bug tracker.
- See more details here.
And finally, some important links:
- HgEclipse project home page
- HgEclipse screen shots
- How to get the plugin via Eclipse Update?
- How to check out the sources?
Posted at 10:23AM Dec 14, 2009 by Intland Team in Announcements | 6 Comments
codeBeamer Managed Repositories Video
In case you missed it, this 2 minute video on codeBeamer Managed Repositories (also known as codeBeamer MR) gives you a quick introduction about the free tool. It shows how MR saves you lots of efforts with managing Subversion, Mercurial and Git repositories:
Posted at 10:40AM Dec 10, 2009 by Aron Gombas in Tutorials | 0 Comments
codeBeamer deployed on Oracle WebLogic Server 11g
Intland has just successfully completed a codeBeamer rollout project for a large German government authority. Our customer is now operating codeBeamer on the Oracle WebLogic 11g application server and Oracle Database, within a completely Oracle infrastructure.
What are the benefits of deploying codeBeamer on a high-end WebLogic application server?
- High availability: you can achieve near-continuous operation with extremely robust and automated fail-over.
- Streamlined management: you can configure and monitor codeBeamer instances from a unified management environment.
- Deep diagnostics: you can monitor codeBeamer in production without impacting its runtime behavior.
- Superior integration: you can consolidate your infrastructure if you use other products from the same vendor, for example when running codeBeamer with Oracle Database.
Posted at 02:33PM Dec 09, 2009 by Intland Team in Customer Stories | 0 Comments
codeBeamer plugins by Markus Eisele
Markus Eisele, a software architect from Bavaria, has set up a web page dedicated to his very own codeBeamer extensions, which might be interesting for all codeBeamer users. Currently, there are two plugins available for free download:
- Tag Label Cloud Plugin: wiki plugin to render tag clouds.
- Gallery Plugin: wiki plugin to show nice galleries from picture files saved in a folder in codeBeamer's Document Manager.
Fore more information, please visit Markus' page: http://www.eisele.net/de/work/codebeamer.html
Did I mention we love third party plugins? If you have something you would like to show to the community, please contact us via email at info at intland dot com.
Posted at 12:40PM Nov 30, 2009 by Aron Gombas in Customer Stories | 0 Comments
This is Official: Subversion Becomes an Apache Project
Dear Subversion,
However the official announcement has been published several weeks ago, we would like to wish you good luck in your new home now!
We believe, as soon as the incubation process gets completed, you will benefit from everything The Apache Software Foundation has built since its inception: know-how, people, infrastructure, events and who knows what else. By removing the burden of corporate overhead, you will be even more accessible for the teams looking for a proven revision control software. We continue to support you, and we are looking forward to see you improving in the forth coming years.
Good luck, again. We love you.
Links:
Posted at 01:34PM Nov 24, 2009 by Aron Gombas in News | 0 Comments
At Last! codeBeamer Managed Repository 1.0 Released
We've come a long way, baby. Four weeks ago, we promised two product releases within the next two weeks, and we have been working late night shift to do our best...
The first product mentioned, codeBeamer Managed Repository, has been silently released over the last week.
This is a fresh and tasty tool for anyone working with Subversion, Mercurial and Git or even with all the three at the same time! Creating and deleting repositories, and setting up access control ("who can read and write what") is usually a major maintenance issue that developers usually hate to solve, as it is boring and inherently error-prone. In other words, our value proposition is dead simple: MR will help you to spend your valueable time rather with coding, not hacking around in SSH and ACL config files.
Feature highlights in a nutshell:
- Starts and close projects and repositories in just seconds
- Project-, group-, and role-based administration across multiple repositories
- ACL on directory level
- SSH authentication
- Lightweight wiki, issue tracking and project management facilities
- Web based
- Remote API
Visit the codeBeamer Managed Repository home page for more information, screenshots and downloads.
Posted at 03:48PM Nov 18, 2009 by Intland Team in Business | 0 Comments