Did you actually “git push” the changes? GIT requires things to be done two or three times to really take… but it calls each of those times a different thing. In this case, to commit something you have to commit it and then push it because commit isn’t really committing it in the SVN sense.
Please note that we are talking about 2 different projects:
The actual sources are on github and are committed regularily
The Netbeans plugin is just the built .jar of the above, and is what I want to commit on google code (not github). I’ve followed the instructions on the tutorial page, but it worked only for the first commit and when I changed some information. It’s as the library itself weren’t part of the plugin.
Please note that we are talking about 2 different projects:
The actual sources are on github and are committed regularily
The Netbeans plugin is just the built .jar of the above, and is what I want to commit on google code (not github). I’ve followed the instructions on the tutorial page, but it worked only for the first commit and when I changed some information. It’s as the library itself weren’t part of the plugin.
So, your only evidence that it didn’t commit is that the end of a long process (that probably isn’t even running) doesn’t produce the output it’s supposed to? Did you even just go to google code and check to see if the file you committed is there with changes?