Aether | A sleek ArchLinux login manager for lightdm-webkit ( lightdm-webkit-theme-aether ) | Theme library

After discussion, the OP Mulgard confirms:

I solved it locally.
I needed to add my gitlab user to the project as a maintainer. Adding it to the group was not enough.

But thats only for local.

The gitlab build still does not run since I cant get the CI_JOB_TOKEN inside the docker.
But that is a different topic I guess.

From the project members permissions, at least Developer is needed for package registry publication.

The CI_JOB_TOKEN problem looks like this issue:

We are having this exact same issue on our gitlab-ce environment, with any attempt to push with "CI_JOB_TOKEN" as part of a pipeline resulting in:

We eventually found that it's a Maven issue that is the cause of our trouble.

It doesn't honor it's false settings and follows it whatever, and during the removal of a link file in target directory, npm causes (by Maven) the deletion of the file source of the link.

I found out the reason after I understood this log line better:

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

That is based on an earlier trial which has failed possible based on network issues etc. which results in having some partial artifacts in your local cache ($HOME/.m2/repository). Just try mvn -U package

As can be seen in the comments of the post, my problem is fixed, so I thought I'd collect a closing answer here to not leave the post pending.

The actual solution: As explained here nicely by @UninformedUser, the issue was that I had conflicting maven package versions in my dependencies. Bringing everything in sync with each other solved the issue.

Incidental solution: As I wrote in the comments above, specifically defining 3.3.0 for the maven-assembly-plugin happened to solve the issue. But this was only chance, as explained here by @Ignazio, just because the order of "assembling" things changed, overwriting the conflicting package.

Huge thanks to both for the help.

Using these properties:

Delete the .m2 folder then try again, I just experienced this.

You need to explicitly declare package type, default is jar if type is omitted.