59 Commits (4f5709acfa3ec9579f380b2f0c132c1db8ac4300)

Author	SHA1	Message	Date
Graham	282dbd268b	Remove repository credentials from the repositories block ... The repositories are now public. Credentials are only required for deployment.	5 years ago
Graham	bb6bd3861e	Switch to the ISC license ... I've been considering this for a long time, and have decided to switch to it at the last minute before opening the repository up publicly. My reasons include: * It's a much simpler license. GPL's complexity adds some risk - for example, it might be incompatible with future open-source licenses (like the well-known GPLv2/Apache v2 incompatibility problem). The "or any later version" clause requires placing some trust in the Free Software Foundation. * The simplicity makes it easier for people to understand and comply with the license. * Dishonest users who disobey the GPL would have an advantage over honest users who refuse to do so. The ISC license provides a much more even playing field. * OpenRS2 will primarily be server software accessible over a network. As such, the GPL can do little to prevent use of the code in a proprietary system, as the code is never distributed. (While the AGPL would fix this, I have already discounted it. Enforcement would be too difficult and dishonest users would have an unfair advantage.) * It's much easier to switch to a stricter license in future versions, if it turns out that is desirable (as the ISC license allows users to sublicense the code). However, switching from the GPL to the ISC license requires all copyright holders to grant permission. * Other open-source projects in the community, such as Apollo, use the ISC license and will be able to make use of OpenRS2 code if they so desire. I've removed the FAQ entry about the reasons for using the GPL license, as I think the ISC license is less controversial and therefore does not require an entry. I've discussed this with Desetude, and he's okay with his commit being relicensed.	5 years ago
Graham	09bdf640f4	Add openrs2 prefix to repo{Username,Password} properties ... These might be added to the user's ~/gradle.properties file, at which point having a per-project prefix is useful. Ideally I'd have preferred to use openrs2.repo.{username,password}. However, Gradle properties with dots in them can't be configured with the ORG_GRADLE_PROJECT_* environment variables, which we use in the Jenkinsfile.	5 years ago
Graham	5d813a345d	Reduce priority of mavenLocal() to fix dependencyUpdates	5 years ago
Graham	641da067da	Depend on kotlin-inline-logger directly	5 years ago
Graham	7708056488	Use kotlin-inline-logger from Maven Central	5 years ago
Graham	e6ac51688c	Skip openrs2 repositories if no username/password are supplied	5 years ago
Graham	a1d1c74987	Enable strict JSR-305 mode	5 years ago
Graham	ccbbf873af	Switch from Maven to Gradle	5 years ago