There's a bug (with workaround) in eGit 1.1.0, which we include in JBT/JBDS requirements mirrors and TPs. It's apparently fixed in eGit 1.2.0, which I assume is slated for release in February as part of Indigo SR2. Issue details: https://issues.jboss.org/browse/JBIDE-10295 https://issues.jboss.org/browse/JBIDE-10307 https://bugs.eclipse.org/357951 When I'm creating a new TP with Indigo SR2 bits, I could also grab a newer eGit at the same time. Any reason not to do so? Please weigh in on the JIRA above. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com