从 GMaven 运行脚本会导致"No such property: project"异常

Question

tl; dr：使用gmaven从maven内部运行groovy脚本时，如何解决" No such property: project"错误？我正在使用Gmaven 1.5，Groovy 2.2.1。和Java 1.7和Maven 3.1.0。

---

我有一个Groovy脚本-DeltaCodeGen（它没有包） - 生成Java代码（对于Java项目，这是该项目中唯一的Groovy）。过去，我们将使脚本生成.java文件，这些文件将被签入，但是现在我们试图在generate-sources阶段的Maven构建过程中构建它们。

我可以从我的IDE成功运行脚本，但是当我尝试运行它作为构建的一部分时，我会得到

Caused by: org.codehaus.groovy.runtime.metaclass.MissingPropertyExceptionNoStack: No such property: project for class: DeltaCodeGen

尽管有其他答案，但我的脚本没有一个称为project的变量，也没有包含字符串"项目"。它不会扩展任何其他脚本。它使用的唯一库是反思（Servlet API的需求仍然是一个开放的问题）。

运行构建，我在stderr（通过运行mvn -X 2>mvn_err.log）中注意到以下错误：

java.lang.NoSuchMethodError: org.codehaus.groovy.runtime.InvokerHelper.getVersion()Ljava/lang/String;
    at org.codehaus.gmaven.runtime.v1_6.ProviderImpl.name(ProviderImpl.java:70)
    at org.codehaus.gmaven.feature.support.ProviderSupport.asString(ProviderSupport.java:175)
    at org.codehaus.gmaven.feature.support.ProviderSupport.toString(ProviderSupport.java:68)
    at org.slf4j.helpers.MessageFormatter.safeObjectAppend(MessageFormatter.java:304)
    at org.slf4j.helpers.MessageFormatter.deeplyAppendParameter(MessageFormatter.java:276)
    at org.slf4j.helpers.MessageFormatter.arrayFormat(MessageFormatter.java:230)
    at org.slf4j.helpers.MessageFormatter.format(MessageFormatter.java:152)
    at org.slf4j.impl.SimpleLogger.formatAndLog(SimpleLogger.java:414)
    at org.slf4j.impl.SimpleLogger.debug(SimpleLogger.java:512)
    at org.codehaus.gmaven.runtime.loader.DefaultProviderSelector.register(DefaultProviderSelector.java:135)
    at org.codehaus.gmaven.runtime.loader.DefaultProviderSelector.select(DefaultProviderSelector.java:72)
    at org.codehaus.gmaven.runtime.loader.DefaultProviderManager.select(DefaultProviderManager.java:102)
    at org.codehaus.gmaven.plugin.ProviderMojoSupport.provider(ProviderMojoSupport.java:120)
    at org.codehaus.gmaven.plugin.ComponentMojoSupport.feature(ComponentMojoSupport.java:49)
    at org.codehaus.gmaven.plugin.ComponentMojoSupport.feature(ComponentMojoSupport.java:42)
    at org.codehaus.gmaven.plugin.ComponentMojoSupport.doExecute(ComponentMojoSupport.java:53)
    at org.codehaus.gmaven.plugin.MojoSupport.execute(MojoSupport.java:71)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:318)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)

---

我的Maven配置是：

<build>
    <plugins>
        <plugin>
            <!-- see: http://docs.codehaus.org/display/GMAVEN/Executing+Groovy+Code#ExecutingGroovyCode-ExecuteaLocalGroovyScript -->
            <groupId>org.codehaus.gmaven</groupId>
            <artifactId>gmaven-plugin</artifactId>
            <version>1.5</version>
            <executions>
                <execution>
                    <phase>generate-sources</phase>
                    <goals>
                        <goal>execute</goal>
                    </goals>
                    <configuration>
                        <source>${pom.basedir}/src/main/groovy/DeltaCodeGen.groovy</source>
                    </configuration>
                </execution>
            </executions>
                <dependencies>
                    <dependency>
                        <groupId>org.reflections</groupId>
                        <artifactId>reflections</artifactId>
                        <version>0.9.9-RC1</version>
                    </dependency>
                    <dependency>
                        <groupId>org.codehaus.groovy</groupId>
                        <artifactId>groovy-all</artifactId>
                        <version>2.2.1</version>
                    </dependency>
                    <dependency>
                        <groupId>javax.servlet</groupId>
                        <artifactId>javax.servlet-api</artifactId>
                        <version>3.1.0</version>
                    </dependency>
            </dependencies>
        </plugin>
    </plugins>
</build>

Answer 1

我最终要上班的是用gmavenplus替换gmaven（目前已维护）。

由于目前未在本地脚本作为示例提供本地脚本，因此这是我的POM中对我有用的原因：

<plugin>
    <groupId>org.codehaus.gmavenplus</groupId>
    <artifactId>gmavenplus-plugin</artifactId>
    <version>1.0</version>
    <executions>
        <execution>
            <phase>generate-sources</phase>
            <goals>
                <goal>execute</goal>
            </goals>
            <configuration>
                <scripts>
                    <script>file:/${pom.basedir}/src/main/groovy/DeltaCodeGen.groovy</script>
                </scripts>
            </configuration>
        </execution>
    </executions>
    <dependencies>
        <dependency>
            <groupId>org.codehaus.groovy</groupId>
            <artifactId>groovy-all</artifactId>
            <version>2.2.1</version>
        </dependency>
    </dependencies>
</plugin>

Answer 2

这是黑暗中的狂野刺伤，但是您是否试图将Maven" Project"属性绑定到脚本上？在您最初的问题中，有人通过使用插值提出了这一点：

def project = ${project}

，但这仅适用于内联脚本。在您的情况下，我会尝试

        <executions>
            <execution>
                <phase>generate-sources</phase>
                <goals>
                    <goal>execute</goal>
                </goals>
                <configuration>
                    <source>${pom.basedir}/src/main/groovy/DeltaCodeGen.groovy</source>
                    <properties>
                        <project>${project}</project>
                    </properties>
                </configuration>
            </execution>
        </executions>

然后，您可能可以将其放入实际的时髦代码中：project = properties ['project']

我猜测，脚本跑步者正在寻找脚本的项目成员，当然，CMD行执行不是。因此，我要定义或胁迫价值。