Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Gitblit Manager launch issue
See original GitHub issueIt seems the latest version of Gitblit Manager v1.9.2 is broken and doesn’t start in Windows. At least 3 java classes are missing in \com\gitblit\client subfolder of manager.jar: GitblitManagerLauncher.class, GitblitManagerLauncher$1.class, GitblitManagerLauncher$2.class.
Also the manifest file \META-INF\Manifest.mf must be corrected at line 16:
main-class: com.gitblit.client.GitblitManagerLauncher
After those changes, I could launch GM without issues by command: java -jar manager.jar (jre1.8.0_321 environment).
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks, it works. I restored an original manager.jar from distributive and updated BAT file.
Gitblit does currently not run with Java-17, due to other restrictions introduced in Java-17. For all other Java versions this is the only way to start the Manager, since the Launcher is no longer there and the JARs from the
extdirectory must be explicitly put on the class path.The
%CD%uses the WindowsCDenvironment variable which resolves to the current path. So this still only works if you are in the directory with themanager.jarandextdirectory. You can also simply use:java -cp "manager.jar;ext/*" com.gitblit.client.GitblitManagerWell, I haven’t tried it on Windows, but you should just as well be able to leave the%CD%out.It is probably best to put this in a small BAT file.