- android - 多次调用 OnPrimaryClipChangedListener
- android - 无法更新 RecyclerView 中的 TextView 字段
- android.database.CursorIndexOutOfBoundsException : Index 0 requested, 光标大小为 0
- android - 使用 AppCompat 时,我们是否需要明确指定其 UI 组件(Spinner、EditText)颜色
我无法使用 Apache Ivy 解析我的 vaadin 7 项目。每当我尝试时,它都会显示一个错误框,上面写着
'IvyDE resolve' has encountered a problem. Some project fails to be resolved.
单击错误框上的“详细信息”按钮后,我得到了以下附加信息
Some projects fail to be resolved Impossible to resolve dependencies of com.example#v7proj;working@User unresolved dependency: com.vaadin#vaadin-client-compiled;7.6.2: not found unresolved dependency: com.vaadin#vaadin-themes;7.6.2: not found unresolved dependency: com.vaadin#vaadin-push;7.6.2: not found unresolved dependency: com.vaadin#vaadin-server;7.6.2: not found unresolved dependency: com.vaadin#vaadin-client-compiler;7.6.2: not found unresolved dependency: com.vaadin#vaadin-client;7.6.2: not found unresolved dependency: javax.servlet#javax.servlet-api;3.0.1: not found
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
最佳答案
这是 Ivy 中的问题,它默认使用旧的 TLS 1.0 版本,maven central 不再支持它。您需要重新配置它。您可以从 Vaadin Forum 中找到更多信息。和另一个 StackOverflow 问题 Why am I getting "Received fatal alert: protocol_version" or "peer not authenticated" from Maven Central?
关于java - 无法解决 Vaadin 7.6.2 与 Ivy 的依赖关系,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/56714858/
下面的说法正确吗? “人最好的 friend 是狗。” public class Mann { private BestFriend dog; //etc } 最佳答案 我想说这样
我一直在 documentation 中查看 Laravel 4 中的关系我正在尝试解决以下问题。 我的数据库中有一个名为“事件”的表。该表具有各种字段,主要包含与其他表相关的 ID。例如,我有一个“
我的表具有如下关系: 我有相互链接的级联下拉框,即当您选择国家/地区时,该国家/地区下的区域将加载到区域下拉列表中。但现在我想将下拉菜单更改为基于 Ajax 的自动完成文本框。 我的问题是,我应该有多
我正在尝试弄清楚如何构建这个数据库。我之前用过Apple的核心数据就好了,现在我只是在做一个需要MySQL的不同项目。我是 MySQL 的新手,所以请放轻松。 :) 对于这个例子,假设我有三个表,Us
MongoDB 的关系表示多个文档之间在逻辑上的相互联系。 文档间可以通过嵌入和引用来建立联系。 MongoDB 中的关系可以是: 1:1 (1对1) 1: N (1对多)
您能解释一下 SQL 中“范围”和“分配单元”之间的区别或关系吗? 最佳答案 分配单元基本上只是一组页面。它可以很小(一页)或很大(很多页)。它在 sys.allocation_units 中有一个元
我有一个表 geoLocations,其中包含两列纬度和经度。还有第二个表(让我们将其命名为城市),其中包含每对唯一的纬度和经度对应的城市。 如何使用 PowerPivot 为这种关系建模?创建两个单
我想用 SQLDelight 建模关系,尤其是 一对多关系。 我有 2 张 table :recipe和 ingredient .为简单起见,它们看起来像这样: CREATE TABLE recipe
我是 Neo4J 新手,我有一个带有源和目标 IP 的简单 CSV。我想在具有相同标签的节点之间创建关系。 类似于... source_ip >> ALERTS >> dest_ip,或者相反。 "d
我正在创建一个类图,但我想知道下面显示的两个类之间是否会有任何关联 - 据我了解,对于关联,ClassA 必须有一个 ClassB 的实例,在这种情况下没有但是,它确实需要知道 ClassB 的一个变
是否可以显示其他属性,即“hasTopping”等? 如何在 OWLViz 中做到这一点? 最佳答案 OWLViz 仅 显示类层次结构(断言和推断的类层次结构)。仅使用“is-a”关系进行描述。 OW
public class MainClass { ArrayList mans = new ArrayList(); // I'm filling in this arraylist,
我想知道“多对二”的关系。 child 可以与两个 parent 中的任何一个联系,但不能同时与两个 parent 联系。有什么办法可以加强这一点吗?我也想防止 child 重复条目。 一个真实的例子
我有一个已经创建的Grails插件,旨在支持许多应用程序。该插件具有一个Employee域对象。问题在于,当在主应用程序中使用该应用程序中的域对象时,需要将其引用回Employee对象。因此,我的主应
我有一个类(class)表、类(class)hasMany部分和部分hasMany讲座以及讲座hasMany评论。如果我有评论 ID 并且想知道其类(class)名称,我应该如何在 LectureCo
我有一个模型团队,包含 ID 和名称。所有可能的团队都会被存储。 我的模型游戏有两列 team_1 和 team_2..我需要哪种关系? 我已经测试了很多,但它只适用于一列.. 最佳答案 也许你可以试
我读了很多关于 ICE 或 Corba 等技术中使用的仆人和对象的文章。有很多资源我可以读到这样的东西: 一个仆人可以处理多个对象(为了节省资源)。 一个对象可以由多个仆人处理(为了可靠性)。 有人可
嗨, 我有一个令人沮丧的问题,我在这方面有点生疏。我有两个这样的类(class): class A{ int i; String j ; //Getters and setters} class B
class Employee { private String name; void setName(String n) { name = n; } String getNam
如果您有这样的关系: 员工与其主管员工之间存在多对一关系 员工与其部门的多对一关系 部门与其经理一对一 我会在 Employee 实体中写入: @ManyToOne (cascade=CascadeT
我是一名优秀的程序员,十分优秀!