无法增强数据核心

将我的gradle更新为1.0.1后，我的appengine构建失败

我收到错误：

groovy.lang.MissingPropertyException: Could not find property 'enhancerApi' on com.google.appengine.AppEnginePluginExtension_Decorated@1dd443c1

看起来 enhacerApi 已被弃用，但我不知道如何解决这个问题 .

App Engine SDK root = C：\ Users \ steve.gradle \ appengine-sdk \ appengine-java-sdk-1.9.17 Java classpath = C：\ workspace \ ShoutBox \ gradle \ wrapper \ gradle-wrapper.jar; C： \ Users \ steve.gradle \ appengine-sdk \ appengine-java-sdk-1.9.17 \ lib \ appengine-tools-api.jar Webapp源目录= C：\ workspace \ ShoutBox \ appengine \ src \ main \ webapp增强DataNucleus classes ...完成了增强DataNucleus类 . ：appengine：appengineEnhance FAILED：appengine：appengineEnhance（Thread [main，5，main]）完成 . 花了1.043秒 . FAILURE：构建因异常而失败 . 出了什么问题：任务'执行失败'：appengine：appengineEnhance' . 增强DataNucleus类时出错 . 尝试：使用--debug选项运行以获取更多日志输出 . 例外情况是：org.gradle.api.tasks.TaskExecutionException：任务'：appengine：appengineEnhance'的执行失败 . 在org.gradle上的org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions（ExecuteActionsTaskExecuter.java:69）org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute（ExecuteActionsTaskExecuter.java:46）位于org.gradle.api.internal的org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute（SkipUpToDateTaskExecuter.java:64）上的.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute（PostExecutionAnalysisTaskExecuter.java:35）位于org.gradle.api.internal.tasks.execution的org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute（SkipEmptySourceFilesTaskExecuter.java:42）.tasks.execution.ValidatingTaskExecuter.execute（ValidatingTaskExecuter.java:58） .skipTaskWithNoActionsExecuter.execute（SkipTaskWithNoActionsExecuter.java:52）org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute（SkipOnlyIfTaskExecuter.java:53）at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecu at.exe.gradle.api.internal.AbstractTask.executeWithoutThrowingTaskFailure（AbstractTask.java:305）中的ter.execute（ExecuteAtMostOnceTaskExecuter.java:43）org.gradle.execution.taskgraph.AbstractTaskPlanExecutor $ TaskExecutorWorker.executeTask（AbstractTaskPlanExecutor.java:79） at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor $ TaskExecutorWorker.processTask（AbstractTaskPlanExecutor.java:63）org.gradle.execution.taskgraph.AbstractTaskPlanExecutor $ TaskExecutorWorker.run（AbstractTaskPlanExecutor.java:51）at org.gradle.execution.taskgraph .defaultTaskPlanExecutor.process（DefaultTaskPlanExecutor.java:23）org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute（DefaultTaskGraphExecuter.java:88）org.gradle.execution.SelectedTaskExecutionAction.execute（SelectedTaskExecutionAction.java:29）at org . grag.exe.exe.DefaultBuildExecuter.execute（DefaultBuildExecuter.java:62）org.gradle.execution.DefaultBuildExecuter.access $ 200（DefaultBuildExecuter.java:23）org.gradle.executio n.DefaultBuildExecuter $ 2.proceed（DefaultBuildExecuter.java:68）org.gradle.execution.DryRunBuildExecutionAction.execute（DryRunBuildExecutionAction.java:32）org.gradle.execution.DefaultBuildExecuter.execute（DefaultBuildExecuter.java:62）at org . grag.exe.exe.DefaultBuildExecuter.execute（DefaultBuildExecuter.java:55）org.gradle.initialization.DefaultGradleLauncher.doBuildStages（DefaultGradleLauncher.java:149）org.gradle.initialization.DefaultGradleLauncher.doBuild（DefaultGradleLauncher.java:106）at org .gradle.initialization.DefaultGradleLauncher.run（DefaultGradleLauncher.java:86）org.gradle.launcher.exec.InProcessBuildActionExecuter $ DefaultBuildController.run（InProcessBuildActionExecuter.java:80）at org.gradle.launcher.cli.ExecuteBuildAction.run（ExecuteBuildAction） .java：33）org.gradle.launcher.cli.ExecuteBuildAction.run（ExecuteBuildAction.java:24）org.gradle.launcher.exec.InProcessBuildActionExecuter.execute（InProcessBuildActionExecuter.java:36）atg.gradle.launche位于org.gradle.internal.Actions的org.gradle.launcher.cli.RunBuildAction.run（RunBuildAction.java:51）中的r.exec.InProcessBuildActionExecuter.execute（InProcessBuildActionExecuter.java:26）$ RunnableActionAdapter.execute（Actions.java： 171）在org.gradle.launcher.cli.CommandLineActionFactory $ ParseAndBuildAction.execute（CommandLineActionFactory.java:237）at atorg.gradle.launcher.cli.CommandLineActionFactory $ ParseAndBuildAction.execute（CommandLineActionFactory.java:210）位于org.gradle.launcher.cli.JavaRuntimeValidationAction的org.gradle.launcher.cli.JavaRuntimeValidationAction.execute（JavaRuntimeValidationAction.java:35） . 执行（JavaRuntimeValidationAction.java:24）在org.gradle.launcher.cli.CommandLineActionFactory $ WithLogging.execute（CommandLineActionFactory.java:206）在org.gradle.launcher.cli.CommandLineActionFactory $ WithLogging.execute（CommandLineActionFactory.java:169）在org.gradle.launcher.cli.ExceptionReportingAction.execute（ExceptionReportingAction.java:33）在org.gradle.launcher.cli.ExceptionReportingAction.execute（ExceptionReportingAction.java:22）在org.gradle.launcher.Main.doAction（主.java：33）在org.gradle.launcher的org.gradle.launcher.bootstrap.EntryPoint.run（EntryPoint.java:45）org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit（ProcessBootstrap.java:54） . bootstrap.ProcessBootstrap.run（ProcessBootstrap.java:35）a org.gradle.launcher.GradleMain.main（GradleMain.java:23）org.gradle.wrapper.BootstrapMainStarter.start（BootstrapMainStarter.java:33）at org.gradle.wrapper.WrapperExecutor.execute（WrapperExecutor.java:130） ）org.gradle.wrapper.GradleWrapperMain.main（GradleWrapperMain.java:48）引起：org.gradle.api.GradleException：增强DataNucleus类时发生错误 . com.google.appengine.task.EnhanceTask.enhanceClasses（EnhanceTask.groovy：58）at com.google.appengine.task.EnhanceTask.executeTask（EnhanceTask.groovy：34）at com.google.appengine.task.AbstractTask.start （AbstractTask.groovy：38）在org.gradle.internal.reflect.JavaMethod.invoke（JavaMethod.java:63）在org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory $ StandardTaskAction.doExecute（AnnotationProcessingTaskFactory.java:218 ）org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory $ StandardTaskAction.execute（AnnotationProcessingTaskFactory.java:211）at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory $ StandardTaskAction.execute（AnnotationProcessingTaskFactory.java:200） ）org.gradle.api.internal.AbstractTask $ TaskActionWrapper.execute（AbstractTask.java:579）位于org.gradle.api的org.gradle.api.internal.AbstractTask $ TaskActionWrapper.execute（AbstractTask.java:562） . internal.tasks.execution.ExecuteActionsTaskExecuter.executeAct离子（ExecuteActionsTaskExecuter.java:80）at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions（ExecuteActionsTaskExecuter.java:61）... 47更多引起：groovy.lang.MissingPropertyException：找不到属性'关于com.google.appengine.AppEnginePluginExtension_Decorated@1dd443c1的enhancerApi' . 在org.gradle.api.internal.AbstractDynamicObject.propertyMissingException（AbstractDynamicObject.java:43）在org.gradle.api.internal.AbstractDynamicObject.getProperty（AbstractDynamicObject.java:35）在org.gradle.api.internal.CompositeDynamicObject.getProperty （CompositeDynamicObject.java:94）在com.google.appengine.AppEnginePluginExtension_Decorated.getProperty（来源不明）在com.google.appengine.AppEnginePlugin $ _configureEnhance_closure9_closure58.doCall（AppEnginePlugin.groovy：313）在com.google.appengine.AppEnginePlugin $ _configureEnhance_closure9_closure58 .doCall（AppEnginePlugin.groovy）org.gradle.api.internal.ConventionAwareHelper $ 2.getValue（ConventionAwareHelper.java:84）org.gradle.api.internal.ConventionAwareHelper $ MappedPropertyImpl.getValue（ConventionAwareHelper.java:136）at org .gradle.api.internal.ConventionAwareHelper.getConventionValue（ConventionAwareHelper.java:114）位于com.google.appeng的com.google.appengine.task.EnhanceTask_Decorated.getEnhancerApi（未知来源） ine.task.EnhanceTask $ _enhanceClasses_closure1.doCall（EnhanceTask.groovy：52）在com.google.appengine.task.EnhanceTask $ _enhanceClasses_closure1.doCall（EnhanceTask.groovy）在org.gradle.api.internal.project.ant.BasicAntBuilder . com.google.appengine.task.EnhanceTask.enhanceClasses（EnhanceTask.groovy：42）中的doInvokeMethod（BasicAntBuilder.java:92）... 57更多BUILD FAILED总时间：19.158秒已停止0编译器守护程序 .