Christoph Läubrich

@pzi-dsa this looks very interesting. Do you think you can add an integration test for this? There are already some for maven and updatesite authentication that might could be used...

> Authentication works when adding the repository directly to the pom, but fails if it is added to the location of the target platform. I must confess that I assumed...

@pzi-dsa if there is a public available example I can also try to take a look, but I have no password-protected setup at hand here to test...

Tycho injects the Maven artifacts into the model, and then maven tries to download them. In general, they should already be available locally then, but for the case of password-protected...

@pzi-dsa is this the error you are expecting? https://ci.eclipse.org/tycho/job/tycho-github/job/PR-1092/1/testReport/junit/org.eclipse.tycho.test.target/PasswordProtectedM2RepositoryTest/testTargetDefinition/

Alright, I think your previous code changes are not related to this failure and it would wonder me if they make anything better as we should inherit the maven settings...

Github action failures are unrelated.

@pzi-dsa thanks for the fix and for the test-case! Lets see if this improves the situation for you :+1:

> At the moment we have `includeAllDependencies=true` and `includeAllSources=false` for the Eclipse-Platform repo I'm not sure if `includeAllDependencies=true` is used, but regardless of what is sued for every bundle contained...

Code is there but @HannesWell wanted to provide a test-case for this so we can verify this works as intended.