| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| | |
Double escaped backslashes, wrongly escaped unicode codes, broken escaped
newlines.
|
| |
| |
| |
| |
| |
| |
| | |
Some property keys had typos.
There is a `gb.ticketStatus` and a `gb.ticketState`. Neither is used
anywhere in the code, but only the former is defined in the default file.
So only use `gb.ticketStatus`.
|
| |
| |
| |
| | |
If keeps acting up when trying to stage parts of it. I hope this fixes that.
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
Some property keys were duplicated, mostly `status`, `permission` and
`comment`.
The problem with `gb.comment` is, that it is used in two different
locations in two different meanings. One as a verb, the second as a
noun. Which makes no difference in English, but other languages.
The solution is that the second key is renamed to `gb.sshKeyComment`.
The code is adjusted accordingly.
|
|\
| |
| | |
Fix norwegian properties file
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To prevent that we have a resource file in a resource bundle broken and
not loading undiscovered for years, add a unit test that will load the
resource properties file for each of the languages.
In order to check if the file was loaded and the bundle mechanism
didn't fall back on the default, a new property key is added to each
language file, solely for the purpose to be checked in the unit test.
|
|/
|
|
| |
This fixes #834
|
|\
| |
| |
| |
| |
| |
| | |
This commit merges the pull request from Zwixx, with additional
changes via a separate Zwixx-fix-cmds branch.
Closes #1370
|
| |
| |
| |
| |
| |
| |
| |
| | |
Fix the output of the help texts in the reindex-tickets and
reindex-tickets bash scripts.
For one the double quotes are unnecessary and get printed out, too.
Secondly, an empty line needs a `echo.`. A simple `echo` will prin the
state of the echo setting, i.e. `Echo is enabled (1)` or something similar.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use SETLOCAL in batch scripts to restrict the visibility of variables
that are set in the script to the script execution. Otherwise the variables
will also be set in the calling shell. That is not a problem when a script
is executed by double clicking it in Windows Explorer. But now that the
scripts are changed so that they can be called on the command line from
other folders, they should also no clutter the calling environment.
|
| |
| |
| |
| |
| | |
Use the path of the script for the Gitblit home path in the remaining
batch scripts, too, to make it possible to call them from any other folder.
|
| | |
|
|/
|
|
|
|
|
|
| |
In order to call the Windows batch scripts on the command line
from a different folder, the path to the files in the Gitblit
directory needs to be explicitly stated in the Java command.
Otherwise the JAR files or data directory are not found as they
would be searched in the current directory.
|
|
|
|
|
|
|
|
| |
The last fix for the stored config merged from Curly060 used Java8-isms.
In order to be able to include this fix in the next release, which will
be for 1.9, I have converted this to be compatible with Java 7.
Also, a file header was added to place it under APL.
|
| |
|
|\
| |
| | |
Update simplified Chinese translation
|
|/
|
| |
Updated simplified Chinese translation and added missing entries. This translation is now 100% completed.
|
|
|
|
|
|
|
| |
Ohloh got acquired by Synopsis and is nor Open Hub.
Change the links for the tiny widget to point to Open Hub.
Closes #1356
|
| |
|
|
|
|
|
|
| |
Add a link parser also for `ExpLinks` because we need to escape paths
to files in subfolders.
This closes #1358
|
|
|
|
| |
Add that issue 879 was fixed in release 1.8.0
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a branch has a slash in the name, the raw servlet was not able
to find the path under that branch. This is due to the replacement of
the forward slash character for URLs. It was not taken into account
when comparing the branch name later.
This fixes #1290 and its duplicates #1234 and #813.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While this may be an unlikely scenario, let's still prevent this.
When a link was created for a path that ends in a trailing slash,
that trailing slash would be replaced with the `forwardSlashCharacter`.
But in getPath that final slash would be transformed back *after* the
check to chop off trailing slashes. This is now switched so that such a
trailing slash is also chopped off.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Refactor the `getBranch` and `getPath` methods to take a String as
second parameter, which is the already sanitised path info. Don't get
the path info from a passed in request anymore.
The methods are only ever called from within `processRequest`, which
already does some checks on the path info, like removing a leading
slash character. So no need to do that every time again the methods
and passing a request for that.
|
| | |
|
|/
|
|
|
|
| |
When creating a link for raw display, a trailing slash is stripped from
the end of the base URL. Also do this for the repository, as well as
stripping leading slashes from the repository and the path values.
|
| |
|
|\
| |
| | |
deps: Upgrade dependency Mockito to 2.28.2.
|
|/ |
|
|\
| |
| | |
Fix 1150: Use external link instead of internal wiki link
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `tickets_overview` page links to the `tickets_setup` page using a
wiki style internal link: `[[tickets setup]]`. Whatever library is
interpreting that is creating a link under the assumption that the
resulting page will be called `tickets-setup.html`. But that is not the
convention used by Moxie, which will use the source file name and thus
create a file called `tickets_setup.html`.
I was not able to find out which of the many libraries included is the
one that parses this file and creates the link. Messy.
There are two solutions. One is to configure the Moxie site build to
generate the file as `tickets-setup.html`. But this would break any
links to that page that might exist somewhere on the Interweb. So I
opted for the other option, which is to not use wiki syntax for the
reference to the local page but normal markdown syntax. This is not
a wiki, afterall.
|
|\
| |
| | |
build: Create single XML JaCoCo report
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When building with Ant, instead of Moxie, JaCoCo is not included in the
classpath. So explicitly initialise the full `jacocoant.jar` from the
`.moxie` repository.
For this we had to switch the dependency to use the `nodeps` jar which
includes all dependencies.
|
|/
|
|
| |
This can be uploaded to coverage services like Coveralls etc.
|
|
|
|
|
| |
Add some guidelines for contributors regarding pull requests,
commits and code conventions.
|
|\
| |
| | |
Add service scripts for FreeBSD
|
|/ |
|
| |
|
| |
|
|
|
|
| |
Also: release notes.
|
|
|
|
|
|
|
| |
Update the service scripts to use `-cp` and specify the GitBlitServer
class, instead of the `-jar` parameter.
Fixes #1333
|
|
|
|
|
|
|
|
|
| |
While most systems will not need the class path passed to the JVM with
the `-cp` parameter to be in quotes, apparently some exist where that
will not work without the quotes, e.g. FreeBSD.
So always use quotes for the class path in all scripts.
Issue #1333
|
|
|
|
|
| |
This is needed for the scripts to work in Alpine Linux, which
comes with a Bourne shell.
|
|
|
|
|
|
| |
Zero out the password to remove it from memory after use.
This is only a first step, implementing it for one method:
`AuthenticationManager.authenticate(String, char[], String)`.
|
|
|
|
|
|
|
|
|
|
| |
The upgrade of a MD5 stored password hash to a PBKDF password hash
destroys the stored password. The has check zeroes out the password that
is tested, so that the new hash is built over the zeroed out value.
This fix prevents that an also adds a check to the test.
Fixes #1335
|
| |
|