Tigase: new repo location found (verified via website & playstore)

This was set to NoSourceSince as the original repo location got lost. Followed it up when stumbling upon its Github repo, verified via

• Google Play listing
• following the old (broken, insecure) repo link up to its roots

Hence removed NoSourceSince, updated URLs and added missing details.

@licaon-kter @Rudloff @uniqx can one of you please verify if the new versions still build, or whether adjustments to the build blocks are needed? If all is fine, we could re-enable auto-update as well (%v and tags).

Ah yuck, they use an insecure and untrusted Maven repo – their own:

maven {url "http://maven-repo.tigase.org/repository/release/"}

So I could either remove the Repo: url again – or a packager could check whether it can substituted/scan-ignored?

I think all these libraries are only available on their Maven repository: https://github.com/tigase/stork/blob/eb34cdba79d71ceea223b1214f8b367d54697393/app/build.gradle#L83

added 1 commit

• 236295a5 - fix Author field (must be AuthorName)

Compare with previous version

@IzzySoft there was an old issue with this #1359 (comment 193585901) and got stuck on "When we get the signal that the deps are in one of those allowed maven repos or that they get build along with the app....yes." though recent @licaon-kter comment on github would point into possibility of circumventing issue with maven-central presence and just building dependencies locally.

It's a matter of time yes, none available to take a look...

Is there (probably there is) an app, that you know that builds required dependencies that I could take a look as a point of reference?

Thanks for checking, Pierre & Licaon-Kter!

So shall I meanwhile remove the Repo: URL to get the other updates through – and the remaining stuff can be dealt with via a separate MR? Then at least the NoSourceSince will be gone, and repo, author, website etc. are pointing to the correct places.

added 1 commit

• b4030600 - Tigase: temporarily removing repo url until maven issue is solved

Compare with previous version

@.wojtek I'm neither packager nor dev, so I can just give raw references:

• git submodules could be used to integrate the dependencies with the app's repo
• srclibs are a way to achieve a comparable goal on our end

So you could "grep" for those keywords (submodules and srclib) in our .yml files to find some examples. Both are not that rare, so there should be several examples you could go by.

Now that the pipeline succeeded, I'm going to merge this. Whoever gets to work on the builds, be welcome to open a new MR. Thanks a lot again to all!

merged

mentioned in commit 8d96f389

Another solution is to get the libraries to build on JitPack. (Building currently fails: https://jitpack.io/com/github/tigase/jaxmpp/3.2.0/build.log)