-
Notifications
You must be signed in to change notification settings - Fork 724
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
Artifact on Maven Central is broken #62
Comments
I have the same problem. It's impossible to use fnlp-core 2.1 in a Maven project because of the broken pom file referring to a parent project which does not exist. |
fnlp-all.zip |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The artifact of the project currently published on Maven Central is broken and can't be checked out automatically with dependency management systems. The Jar file can, however, be manually downloaded.
The POM of the artifact org.fnlp.fnlp-core contains the following parent tag:
org.fnlp fnlp-all 2.1-SNAPSHOT ../pom.xmlHowever, there is no artifact called fnlp-all in Maven Central.
It is therefore not possible to use it as a managed dependency; the download will fail.
Solution
I believe the simplest solution would be to re-publish the artifact removing the tag altogether.
Effect
When using the following snippet with Leiningen:
and running lein deps, the build fails with the following message:
A workaround is to download the jar manually; however, this makes production deployment impossible in my environment.
The text was updated successfully, but these errors were encountered: