qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rafael Schloming <rafa...@redhat.com>
Subject Re: Qpid java trunk build break
Date Thu, 24 Apr 2008 17:15:33 GMT
Try using the ant build. The maven one is going to be removed soon.

--Rafael

Suran Jayathilaka wrote:
> Thanks.
> 
> Still having problems with the build though.
> 
> [INFO] 
> ---------------------------------------------------------------------------- 
> 
> [INFO] Building Qpid Integration Tests
> [INFO]    task-segment: [install]
> [INFO] 
> ---------------------------------------------------------------------------- 
> 
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> Compiling 12 source files to 
> /home/suran/projects/qpid/java/integrationtests/target/classes
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Compilation failure
> 
> /home/suran/projects/qpid/java/integrationtests/src/main/java/org/apache/qpid/interop/clienttestcases/TestCase5PubSubMessageSize.java:[141,37]

> cannot access uk.co.thebadgerset.junit.extensions.util.ParsedProperties
> file uk/co/thebadgerset/junit/extensions/util/ParsedProperties.class not 
> found
>            connection[0] = 
> TestUtils.createConnection(TestClient.testContextProperties);
> 
> 
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.BuildFailureException: Compilation failure
>    at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)

> 
>    at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)

> 
>    at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)

> 
>    at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)

> 
>    at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)

> 
>    at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

> 
>    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>    at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>    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:585)
>    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:505) 
> 
>    at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
>    at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)

> 
>    at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)

> 
>    ... 16 more
> [INFO] 
> ------------------------------------------------------------------------
> 
> Robert Godfrey wrote:
>>  Hi that should be fixed now;
>>
>>  was a Java 1.5 vs 1.6 issue
>>
>>  -- Rob
>>
> 
> 

Mime
View raw message