当前位置: 首页 > 知识库问答 >
问题:

未能解析Vaadin 7.6.2与常春藤的依赖关系

澹台权
2023-03-14

我无法使用Apache Ivy解决我的vaadin 7项目。每当我尝试时,它都会显示一个错误框,其中显示

“常春藤解决”遇到了一个问题。某些项目无法解决。

在单击错误框上的“详细信息”按钮时,我得到了以下附加信息

某些项目无法解决无法解决com.example#v7proj;的依赖项;working@User无法解析的依赖项:com.vaadin#vaadin客户端已编译;7.6.2:未找到未解析的依赖项:com.vaadin#vaadin themes;7.6.2:未找到无法解析的依赖项:com.vaadin#vaadin push;7.6.2:未找到无法解析的依赖项:com.vaadin#vaadin server;7.6.2:未找到无法解析的依赖项:com.vaadin#vaadin客户端编译器;7.6.2:未找到无法解析的依赖项:com.vaadin#vaadin client;7.6.2:未找到未解析的依赖项:javax.servlet#javax.servelt-api;3.0.1:未找到

ivy.xml

<?xml version="1.0"?>
<!DOCTYPE ivy-module [
    <!ENTITY vaadin.version "7.6.2">
]>
<ivy-module version="2.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd">
    <info organisation="com.example" module="v7proj" />
    <configurations>
        <!-- The default configuration, which should be deployed to the server -->
        <conf name="default" />
        <!-- A configuration only needed when compiling the widget set. Should 
            not be deployed to the server -->
        <conf name="widgetset-compile" />
        <!-- A configuration used in compilation of server side classes only.
            Should be deployed to the server -->
        <conf name="nodeploy" />
    </configurations>
    <dependencies defaultconf="default" defaultconfmapping="default->default">
        <!-- The core server part of Vaadin -->
        <dependency org="com.vaadin" name="vaadin-server" rev="&vaadin.version;" />

        <!-- Vaadin themes -->
        <dependency org="com.vaadin" name="vaadin-themes" rev="&vaadin.version;" />

        <!-- Push support -->
        <dependency org="com.vaadin" name="vaadin-push" rev="&vaadin.version;" />

        <!-- Servlet 3.0 API -->
        <dependency org="javax.servlet" name="javax.servlet-api" rev="3.0.1" conf="nodeploy->default" />

        <!-- Precompiled DefaultWidgetSet -->
        <dependency org="com.vaadin" name="vaadin-client-compiled"
            rev="&vaadin.version;" />

        <!-- Vaadin client side, needed for widget set compilation -->
        <dependency org="com.vaadin" name="vaadin-client" rev="&vaadin.version;"
             conf="widgetset-compile->default" />

        <!-- Compiler for custom widget sets. Should not be deployed -->
        <dependency org="com.vaadin" name="vaadin-client-compiler"
            rev="&vaadin.version;" conf="widgetset-compile->default" />

    </dependencies>
</ivy-module>

ivysettings.xml

<?xml version="1.0" encoding="UTF-8"?>
<ivysettings>
    <settings defaultResolver="default" />
    <resolvers>
        <chain name="default">
            <!-- Public Maven repository -->
            <ibiblio name="public" m2compatible="true" />

            <!-- Vaadin Add-on repository -->
            <ibiblio name="vaadin-addons" usepoms="true" m2compatible="true"
                root="http://maven.vaadin.com/vaadin-addons" />

            <!-- Vaadin snapshots repository -->
            <ibiblio name="vaadin-snapshots" usepoms="true" m2compatible="true"
                root="https://oss.sonatype.org/content/repositories/vaadin-snapshots" />
            <!-- Repository used for Vaadin modified smartsprites library -->
            <dual name="custom-smartsprites">
                <filesystem name="smartsprites-ivy">
                    <ivy pattern="${basedir}/ivymodule/[module]-ivy-[revision].xml" />
                </filesystem>
                <url name="smartsprites-artifact">
                    <artifact
                        pattern="http://dev.vaadin.com/svn/versions/6.8/build/smartsprites/lib/[artifact](-[revision]).[ext]" />
                </url>
            </dual>
        </chain>
    </resolvers>
    <modules>
        <!-- Vaadin patched SmartSprites -->
        <module organisation="com.carrotsearch" name="smartsprites"
            revision="0.2.3-itmill" resolver="custom-smartsprites" />
    </modules>


