[ https://issues.jboss.org/browse/JBIDE-10896?page=com.atlassian.jira.plugi... ] Stefan Bunciak updated JBIDE-10896: ----------------------------------- Attachment: nsme.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10896?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10896: ------------------------------------------ I can reproduce this in the binary build only, it does not happen if I run it from TRUNK. I compared the egit versions, and both match (egit 1.1.0 in both cases). So for the moment I also checked if the constructor, that the binary build is missing, is present: it is (CommitOperation(Collection, Collection, Collection, String, String, String). So I currently dont understand what's happending here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10896?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10896 at 2/15/12 1:02 PM: ------------------------------------------------------------------- I can reproduce this in the binary build only, it does not happen if I run it from TRUNK. I compared the egit versions, and both match (egit 1.1.0 in both cases). I also checked if the constructor, that the binary build is missing, is present: it is (CommitOperation(Collection, Collection, Collection, String, String, String). So I currently dont understand what's happending here. was (Author: adietish): I can reproduce this in the binary build only, it does not happen if I run it from TRUNK. I compared the egit versions, and both match (egit 1.1.0 in both cases). So for the moment I also checked if the constructor, that the binary build is missing, is present: it is (CommitOperation(Collection, Collection, Collection, String, String, String). So I currently dont understand what's happending here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10896?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10896: ------------------------------------------ we decided to wait for a fresh build and hope it'll be solved. It looks like this is some weird build issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10896?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-10896. -------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10896?page=com.atlassian.jira.plugi... ] Stefan Bunciak closed JBIDE-10896. ---------------------------------- Clean install went smooth, cannot reproduce. Verified on JBoss Tools 3.3.0.Beta1b -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira