This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
No really sure if this is a java or git module bug. I track my project under git. When I add the following to git (to fetch all pull requests): [remote "pr"] fetch = +refs/pull/*/head:refs/remotes/origin/pr/* url = git+ssh://git@github.com/graphhopper/graphhopper.git then NetBeans reports something with invalid wildcards (disappears very fast so I can't tell you the details ;)) when I try to create a new test for a class: hit CTRL+SHIFT+U and then simply ENTER And the dialog keeps open but no test is created. To fix this I can uncomment the above lines in .git/config and reopen my project.
Created attachment 135169 [details] The exception.
> fetch = +refs/pull/*/head:refs/remotes/origin/pr/* i have never seen such a use of refs specs. Is it allowed in git? Please point me to some documentation of this specific usage. Anyway, i will hardly fix this, it's coming from JGit, you should file a bug there and explain why their expected formats are insufficient: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JGit Looking at their parsing method, they expect: Parse a ref specification for use during transport operations. * <p> * Specifications are typically one of the following forms: * <ul> * <li><code>refs/head/master</code></li> * <li><code>refs/head/master:refs/remotes/origin/master</code></li> * <li><code>refs/head/*:refs/remotes/origin/*</code></li> * <li><code>+refs/head/master</code></li> * <li><code>+refs/head/master:refs/remotes/origin/master</code></li> * <li><code>+refs/head/*:refs/remotes/origin/*</code></li> * <li><code>:refs/head/master</code></li> * </ul> I can suppress the exception so it does not block creating the file, but that will probably end up in broken and unavailable git support for your project.
I'm not sure if this is a valid format but here you see it: https://gist.github.com/piscisaureus/3342247 and also others are using it :)
i took a quick check and it's probably fixed in JGit already: http://git.eclipse.org/c/jgit/jgit.git/commit/org.eclipse.jgit/src/org/eclipse/jgit/transport/RefSpec.java?id=a51899c2036984fa7a04290ca1364a02af34f95a But we have to wait until JGit 3.0 is released.
ok, thanks!
for now i'll try to workaround the exception so the exception does not block you. We won't upgrade JGit sooner than in the next release (after 7.4)
No workaround or hurry is necessary. I mean for me this is not critical. I can uncomment these lines and all is fine.
fix: http://hg.netbeans.org/core-main/rev/3e7f2efc32e7
Integrated into 'main-golden', will be available in build *201306012301* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/3e7f2efc32e7 User: Ondrej Vrabec <ovrabec@netbeans.org> Log: #230535 - Because of git I cannot create a test case the exception is only logged and user is notified only when it's really needed (running fetch, pull, push)
*** Bug 230608 has been marked as a duplicate of this bug. ***
In case anyone else wanders through here with a similar issue. Mine was caused on Windows with the GitHub client. Uninstalling (Including ALL the user directories) and re-installing that cleared the issue for me