Open ThorbenLindhauer opened 4 years ago
This comment was imported from JIRA and written by user @koevskinikola
Hey L3xJbNX,
Thanks for the report. I will forward the ticket for a decision.
As a side-note, the dependency can actually be downloaded from the Chromium Chromedriver page. This page explains how specific version can be found: https://chromedriver.chromium.org/downloads/version-selection. Here is a link to the version 2.27 files https://chromedriver.storage.googleapis.com/index.html?path=2.27/.
However, I'm only posting this for reference, since as you said, this shouldn't be required to build the OSS version, and we should only rely on Maven Central.
Best, Nikola
This comment was imported from JIRA and written by user L3xJbNXWhat is this name?
This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.
Hi @tmetzke
This ticket is about removing the dependency altogether. We shouldn't keep such a dependency on our nexus. I believe moving the dependency to a less used module/profile does not fix the problem
This issue was imported from JIRA:
What is this name?
This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.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:
Since we can't guarantee that, I would suggest that we remove our dependency on this custom artifact. As i mentioned to @ThorbenLindhauer the nexus public section is considered a convenience_ and not a _necessity. We shouldn't consider it as such.
AT:
Links: