gpt4 book ai didi

maven - 在 leiningen 项目中使用 maven 的 "LATEST"关键字

转载 作者:行者123 更新时间:2023-12-04 06:05:21 25 4
gpt4 key购买 nike

我有两个 leiningen 项目。根据this question ,maven 应该允许我使用“最新”作为依赖版本。它给了我一个错误,提示找不到版本为“LATEST”的依赖项。 This answer代表我如何在本地使用 leiningen 引用这个项目,如果这很重要的话。

我怎样才能让它工作?如果这不是您在项目中引用本地依赖项的方式,我愿意接受其他建议。

项目文件如下所示:

(defproject mongo-model "0.0.19-SNAPSHOT"
:description "A simple way to create model templates for mongodb for write-time data validation"
:dependencies [[org.clojure/clojure "1.3.0"]]
:main mongo-model.core)


(defproject bayou "0.1.0-SNAPSHOT"
:description "FIXME: write this!"
:dependencies [[org.clojure/clojure "1.3.0"]
[mongo-model "LATEST"]]
:main bayou.server)

运行 lein deps在第二个项目中给了我这个错误:
An error has occurred while processing the Maven artifact tasks.
Diagnosis:

Unable to resolve artifact: Missing:
----------
1) mongo-model:mongo-model:jar:LATEST

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=mongo-model -DartifactId=mongo-model -Dversion=LATEST -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=mongo-model -DartifactId=mongo-model -Dversion=LATEST -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) org.apache.maven:super-pom:jar:2.0
2) mongo-model:mongo-model:jar:LATEST

----------
1 required artifact is missing.

for artifact:
org.apache.maven:super-pom:jar:2.0

from the specified remote repositories:
clojars (http://clojars.org/repo/),
central (http://repo1.maven.org/maven2)



Exception in thread "main" Unable to resolve artifact: Missing:
----------
1) mongo-model:mongo-model:jar:LATEST

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=mongo-model -DartifactId=mongo-model -Dversion=LATEST -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=mongo-model -DartifactId=mongo-model -Dversion=LATEST -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) org.apache.maven:super-pom:jar:2.0
2) mongo-model:mongo-model:jar:LATEST

----------
1 required artifact is missing.

for artifact:
org.apache.maven:super-pom:jar:2.0

from the specified remote repositories:
clojars (http://clojars.org/repo/),
central (http://repo1.maven.org/maven2)

(NO_SOURCE_FILE:0)
at clojure.lang.Compiler.eval(Compiler.java:5440)
at clojure.lang.Compiler.eval(Compiler.java:5391)
at clojure.core$eval.invoke(core.clj:2382)
at clojure.main$eval_opt.invoke(main.clj:235)
at clojure.main$initialize.invoke(main.clj:254)
at clojure.main$script_opt.invoke(main.clj:270)
at clojure.main$main.doInvoke(main.clj:354)
at clojure.lang.RestFn.invoke(RestFn.java:457)
at clojure.lang.Var.invoke(Var.java:377)
at clojure.lang.AFn.applyToHelper(AFn.java:172)
at clojure.lang.Var.applyTo(Var.java:482)
at clojure.main.main(main.java:37)
Caused by: Unable to resolve artifact: Missing:
----------
1) mongo-model:mongo-model:jar:LATEST

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=mongo-model -DartifactId=mongo-model -Dversion=LATEST -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=mongo-model -DartifactId=mongo-model -Dversion=LATEST -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) org.apache.maven:super-pom:jar:2.0
2) mongo-model:mongo-model:jar:LATEST

----------
1 required artifact is missing.

for artifact:
org.apache.maven:super-pom:jar:2.0

from the specified remote repositories:
clojars (http://clojars.org/repo/),
central (http://repo1.maven.org/maven2)


at org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTask.java:175)
at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtifactTask.java:678)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:90)
at clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:265)
at leiningen.deps$do_deps.invoke(deps.clj:131)
at leiningen.deps$deps.doInvoke(deps.clj:195)
at clojure.lang.RestFn.invoke(RestFn.java:410)
at clojure.lang.Var.invoke(Var.java:365)
at clojure.lang.AFn.applyToHelper(AFn.java:161)
at clojure.lang.Var.applyTo(Var.java:482)
at clojure.core$apply.invoke(core.clj:542)
at leiningen.core$apply_task.invoke(core.clj:228)
at leiningen.core$_main.doInvoke(core.clj:294)
at clojure.lang.RestFn.invoke(RestFn.java:410)
at clojure.lang.AFn.applyToHelper(AFn.java:161)
at clojure.lang.RestFn.applyTo(RestFn.java:132)
at clojure.core$apply.invoke(core.clj:542)
at leiningen.core$_main.invoke(core.clj:297)
at user$eval42.invoke(NO_SOURCE_FILE:1)
at clojure.lang.Compiler.eval(Compiler.java:5424)
... 11 more
Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
----------
1) mongo-model:mongo-model:jar:LATEST

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=mongo-model -DartifactId=mongo-model -Dversion=LATEST -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=mongo-model -DartifactId=mongo-model -Dversion=LATEST -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) org.apache.maven:super-pom:jar:2.0
2) mongo-model:mongo-model:jar:LATEST

----------
1 required artifact is missing.

for artifact:
org.apache.maven:super-pom:jar:2.0

from the specified remote repositories:
clojars (http://clojars.org/repo/),
central (http://repo1.maven.org/maven2)


at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324)
at org.apache.maven.artifact.ant.DependenciesTask.doExecute(DependenciesTask.java:170)
... 34 more

最佳答案

这里有两件事在起作用:标准的依赖解析和 checkouts 的便利性。目录。
checkouts目录
checkouts 的功能目录非常简单:Leiningen 期望在那里找到一个或多个目录,每个目录都包含另一个 Leiningen 项目。通常您在这里创建指向其他项目的符号链接(symbolic link)。对于每个链接的项目,源路径、编译路径和资源路径都添加到类路径中。 (默认情况下 - 可以配置目录列表。)

这意味着链接项目的命名空间在父项目中可用,无论它们是否包含在依赖项中。不过,您仍然应该将它们包含在依赖项中,以便其他人可以使用您的代码库。

依赖项

依赖解析机制不关心 checkouts目录。它尝试在本地和远程 Maven 存储库中查找所有依赖项。如果您对从未安装在存储库中的本地项目有依赖关系,则无法找到它,即使项目链接到 checkouts 中,Leiningen 也会出现与您的问题中显示的错误类似的错误。目录。

您需要在本地存储库中至少安装一次您所依赖的 Artifact 。这就像调用 lein install 一样简单.您无需在每次更改后都执行此操作,因为您始终通过 checkouts 使用最新代码符号链接(symbolic link)。

关于LATEST的使用:我会说鼓励对依赖项使用固定版本号。这是防止曾经成功的构建由于依赖关系的变化而突然中断的唯一方法。另请参阅此问题:How do I tell Maven to use the latest version of a dependency?

关于maven - 在 leiningen 项目中使用 maven 的 "LATEST"关键字,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/8426195/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com