atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Jones (JIRA)" <>
Subject [jira] [Commented] (ATLAS-2084) Make berkeley DB backed Atlas available without external download
Date Mon, 20 Nov 2017 18:07:00 GMT


Nigel Jones commented on ATLAS-2084:

To clarify - having done a mvn dependency check, the path is
[INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ atlas-graphdb-janus ---
[INFO] +- org.janusgraph:janusgraph-berkeleyje:jar:0.2.0:compile
[INFO] |  \- com.sleepycat:je:jar:7.3.7:compile

I notice if doing a dependency:list-dependencies a number of
[WARNING] Missing POM for com.sleepycat:je:jar:7.3.7

However when try
18:04 $ mvn dependency:get -Dartifact=com.sleepycat:je:jar
I get:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.10:get (default-cli)
on project apache-atlas: Couldn't download artifact: Missing:
[ERROR] ----------
[ERROR] 1) com.sleepycat:je:jar:jar
[ERROR]   Try downloading the file manually from the project website.
[ERROR]   Then, install it using the command: 
[ERROR]       mvn install:install-file -DgroupId=com.sleepycat -DartifactId=je -Dversion=jar
-Dpackaging=jar -Dfile=/path/to/file
[ERROR]   Alternatively, if you host your own repository you can deploy the file there: 
[ERROR]       mvn deploy:deploy-file -DgroupId=com.sleepycat -DartifactId=je -Dversion=jar
-Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR]   Path to dependency: 
[ERROR]   	1) org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR]   	2) com.sleepycat:je:jar:jar
[ERROR] ----------
[ERROR] 1 required artifact is missing.
[ERROR] for artifact: 
[ERROR]   org.apache.maven.plugins:maven-downloader-plugin:jar:1.0
[ERROR] from the specified remote repositories:
[ERROR]   central (, releases=true, snapshots=false),
[ERROR]   hortonworks.repo (, releases=true,
[ERROR]   apache.snapshots.repo (, releases=true,
[ERROR]   apache-staging (, releases=true,
[ERROR]   default (, releases=true, snapshots=true),
[ERROR] (, releases=true, snapshots=true),
[ERROR] (,
releases=true, snapshots=true),
[ERROR]   typesafe (, releases=true, snapshots=true),
[ERROR]   apache.snapshots (, releases=false, snapshots=true)
[ERROR] -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following
[ERROR] [Help 1]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :apache-atlas
✘-1 ~/src/atlas [master|⚑ 11] 

I think the result of this is that although a dependency is expressed by Janus, it is not
being pulled in by maven, and thus would not work.

This means this JIRA does need work, with a few mods to the original proposal - the scope
of the repo needs to be top level, and we should change the artifact name accordingly.

> Make berkeley DB backed Atlas available without external download
> -----------------------------------------------------------------
>                 Key: ATLAS-2084
>                 URL:
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Nigel Jones
>            Assignee: Nigel Jones
>         Attachments: ATLAS_2084_Add_BerkeleyDB_libraries.patch
> In I proposed providing a dockerized
version of Atlas to aid people getting up to speed with the technology. During the review
it was noted that we had used Hbase for storage rather than the more lightweight, simpler,
BerkeleyDB. My concern had been around licensing.
> Today when we build Atlas following the instructions at
the user is directed to download the berkeleyDB jar from oracle. In ATLAS-2012 David/Graham
pointed out that this DB appears to be Apache 2.0 licensed, which means we could incorporate
it into our build legitimately.
> Given the necessity to get licensing correct I've opened up this new JIRA to focus on
that change. We would need to
>  * Validate we are indeed correct about the license
>  * Add the DB file into the build
>  * Update the web instructions
>  * And optionally as per the original JIRA, consider making B-DB the default for our
docker image (most lightweight).
> Please add your thoughts. I'm happy to get and do this change .

This message was sent by Atlassian JIRA

View raw message