从Vaadin 7 8升级后构建失败 [英] Build fails after upgrading from Vaadin 7 8

查看:119
本文介绍了从Vaadin 7 8升级后构建失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我刚从Vaadin 7升级到8.我们使用的是7.7.7,现在使用的是8.0.3.我的IDE没有显示编译时错误,但是当我运行mvn软件包时,看到以下错误.

I just upgraded from Vaadin 7 to 8. We were on 7.7.7 and now we are on 8.0.3. My IDE shows no compile time errors but when I run mvn package I see the following error..

[INFO] --- vaadin-maven-plugin:8.0.3:compile (default) @ eagleportal ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 25.728 s
[INFO] Finished at: 2017-03-22T18:19:55-06:00
[INFO] Final Memory: 22M/142M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.vaadin:vaadin-maven-plugin:8.0.3:compile (default) on project eagleportal: GWT Module com.vaadin.terminal.gwt.DefaultWidgetSet not found in project sources or resources. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

我的Vaadin编译器的maven配置如下所示

My maven config for the Vaadin compiler looks like this

    <plugin>
        <groupId>com.vaadin</groupId>
        <artifactId>vaadin-maven-plugin</artifactId>
        <version>${vaadin.plugin.version}</version>
        <configuration>
            <extraJvmArgs>-Xmx512M -Xss1024k</extraJvmArgs>
            <!-- <runTarget>mobilemail</runTarget> -->
            <!-- We are doing "inplace" but into subdir VAADIN/widgetsets. This
                way compatible with Vaadin eclipse plugin. -->
            <webappDirectory>${basedir}/src/main/webapp/VAADIN/widgetsets</webappDirectory>
            <hostedWebapp>${basedir}/src/main/webapp/VAADIN/widgetsets</hostedWebapp>
            <noServer>true</noServer>
            <!-- Remove draftCompile when project is ready -->
            <draftCompile>false</draftCompile>
            <compileReport>true</compileReport>
            <style>OBF</style>
            <runTarget>http://localhost:8080/</runTarget>
            <warSourceDirectory>${basedir}/src/main/webapp</warSourceDirectory>
        </configuration>
        <executions>
            <execution>
                <configuration>
                    <modules>
                        <module>com.eaglecopter.portal.EaglePortal</module>
                        <module>com.eaglecopter.portal.EaglePortalMobile</module>
                    </modules>
                </configuration>
                <phase>generate-resources</phase>
                <goals>
                    <goal>clean</goal>
                    <goal>resources</goal>
                    <goal>update-theme</goal>
                    <goal>update-widgetset</goal>
                    <goal>compile-theme</goal>
                    <goal>compile</goal>
                </goals>
            </execution>
        </executions>
    </plugin>

推荐答案

您使用的应用程序小部件集或某些附加组件仍指向V6时代 com.vaadin.terminal.gwt.DefaultWidgetSet .如果re是您的应用程序.gwt.xml文件中的直接引用,则将其切换为 com.vaadin.DefaultWidgetSet .

Your application widgetset or some add-on that you are using is still pointing to V6 era com.vaadin.terminal.gwt.DefaultWidgetSet. If the re is a direct reference to that in your applications .gwt.xml files, switch that to com.vaadin.DefaultWidgetSet.

如果有尝试将其引入的附加组件,请将其升级到Vaadin 8兼容版本.如果还没有兼容V8的版本,我需要帮助维护人员升级或尝试在没有附加组件的情况下进行管理.

If there are some add-ons that try to bring it in, upgrade those to Vaadin 8 compatible versions. If no V8 compatible version is out yet, I'll need to help the maintainer to upgrade or try to manage without the add-on.

这篇关于从Vaadin 7 8升级后构建失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