While building camunda-bpm-platform without using our own nexus I noticed that we have a dependency on chromedriver:chromedriver:zip:2.27 that is impossible to resolve.

It looks like this artifact was uploaded manually to our nexus and it's not available anywhere else (or at least, I couldn't find it).

This poses two main problems:

• As a contributor, I expect to be able to build camunda-bpm-platform without relying on manually uploaded artifacts on third-party nexus. Ideally a contributor should be able to build Cambpm (OSS version) relying just on maven central
• We are currently distributing this artifact to all the users of our nexus, since it's stored in the public section of our artifact repository. We should verify if that's permitted by the license.

Since we can't guarantee that, I would suggest that we remove our dependency on this custom artifact. As i mentioned to thorben.lindhauer the nexus public section is considered a convenience and not a necessity. We shouldn't consider it as such.

AT:

• Dependency on chromedriver:chromedriver:zip:2.27 is removed from the camunda-bpm-platform repository and eventually backported
• The artifact is removed from our nexus
• Camunda BPM platform is able to build without using our custom nexus (maybe follow-up ticket?)