I'm seeing a very strange compilation problem:
Somehow LuceneIterableTest tries to extend
org.apache.mahout.math.MahoutTestCase which does not exist, but it
correctly imports org.apache.mahout.common.MahoutTestCase...
mvn -e -DskipTests=true clean install
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Compilation failure
/home/ssc/Entwicklung/workspaces/asf/mahout/utils/src/test/java/org/apache/mahout/utils/vectors/lucene/LuceneIterableTest.java:[36,7]
cannot access org.apache.mahout.math.MahoutTestCase
class file for org.apache.mahout.math.MahoutTestCase not found
public class LuceneIterableTest extends MahoutTestCase {
/home/ssc/Entwicklung/workspaces/asf/mahout/utils/src/test/java/org/apache/mahout/utils/vectors/lucene/LuceneIterableTest.java:[50,4]
cannot find symbol
symbol : variable super
location: class org.apache.mahout.utils.vectors.lucene.LuceneIterableTest
/home/ssc/Entwicklung/workspaces/asf/mahout/utils/src/test/java/org/apache/mahout/utils/vectors/lucene/LuceneIterableTest.java:[48,2]
method does not override or implement a method from a supertype
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: Compilation failure
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.CompilationFailureException:
Compilation failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at
org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:102)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Am 07.05.2010 17:22, schrieb Sean Owen:
> To be honest I am also having the same issues, and I do not understand
> how. My build fails in utils/ with *no* error message. While it seems
> like it must be related to my last set of changes, I don't see how so,
> since these are Maven-level dependency problems.
>
> Is anyone else seeing any such thing? I am also stumped.
>
> On Fri, May 7, 2010 at 4:18 PM, Saul Moncada <[email protected]> wrote:
>
>> At step five I got this compilation errors in utils:
>>
