Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with top level dependency on Maven Central #42

Closed
datalemming opened this issue Apr 4, 2017 · 1 comment
Closed

Issue with top level dependency on Maven Central #42

datalemming opened this issue Apr 4, 2017 · 1 comment

Comments

@datalemming
Copy link

datalemming commented Apr 4, 2017

Hi,

I'd like to use Baleen on a project. I have added in the top level dependency from Maven Central to my pom file, as follows:

<dependency>
    <groupId>uk.gov.dstl.baleen</groupId>
    <artifactId>baleen</artifactId>
    <version>2.3.0</version>
</dependency>

but the build is failing. If you use one of the child packages it seems to work. Any ideas what I am doing wrong?

[ERROR] Failed to execute goal on project graph-loader-ejb: Could not resolve dependencies for project graph-loader-ejb:ejb:1.0-SNAPSHOT: Failure to find uk.gov.dstl.baleen:baleen:jar:2.3.0 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
[

@jbaker-dstl
Copy link
Contributor

The top level dependency is just a POM file, and isn't a JAR file. It contains only properties, common dependencies, build settings, etc. You should be adding the relevant child package, or if you want all of the packages then adding baleen-runner will include all of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants