javaoraclemavendbeaver

how to configue a dbeaver proxy connection to a private maven repository


I am using an internal maven/artifactory repository on my network.

I am trying to intialize an Oracle Connection with DBeaver 7.1.0. (not the eclipse plugin, the standalone program)

Each time it initializes, it fails to download the drivers. with the error

Error Resolving Dependencies
  Maven artifact 'maven:/com.oracle.database.xml:xmlparserv2:RELEASE' not found

I'm assuming this is because the proxy is blocking outside access to download files.

Knowing the contents of my ~/.m2/settings.xml


       <proxies>
         <proxy>
           <host>myproxy.foo</host>
           <port>80</port>
         </proxy>
       <proxies>
       <profiles>
        <profile>
          ...
          <repositories>
            <repository>
              <id>foobar</id>
              <name>mystuff</id>
              <url>https://my-interal-maven.foo/artifactory/mystuff</url>

what are the steps to configure the connection correctly so it can download the files?

EDIT: I bypassed using maven and manually copied the JARs into the settings, like the answer given by @FeodorG

enter image description here

Basically, when trying to get the driver working it would break when in Driver Settings -> "Download" throws error resolving dependencies... Error resolving dependencies Maven artifact 'maven:/com.oracle.database.nls:orai18n:RELEASE' not found

so I would go grab that jar in mvnRepository: and repeat for each other entry that would fail at downloading

https://mvnrepository.com/artifact/com.oracle.database.nls/orai18n/12.2.0.1
https://mvnrepository.com/artifact/com.oracle.database.xml/xmlparserv2/12.2.0.1
https://mvnrepository.com/artifact/com.oracle.database.xml/xdb6/12.2.0.1
https://mvnrepository.com/artifact/com.oracle.database.nls/orai18n/12.2.0.1

After replacing all entries with JARs on my filesystem... the connection worked!


Solution

  • Well, I had the same issue (all kinds of security settings issues on corporate networks were preventing me from setting up the driver).

    My workaround was to:

    So, in short, I just brought the jar files to my local drive and created a new driver and a new connection.