java - Hudson 2.0.1 和 Maven 2.2.1 找不到符号错误

Question

在做一些研究后，我发现了这个 Old Post带有指向 Hudson 问题跟踪器站点的链接，其中包含关于几乎相同问题的一些信息，该问题声称已针对我正在使用的当前版本的 Hudson 2.0.1 和 Maven 2.2.1 进行了修复。

似乎当我尝试在 Hudson 上运行我的测试时，我得到一个“找不到符号错误”，它在 eclipse 中运行良好，这让我认为它可能与 Hudson 和 Maven 有关，但我不确定.

这是我的堆栈跟踪，其中包含我认为(在阅读上一篇文章之后)相关或以某种方式相关的部分

[WARNING] 
************ WARNING ************

This Maven runtime contains a LifecycleExecutor component with an incomplete configuration.

LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement: org.apache.maven.project.MavenProjectBuilder

NOTE: This seems to be a third-party Maven derivative you are using. If so, please
notify the developers for this derivative project of the problem. The Apache Maven team is not
responsible for maintaining the integrity of third-party component overrides.


[WARNING] 
************ WARNING ************

This Maven runtime contains a LifecycleExecutor component with an incomplete configuration.

LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement: org.apache.maven.project.interpolation.ModelInterpolator

NOTE: This seems to be a third-party Maven derivative you are using. If so, please
notify the developers for this derivative project of the problem. The Apache Maven team is not
responsible for maintaining the integrity of third-party component overrides.


[WARNING] 
************ WARNING ************

This Maven runtime contains a LifecycleExecutor component with an incomplete configuration.

LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor
Missing component requirement: org.apache.maven.ConfigurationInterpolator

NOTE: This seems to be a third-party Maven derivative you are using. If so, please
notify the developers for this derivative project of the problem. The Apache Maven team is not
responsible for maintaining the integrity of third-party component overrides.


[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Lonely Planet Code Test
[INFO]    task-segment: [clean, install]
[INFO] ------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set: /var/lib/hudson/jobs/Lonely Planet Coding Tests/workspace/trunk/com.lonelyplanet.codetest.wkallan/target (included: [**], excluded: [])
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 1 source file to /var/lib/hudson/jobs/Lonely Planet Coding Tests/workspace/trunk/com.lonelyplanet.codetest.wkallan/target/classes
[HUDSON] Archiving /var/lib/hudson/jobs/Lonely Planet Coding Tests/workspace/trunk/com.lonelyplanet.codetest.wkallan/pom.xml to /var/lib/hudson/jobs/Lonely Planet Coding Tests/modules/com.lonelyplanet.codetest.wkallan$com.lonelyplanet.codetest.wkallan/builds/2011-06-30_13-40-15/archive/com.lonelyplanet.codetest.wkallan/com.lonelyplanet.codetest.wkallan/0.0.1-SNAPSHOT/pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
/var/lib/hudson/jobs/Lonely Planet Coding Tests/workspace/trunk/com.lonelyplanet.codetest.wkallan/src/main/java/com/lonelyplanet/codetest/wkallan/ContentGenerator.java:[30,15] cannot find symbol
symbol  : method format(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String)
location: class java.lang.String

Answer 1

说真的，我支持丹尼尔的建议。搬到 Jenkins 。自从与 Oracle 分离后，几乎所有 Hudson 开发人员都已转移到 Jenkins，并且不再支持或以旧名称开发 Hudson。 我已将我们的 Hudson 迁移到 Jenkins。迁移通常是无缝的。 使用 Jenkins 的好处是他们每周(基于迭代)发布版本，而且他们往往比 Oracle 修复很多更多的东西。

我并不是想在这里挑起一场口水战，这只是我个人的看法。只是建议。 :-)