The beta 1 release of dashboard required that the Cruise Control AntBuilder be patched to allow a custom listener to be connected to the underlying Ant build.
Beta 2 is out now, and this provides a custom Logger that mimics the built in XmlLogger used by Cruise. This means that you can now use Dashboard on the server with an unmodified Cruise Control installation. What's even better is that there are now some documents in the distribution that show you how to do this.
Please note, though, that Dashboard cannot currently be used with the Cruise Control maven builder (but you can use the Ant checkpoint task inside your maven build instead).
> that there are now some documents
can you expand on this? where are these documents? what needs to be done?
Steve Polyak
Stephen.Polyak@pearson.com
The docs are in the dashboard distribution. You can download the latest version from http://www.sf.net/projects/dashboard
They walk you through the steps required to connect a Dashboard component to your Cruise build. - Ian Bourke
I modified the cruisecontrol.xml like the readme said to use the dashboard ant logger class, but cruisecontrol will not start if i have this. - Rob Biernat
Does anyone know if there is a port of Dashboard as a JBuilder plug-in? I'm an IntelliJ junky myself, but we've got the full suite of Borland tools in house. It would be nice if others on the team could use the tool as well.
May 19, 2004:
I was having the same problem Rob was describing above. After adding the Dashboard-specified Ant logger to my CruiseControl config.xml file, builds would no longer work--I got a class not found exception from Ant. Apparently, the Dashboard server jar file must also be in the classpath for Ant (I accomplished this by copying the jar to the Ant lib directory).
However, this was not enough. After this I got a class not found exception for org/jdom/JDOMException. I copied the jdom.jar file from CruiseControl into the Ant lib directory as well.
However, this was still not enough. Now I get a RuntimeException: "Unable to instantiate specified logger class net.sourceforge.dashboard.cruisecontrol.CruiseBuildManager". This one's got me stumped. Does anyone have any ideas? Surely somebody's gotten this to work before?
June 24, 2004
I'm having the same problem with the listener when the build starts : ""Unable to instantiate listener net.sourceforge.dashboard.cruisecontrol.CruiseBuildManager". I use CruiseControl 2.1.5, DashBoard 1.0.5 and Eclipse 3.0RC3. If anyone knows something to fix the issue (incompatibilities? configuration issue?), you're more than welcome.
—
August 3 2004
I think the solution (at least for me, Eric) was to ensure that <host> and <port> had values in the multicast element. Without those, I got the same instantiation error as you describe.
=david=
—
Aug. 12, 2004
I had the same problem and actually it can happen for quite a few reasons regarding the xml configuration file for dashboard. In order to track down the cause I modified the [Main.class|^Main.class] in Ant and updated the ant.jar in the lib directory. After there it was quite easy to figure out what was wrong.
Shane
Nov. 02, 2004
Has anyone figured out how to solve this issue? I am experiencing the same problems as Jack describes above:
1) I have copied the dashboard-server-1.0.5.jar to the Ant lib directory, and got the class not found exception for org/jdom/JDOMException.
2) I copied the jdom.jar file from CruiseControl into the Ant lib directory, and got the RuntimeException: "Unable to instantiate specified logger class net.sourceforge.dashboard.cruisecontrol.CruiseBuildManager".
I use cruisecontrol-2.1.6, dashboard-1.0.5, apache-ant-1.6.2 and IntelliJ IDEA 4.5.2.
dashboard-props.xml:
------------
<dashboard>
<multicast>
<host>192.168.5.121</host>
<port>3274</port>
</multicast>
<targets>
<target name="init">
<message index="1"/>
</target>
<target name="clean">
<message index="2"/>
</target>
<target name="compile">
<message index="3"/>
</target>
<target name="aspect-compile">
<message name="aspect-compile" index="4"/>
</target>
<target name="signjars">
<message index="5"/>
</target>
<target name="deploy">
<message index="6"/>
</target>
<target name="test" event="FAILED">
<message name="aaargh" status="FAILED"/>
</target>
</targets>
</dashboard>
------------
Nov. 02, 2004
I solved my problem 
What I did: I moved the dashboard-props.xml from the Ant lib directory into another location and added the path to it in the ant-script ($ANT_HOME/bin/ant) like this:
LOCALCLASSPATH="$LOCALCLASSPATH":/path/to/props/
