![]() ![]() For more information about the errors and possible solutions, please read the following articles:īeta Was this translation helpful? Give feedback. Re-run Maven using the -X switch to enable full debug logging. To see the full stack trace of the errors, re-run Maven with the -e switch. Cannot resolve dependencies of MavenProject: ::1.0.129-SNAPSHOT /Users/qianlei/workSpace/me/dbeaver/plugins//pom.xml: See log for details - > Missing requirement: 1.0.129.qualifier requires 'osgi.bundle 0.0.0 ' but it could not be found Software being installed: 1.0.129.qualifier Resolving dependencies of MavenProject: ::1.0.129-SNAPSHOT /Users/qianlei/workSpace/me/dbeaver/plugins//pom.xml Computing target platform for MavenProject: ::1.0.129-SNAPSHOT /Users/qianlei/workSpace/me/dbeaver/plugins//pom.xml Resolving class path of MavenProject: ::2.0.133-SNAPSHOT /Users/qianlei/workSpace/me/dbeaver/bundles//pom.xml Resolving dependencies of MavenProject: ::2.0.133-SNAPSHOT /Users/qianlei/workSpace/me/dbeaver/bundles//pom.xml Computing target platform for MavenProject: ::2.0.133-SNAPSHOT /Users/qianlei/workSpace/me/dbeaver/bundles//pom.xml With a bit of luck when DBeaver 5.3.2 is released is a 'nothing' problem. ![]() I have to restart DBeaver after been connected with the old before I connect with the new. If I have one connection of each type in the same DBeaver project they don't live to happily. Resolving class path of MavenProject: ::2.1.123-SNAPSHOT /Users/qianlei/workSpace/me/dbeaver/bundles//pom.xml I think the new and the old Microsoft driver collide in some way. Resolving dependencies of MavenProject: ::2.1.123-SNAPSHOT /Users/qianlei/workSpace/me/dbeaver/bundles//pom.xml Computing target platform for MavenProject: ::2.1.123-SNAPSHOT /Users/qianlei/workSpace/me/dbeaver/bundles//pom.xml ~/workSpace/me/dbeaver(devel) » mvn package 1 ↵ Scanning for projects. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |