Phillip
September 16, 2016, 8:36am
1
Hi
Could not resolve archetype com.vaadin:vaadin-archetype-application:7.7.1 from any of the configured repositories.https://repo.maven.apache.org/maven2 ): connect timed outhttps://repo.maven.apache.org/maven2 ): connect timed out
alejandro.du
September 16, 2016, 1:43pm
2
What do you get when you try the following in a terminal?
(use the
Phillip
September 16, 2016, 2:09pm
3
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.4/maven-install-plugin-2.4.pom https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-deploy-plugin/2.7/maven-deploy-plugin-2.7.pom https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-site-plugin/3.3/maven-site-plugin-3.3.pom https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-antrun-plugin/1.3/maven-antrun-plugin-1.3.pom https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-assembly-plugin/2.2-beta-5/maven-assembly-plugin-2.2-beta-5.pom https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-dependency-plugin/2.8/maven-dependency-plugin-2.8.pom https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.3.2/maven-release-plugin-2.3.2.pom https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml https://repo.maven.apache.org/maven2 ): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.60.215 ]https://repo.maven.apache.org/maven2 ): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.60.215 ]https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.apache.maven.plugins/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2 ): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.60.215 ]https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (https://repo.maven.apache.org/maven2 ): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.60.215 ][ERROR]https://repo.maven.apache.org/maven2 )]
[ERROR]
[ERROR]
[ERROR]http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
P:>
Vesa
September 17, 2016, 6:55am
4
Hi
Now WidgetSetBuilder throws exception
[ERROR]
Exception in thread "main" java.lang.IllegalArgumentException: URI has an authority component
[ERROR]
at java.io.File.<init>(File.java:423)
[ERROR]
at com.vaadin.server.widgetsetutils.WidgetSetBuilder.updateWidgetSet(WidgetSetBuilder.java:74)
[ERROR]
at com.vaadin.server.widgetsetutils.WidgetSetBuilder.main(WidgetSetBuilder.java:54)
I dig a little and what I can see is that previously path to gwt xml was handled as String in WidgetSetBuilder
72 String wsFullPath = sourceUrl.getFile() + "/" + widgetsetFileName;
73
74 File widgetsetFile = new File(wsFullPath);
75 if (!widgetsetFile.exists()) {
Now it use URI.
63 Map<String, URL> availableWidgetSets = ClassPathExplorer
64 .getAvailableWidgetSets();
65
66 String widgetsetFileName = widgetset.replace(".", "/") + ".gwt.xml";
67 URL sourceUrl = availableWidgetSets.get(widgetset);
68 if (sourceUrl == null) {
69 // find first/default source directory
70 sourceUrl = ClassPathExplorer
71 .getWidgetsetSourceDirectory(widgetsetFileName);
72 }
73
74 File widgetsetFile = new File(new File(sourceUrl.toURI()),
75 widgetsetFileName);
Changes seems to be linked on to issue
Roland38
September 17, 2016, 9:13am
5
I have the same problem, if I change from vaadin 7.7.0 to 7.7.1 …
Reto5
September 17, 2016, 11:03am
6
I also have the same problem. I’m using Eclipse Neon. I can’t update my project to Vaadin 7.7.1, but I’m also not able to create a new example project with this version. It does not matter if I use eclipse or mvn on the command line.
Should this version even work?
Ingo4
September 17, 2016, 1:42pm
7
7.7.1 broke widget set compilation on Windows. The fix is already in the 7.7 branch:
I hope they release 7.7.2 really soon.