Александър Куртаков
Александър Куртаков
I haven't found a way to disable logging for the server.
The following snippet generates "Failed to parse exception": ```bash #!/usr/bin/env bash echo CommandName InputFiles `#1st comment` \ --option1 arg1 `#2nd comment` \ --option2 arg2 `#3rd comment` ```
Wikitext is published to Maven Central using project GPG key as shown [here](https://ci.eclipse.org/docs/job/mylyn-wikitext-release). Tycho should do the same so artifacts are signed with the project key instead of developer key...
Java 17 is the latest LTS and new major version of Tycho is in the works. It's the perfect time to do this switch too.
Redoing the test based on artifact hopefully at https://repo.eclipse.org or another more available repository as https://nexus.se.rwth-aachen.de/repository/ doesn't seem to be such. It's not the first time connection fails.
It would make debugging easeir for debuging buildship e.g. when used by jdt.ls. Hopefully it would even help automating IPlab requests like https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/11675 (failng with no source found).
The project requires on the JNR stack for unixsocket but Java 16+ already provides native support. It would be nice to make use of it and drop this extra dependency...
Clearlydefined being less and less stable makes me wonder whether in case it is down licensetool should fail or it should list not approved artifacts so they are reported to...
In order to be able to use the new maven-plugin it has to be published to maven repository. It's too early to think of maven central so probably https://repo.eclipse.org/ is...
Today's build https://download.eclipse.org/eclipse/downloads/drops4/I20221119-1800/ contains no changes as per https://download.eclipse.org/eclipse/downloads/drops4/I20221119-1800/gitLog.php : ``` Git log from I20221119-0600 (previous) to I20221119-1800 (current) The tagging, and this report, were done at about 20221119-1806 ```...