使用gmaven插件获取org.codehaus.groovy.control.MultipleCompilationE

Question

这是我的示例程序，而使用mvn编译它抛出我的编译错误，我试图添加一个静态方法使用ExpandoMetaClass -

@Singleton
        class ThrowError {
            def parse ()
            {
                println "Anish"
            }
        }
        ThrowError.metaClass.static.getMap = {m_var -> ThrowError.instance.parse(m_var) }

我正在使用gmaven插件来编译项目，同时发布MVN编译..........

[ERROR] Failed to execute goal org.codehaus.gmaven:gmaven-plugin:1.2:generateStubs (default) on project TestExpandoMetaClass: startup failed:
[ERROR] /C:/groovy/ThrowError.groovy: 4
: Invalid duplicate class definition of class ThrowError : The source /C:/groovy/ThrowError.groovy contains at least two definitions of the class ThrowError.
**[ERROR] One of the classes is a explicit generated class using the class statement, the other is a class generated from the s
cript body based on the file name. Solutions are to change the file name or to change the class name.**
[ERROR] @ line 4, column 1.
[ERROR] @Singleton
[ERROR] ^
[ERROR]
[ERROR] 1 error
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.gmaven:gmaven-plugin:1.2:generate
Stubs (default) on project TestExpandoMetaClass: startup failed:
/C:/groovyThrowError.groovy: 4: Invali
d duplicate class definition of class ThrowError : The source /groovy/ThrowError.groovy contains at least two definitions of the class ThrowError

这是我的pom.xml条目gmaven构建插件条目

    <project>
............
............
    <build>
            <plugins>
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-compiler-plugin</artifactId>
                    <configuration>
                        <source>1.6</source>
                        <target>1.6</target>
                    </configuration>
                </plugin>
                <plugin>
                    <groupId>org.codehaus.mojo</groupId>
                    <artifactId>exec-maven-plugin</artifactId>
                    <version>1.1</version>
                    <executions>
                        <execution>
                            <goals>
                                <goal>java</goal>
                            </goals>
                        </execution>
                    </executions>
                </plugin>
                <plugin>
                    <groupId>org.codehaus.gmaven</groupId>
                    <artifactId>gmaven-plugin</artifactId>
                    <version>1.2</version>
                    <configuration>
                        <providerSelection>1.7</providerSelection>
                    </configuration>
                    <dependencies>
                        <dependency>
                            <groupId>org.codehaus.gmaven.runtime</groupId>
                            <artifactId>gmaven-runtime-1.7</artifactId>
                            <version>1.2</version>
                        </dependency>
                        <dependency>
                            <groupId>org.codehaus.groovy</groupId>
                            <artifactId>groovy-all</artifactId>
                            <version>1.7.2</version>
                        </dependency>
                    </dependencies>
                    <executions>
                        <execution>
                            <goals>
                                <goal>generateStubs</goal>
                                <goal>compile</goal>
                                <goal>generateTestStubs</goal>
                                <goal>testCompile</goal>
                            </goals>
                        </execution>
                    </executions>
                </plugin>
            </plugins>
        </build>
..........
..........
    </project>

Answer 1

这里的答案与Groovy邮件列表中的答案相同，可能会有更多的解释…在Groovy中我们有脚本和类。类是具有类结构的一切，就像在Java中一样。例如，类B{}是一个类结构并定义了一个类B。脚本也是类，但它们不在这样的结构中。如果你现在有"类B{};def b = new b()"，您有b的类结构，但也有内容为"def b = new b()"的脚本。我说过这也是一个类，但是这个类叫什么名字呢?名称由定义该脚本的文件名定义(如果没有文件，则选择script1456之类的名称)。现在您可以创建一个B.groovy，其内容为"类B{};def b = new b()"。会有一个名为B的类和一个同名的脚本。这是一种冲突。