</ivysettings>

我检查了存储库Central repository,它包含所有必需的jar。那为什么它没有解决?

更新:

我查看了Ivy控制台,发现了以下日志

[IvyDE] Resolve job starting...
[IvyDE] Processing resolve request ivy.xml[*] in MyProject
[IvyDE] 1 module(s) to resolve outside the workspace
[IvyDE] Resolving ivy.xml[*] in MyProject
:: resolving dependencies :: com.example#v7proj;working@Shakir
    confs: [default, widgetset-compile, nodeploy]
:: resolution report :: resolve 22ms :: artifacts dl 0ms
    ---------------------------------------------------------------------
    |                  |            modules            ||   artifacts   |
    |       conf       | number| search|dwnlded|evicted|| number|dwnlded|
    ---------------------------------------------------------------------
    |      default     |   4   |   0   |   0   |   0   ||   0   |   0   |
    | widgetset-compile|   2   |   0   |   0   |   0   ||   0   |   0   |
    |     nodeploy     |   1   |   0   |   0   |   0   ||   0   |   0   |
    ---------------------------------------------------------------------

:: problems summary ::
:::: WARNINGS
        module not found: com.vaadin#vaadin-server;7.6.2

    ==== local: tried

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-server\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-server;7.6.2!vaadin-server.jar:

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-server\7.6.2\jars\vaadin-server.jar

    ==== shared: tried

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-server\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-server;7.6.2!vaadin-server.jar:

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-server\7.6.2\jars\vaadin-server.jar

    ==== public: tried

      https://repo1.maven.org/maven2/com/vaadin/vaadin-server/7.6.2/vaadin-server-7.6.2.pom

      -- artifact com.vaadin#vaadin-server;7.6.2!vaadin-server.jar:

      https://repo1.maven.org/maven2/com/vaadin/vaadin-server/7.6.2/vaadin-server-7.6.2.jar

        module not found: com.vaadin#vaadin-themes;7.6.2

    ==== local: tried

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-themes\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-themes;7.6.2!vaadin-themes.jar:

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-themes\7.6.2\jars\vaadin-themes.jar

    ==== shared: tried

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-themes\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-themes;7.6.2!vaadin-themes.jar:

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-themes\7.6.2\jars\vaadin-themes.jar

    ==== public: tried

      https://repo1.maven.org/maven2/com/vaadin/vaadin-themes/7.6.2/vaadin-themes-7.6.2.pom

      -- artifact com.vaadin#vaadin-themes;7.6.2!vaadin-themes.jar:

      https://repo1.maven.org/maven2/com/vaadin/vaadin-themes/7.6.2/vaadin-themes-7.6.2.jar

        module not found: com.vaadin#vaadin-push;7.6.2

    ==== local: tried

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-push\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-push;7.6.2!vaadin-push.jar:

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-push\7.6.2\jars\vaadin-push.jar

    ==== shared: tried

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-push\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-push;7.6.2!vaadin-push.jar:

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-push\7.6.2\jars\vaadin-push.jar

    ==== public: tried

      https://repo1.maven.org/maven2/com/vaadin/vaadin-push/7.6.2/vaadin-push-7.6.2.pom

      -- artifact com.vaadin#vaadin-push;7.6.2!vaadin-push.jar:

      https://repo1.maven.org/maven2/com/vaadin/vaadin-push/7.6.2/vaadin-push-7.6.2.jar

        module not found: com.vaadin#vaadin-client-compiled;7.6.2

    ==== local: tried

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-client-compiled\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-client-compiled;7.6.2!vaadin-client-compiled.jar:

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-client-compiled\7.6.2\jars\vaadin-client-compiled.jar

    ==== shared: tried

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-client-compiled\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-client-compiled;7.6.2!vaadin-client-compiled.jar:

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-client-compiled\7.6.2\jars\vaadin-client-compiled.jar

    ==== public: tried

      https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiled/7.6.2/vaadin-client-compiled-7.6.2.pom

      -- artifact com.vaadin#vaadin-client-compiled;7.6.2!vaadin-client-compiled.jar:

      https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiled/7.6.2/vaadin-client-compiled-7.6.2.jar

        module not found: com.vaadin#vaadin-client;7.6.2

    ==== local: tried

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-client\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-client;7.6.2!vaadin-client.jar:

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-client\7.6.2\jars\vaadin-client.jar

    ==== shared: tried

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-client\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-client;7.6.2!vaadin-client.jar:

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-client\7.6.2\jars\vaadin-client.jar

    ==== public: tried

      https://repo1.maven.org/maven2/com/vaadin/vaadin-client/7.6.2/vaadin-client-7.6.2.pom

      -- artifact com.vaadin#vaadin-client;7.6.2!vaadin-client.jar:

      https://repo1.maven.org/maven2/com/vaadin/vaadin-client/7.6.2/vaadin-client-7.6.2.jar

        module not found: com.vaadin#vaadin-client-compiler;7.6.2

    ==== local: tried

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-client-compiler\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-client-compiler;7.6.2!vaadin-client-compiler.jar:

      C:\Users\Shakir\.ivy2\local\com.vaadin\vaadin-client-compiler\7.6.2\jars\vaadin-client-compiler.jar

    ==== shared: tried

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-client-compiler\7.6.2\ivys\ivy.xml

      -- artifact com.vaadin#vaadin-client-compiler;7.6.2!vaadin-client-compiler.jar:

      C:\Users\Shakir\.ivy2\shared\com.vaadin\vaadin-client-compiler\7.6.2\jars\vaadin-client-compiler.jar

    ==== public: tried

      https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiler/7.6.2/vaadin-client-compiler-7.6.2.pom

      -- artifact com.vaadin#vaadin-client-compiler;7.6.2!vaadin-client-compiler.jar:

      https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiler/7.6.2/vaadin-client-compiler-7.6.2.jar

        module not found: javax.servlet#javax.servlet-api;3.0.1

    ==== local: tried

      C:\Users\Shakir\.ivy2\local\javax.servlet\javax.servlet-api\3.0.1\ivys\ivy.xml

      -- artifact javax.servlet#javax.servlet-api;3.0.1!javax.servlet-api.jar:

      C:\Users\Shakir\.ivy2\local\javax.servlet\javax.servlet-api\3.0.1\jars\javax.servlet-api.jar

    ==== shared: tried

      C:\Users\Shakir\.ivy2\shared\javax.servlet\javax.servlet-api\3.0.1\ivys\ivy.xml

      -- artifact javax.servlet#javax.servlet-api;3.0.1!javax.servlet-api.jar:

      C:\Users\Shakir\.ivy2\shared\javax.servlet\javax.servlet-api\3.0.1\jars\javax.servlet-api.jar

    ==== public: tried

      https://repo1.maven.org/maven2/javax/servlet/javax.servlet-api/3.0.1/javax.servlet-api-3.0.1.pom

      -- artifact javax.servlet#javax.servlet-api;3.0.1!javax.servlet-api.jar:

      https://repo1.maven.org/maven2/javax/servlet/javax.servlet-api/3.0.1/javax.servlet-api-3.0.1.jar

        ::::::::::::::::::::::::::::::::::::::::::::::

        ::          UNRESOLVED DEPENDENCIES         ::

        ::::::::::::::::::::::::::::::::::::::::::::::

        :: com.vaadin#vaadin-server;7.6.2: not found

        :: com.vaadin#vaadin-themes;7.6.2: not found

        :: com.vaadin#vaadin-push;7.6.2: not found

        :: com.vaadin#vaadin-client-compiled;7.6.2: not found

        :: com.vaadin#vaadin-client;7.6.2: not found

        :: com.vaadin#vaadin-client-compiler;7.6.2: not found

        :: javax.servlet#javax.servlet-api;3.0.1: not found

        ::::::::::::::::::::::::::::::::::::::::::::::

:::: ERRORS
Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-server/7.6.2/vaadin-server-7.6.2.pom (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-server/7.6.2/vaadin-server-7.6.2.jar (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-themes/7.6.2/vaadin-themes-7.6.2.pom (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-themes/7.6.2/vaadin-themes-7.6.2.jar (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-push/7.6.2/vaadin-push-7.6.2.pom (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-push/7.6.2/vaadin-push-7.6.2.jar (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiled/7.6.2/vaadin-client-compiled-7.6.2.pom (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiled/7.6.2/vaadin-client-compiled-7.6.2.jar (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-client/7.6.2/vaadin-client-7.6.2.pom (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-client/7.6.2/vaadin-client-7.6.2.jar (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiler/7.6.2/vaadin-client-compiler-7.6.2.pom (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiler/7.6.2/vaadin-client-compiler-7.6.2.jar (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/javax/servlet/javax.servlet-api/3.0.1/javax.servlet-api-3.0.1.pom (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

Server access error at url https://repo1.maven.org/maven2/javax/servlet/javax.servlet-api/3.0.1/javax.servlet-api-3.0.1.jar (javax.net.ssl.SSLException: Received fatal alert: protocol_version)

:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
[IvyDE] Error on resolve of ivy.xml[*] in MyProject: Impossible to resolve dependencies of com.example#v7proj;working@Shakir

共有2个答案

范浩荡
2023-03-14

将下一段代码添加到ivysettings.xml中

<url name="ibiblio" m2compatible="true">
            <artifact pattern="http://repo1.maven.org/maven2/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
        </url>
澹台玉石
2023-03-14

这是常春藤中的问题,默认情况下它使用旧的TLS 1.0版本,maven中心不再支持该版本。您需要重新配置它。您可以从Vaadin论坛和另一个StackOverflow问题中找到更多信息,为什么我从Maven Central收到“收到致命警报:protocol_version”或“对等体未通过身份验证”?

 类似资料:
  • 我是艾薇的新手,所以这可能已经被报道过了,但是我知道的还不够多。我的搜索结果是空的,没有找到类似的经历。 因此,当我第一次下拉整个项目并且更新库引用时,我有时会收到未解决的依赖项警告。它似乎在随机库上。 例如,我刚刚在某个项目中添加了Commons-codec-1.9,而工作集中的其他项目使用1.6和1.7。当运行盛大的构建脚本时,突然对于1.6和1.7“配置[is]未找到”: 现在,我不完全确定

  • 我作为一个Maven新手,我正在玩我自己的本地Sonartype Nexus。我已经将我的maven安装配置为使用它作为代理,并且在解决我的< code>pom.xml中的以下依赖关系时,它对于一个简单的测试项目工作得很好 接下来,我尝试了一个类似的项目 在.常春藤使用与代理相同的Nexus服务器(在中配置.xml) 但是,在运行ant时,它无法解析 我已经尝试在Nexus安装中添加更多的远程存储

  • 我无法通过终端用Ant编译源代码,因为尽管我发出了“Ant resolve or Ant retrieve”,但依赖项似乎没有正确解析? 下面是我的build.xml和ivy.xml 编译文件 ivy.xml 当我运行“ant-compile”时,on-compiling ant抱怨它找不到作为tomcat一部分的“Servlet Context”。jar或“TObject”、“THashMap”

  • 问题内容: 我在ivaven.xml中添加了一个依赖项(让我们将其命名为A),它在maven Central中具有一个pom文件。Ivy使用ibiblio解决了Maven依赖关系。添加到ivy.xml的依赖项(A)具有传递的依赖项(B)。到目前为止,到目前为止很好。常春藤无法解决传递性依赖项(B)的依赖项(C)。 我在ivy.xml中定义了A,如下所示: 在B的pom文件中,在编译和测试范围中都定

  • 使用日食(赫利俄斯)的常春藤2.2和常春藤DE 2.2。... 想从http://maven . spring framework . org/milestone/org/spring framework/data/spring-data-neo4j/2 . 1 . 0 . m1获取spring-data-neo4j及其默认依赖项 在我的常春藤文件中使用以下内容: 以及我的设置文件中的这些解析器:

  • 我有一个简单的文件: 其中是我的配置名称,是映射的Maven类型。这被正确解析并给我这些文件: 现在,我必须添加这个依赖项: 它将< code>validation-api作为其依赖项,与我在顶部指定的相同。 艾薇解决了这个问题,给了我这些文件: 但这次没有检索到文件。为什么?我认为这个文件没有冲突……我应该怎么做才能拥有和jar(二进制和源代码)?