The *Mylyn/Gitea Tasks Connector* is provided under the MIT License you may find a copy here [https://teilginn.github.io/mylyn-gitea-updatesite/LICENSE](https://teilginn.github.io/mylyn-gitea-updatesite/LICENSE)
### Thanks and Credits
I want to thanks and credit:
*`pweingardt` for the [Mylyn Gilab Connector](https://github.com/pweingardt/mylyn-gitlab) which helps me in my initial plug-ins setup.
*`zeripath` for the [Java Gitea API](https://github.com/zeripath/java-gitea-api) I used first to communicate with Gitea's instance before facing ssl and JDK 11 compliance issues.
* Contributors to the [GitHub Mylyn Connector](https://github.com/eclipse/egit-github) which helps me to understand how I can make GUI of the plugin different.
In addition to the _internal_ signature, a detached GPG signature will be provided for all files associated with the release, including this README and the certificate public key, in the `gpg/` directory.
More over all commits in *Mylyn/Gitea Tasks Connector* related repositories are also now *git-signed*.
* Public key certificate file in PEM format (selfsigned.pem)[https://teilginn.github.io/mylyn-gitea-updatesite/selfsigned.pem) or DER format (selfsigned.der)[https://teilginn.github.io/mylyn-gitea-updatesite/selfsigned.der)
In addition to *Mylyn/Gitea Tasks Connector Update Site* GPG public key file is available from the different Git repositories used to develop the plugin :
* Update Site sources [main repository](https://forge.chapril.org/gitea/mylyn-gitea-updatesite/src/commit/457a618b438b6a712221cfabae80aa799df83135/2A766910298F3874.asc) and [Github mirror](https://raw.githubusercontent.com/teilginn/mylyn-gitea-updatesite/master/2A766910298F3874.asc)
You can also check the GPG key validity/fingerprint from [keys.openpgp.org](https://keys.openpgp.org/) : [https://keys.openpgp.org/search?q=2A766910298F3874](https://keys.openpgp.org/search?q=2A766910298F3874)
1. Enter the project URL (something like `http(s)://my-gitea-instance.org/myname_or_organisation/my_repository(.git)`) (the connector will disguard the `.git` if present)
If you use *https* instead of http (*and you absolutely should use https*), be sure you have a _valid_ certificate. That means it is signed by a trusted CA.
If you don't have a _valid_ certificate like a self signed certificate, the plugin may refuse to connect. If you want to add your CA certificate to the
1. On Linux, Mac OS X, or Unix systems, use `keytool -import -alias A-UNIQUE-ALIAS -file YOUR-CA.crt -keystore $PATH_TO_YOUR_KEYSTORE` (root permissions may be necessary)
2. On Windows, in an Administrator Command Prompt use `"%PROGRAMFILES%\java\jre<JAVE-VERSION>\bin\keytool" -import -alias A-UNIQUE-ALIAS -file YOUR-CA.cer -keystore "%PROGRAMFILES%\Java\jre7\lib\security\cacerts"`
Note: Starting with Java8, Let'Encrypt Certificates are accepted default.
It is tested in front of *Gitea 1.14* Instance. It's highly recommended to keep your Gitea's instance up to date. You can use the [Gitea Auto Update](https://github.com/CMiksche/gitea-auto-update) script to do it for You.
* *Mylyn/Gitea Tasks Connector* is using the Gitea's instance Swagger API. It's obvious but it can only communicate with the Gitea's instance only if the Swagger API is activate. This feature is active by default, so contact your Gitea's instance administrator if it has been disabled.
* List of Eclipse versions plugins is compliant with, is to be defined. It will be test with the version of Eclipse I'm using (Linux/Windows) in front of an *always* up to date gitea instance.
* If you create a new milestone or add a new member via the web interface, you have to update the repository configuration or query properties, so that the connector reloads the project members and milestones. Right click on the Gitea repository in the Task repositories view and click on "Update Repository Configuration".
To avoid any account management activity, issues tracker is handled at [Github](https://github.com/teilginn/mylyn-gitea/issues).
Feel free to open issues to report bugs or request new features but please only write in English or in French (Google translate is not so good with technical tanslations)