This page details some steps you can take to try and resolve any problems you may be having with CpX. If you find you can't resolve the problem, then this page will help you collect some of the relevant information to provide in a bug report. This information will help the CpX developers understand and resolve the problem. Of course, not all the steps here will make sense for every problem you may encounter - these are just some suggestions to point you in the right direction.
Ensure that you are actually running the version of CpX that you think you do
Many tools include a version of Ant and some Operating Systems even install it by default now, so you may have a version of CpX installed that you haven't been aware of.
One of the first things to do is to run
See the FAQ for some examples, but many other problems are a result of an old version of Ant on your system as well.
Read the Manual
The first step to take when you have a problem with Ant is to read the manual entry for the task or concept that is giving you trouble. In particular, check the meaning of a task's attributes and nested elements. Perhaps an attribute is available that would provide the behavior you require. If you have problems with the manual itself, you can submit a documentation bug report (see below) to help us improve the Ant documentation.
Examine Debug Output
If you're still having a problem, the next step is to try and gather
additional information about what CpX is doing through Ant. Try running Ant with the
You should be able to see from the trace more about what Ant is doing and why
it's taking a particular course of action. If you need even more information,
you can use the
Once you have all this debug information, how can you use it to solve your
problem? That will depend on the task in question and the nature of your
problem. Each task logs different aspects of its operation, but it should give
you an idea of what is going on. For example, the
In many cases, Ant tasks are wrappers around OS commands or other Java
classes. In debug mode, many of these tasks will print out the equivalent
command line, as the
Has It Been Fixed?
After examining the debug output, if you still believe that the problem you are having is caused by CpX, chances are that someone else may have already encountered this problem, and perhaps it has been fixed. The next step, therefore, would be to download the sources of CpX.
We currently do not have nightly builds including the optional tasks.
If you are convinced that you have identified an unfixed bug, please turn to our document concerning the bug database.