Found the problem - a third-party jar file had spaces after
the version value which was causing the NumberFormatException.
The following change to DeweyDecimal fixes the problem.

  RCS file:
/home/cvspublic/jakarta-avalon-excalibur/src/scratchpad/org/apache/avalon/ex
calibur/util/DeweyDecimal.java,v
  retrieving revision 1.2
  diff -r1.2 DeweyDecimal.java
  58c58
  <             final String component = tokenizer.nextToken();
  ---
  >             final String component = tokenizer.nextToken().trim();

Cheers, Steve.


> -----Original Message-----
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 21 November, 2001 16:50
> To: Avalon Developers List
> Subject: [phoenix] launch failure
>
>
>
> Have just updated out site with the latest CVS of Avalon, Logkit,
> Excalibur
> and Phoenix.  The build (under Win NT4 SP6, JDK1.4beta3 completed without
> problem).  However, when starting Phoenix the
> DefaultDeployer.deploy method
> is throwing a DeploymentException.  The cause of the
> DeploymentException is
> a NumberFormatException thrown by Integer.parseInt within Excalibur's
> DeweyDecimal which is called within excalibur's Extension constructor.
>
> Trace attached.
>
> Cheers, Steve.
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to