Hi Susanne,

Thanks for writing up the problem(s).


On Wed, Feb 9, 2011 at 3:20 AM, Susanne Gladén <[email protected]> wrote:
> I now checked out the code from trunk and I followed the steps in:
> https://cwiki.apache.org/confluence/display/ROLLER/Build+and+Run+Roller+5+in+Eclipse

I just wrote those instructions last week, so you may be the first
"tester" here. They work for me, but until they work for others they
are useless so let's fix them.


> When building I get the following errors:

What steps are you on in the process here? What did you use to invoke
the build? You should first run "mvn install" on the pom.xml file at
the top of the Roller trunk directory.

> Build errors for roller-planet-business;
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-antrun-plugin:1.2:run
> (gen-db-scripts) on project roller-planet-business: Execution
> gen-db-scripts of goal
> org.apache.maven.plugins:maven-antrun-plugin:1.2:run failed: Plugin
> org.apache.maven.plugins:maven-antrun-plugin:1.2 or one of its
> dependencies could not be resolved: Could not find artifact
> org.apache.roller:test-utils:jar:5.0.0-RC4 in central
> (http://repo1.maven.org/maven2)

Here, it appears that the test-utils jar was not built for some
reason. This might be happening because of the way you launched the
build, or the failure below.


> Build errors for roller-weblogger-business;
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.codehaus.mojo:buildnumber-maven-plugin:1.0-beta-3:create
> (default) on project roller-weblogger-business: Cannot get the
> revision information from the scm repository : Error!

Here it seems the build cannot connect to SVN to determine the
revision number to put into the build. I'm not sure what could cause
that because you said that you have Subclipse and therefore the
Subversion client installed.

To fix this you may have to install a Subversion client separately
from Eclipse. Or maybe you already have one? Open up a command-line
window and run "svn --version" and tell us what you get.

The rest of the errors are due to test-utils not being built.

Hope that helps,

- Dave

Reply via email to