directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norbet Reilly" <nrh...@gmail.com>
Subject Re: Apparent ClassCastException with ADS RC1
Date Mon, 27 Feb 2006 05:53:59 GMT
Ok, I completely blew off my Maven 2.0.2 repository and checked out a
brand new build of trunks (rev 381205) and found the following:

--------------------------------------------------------------------------------------
1. mvn clean and recompile using JDK1.4
	2. SAR build failed as below (releases must be being built with
JDK1.5 in 1.4 compatibility mode ?):
    <<<<<
[INFO] [compiler:compile]
Compiling 2 source files to D:\src\adt\apacheds\server-sar\target\classes
[INFO] -------------------------------------------------------------------------
---
[ERROR] BUILD FAILURE
[INFO] -------------------------------------------------------------------------
---
[INFO] Compilation failure

D:\src\adt\apacheds\server-sar\src\main\java\org\apache\directory\server\sar\DirectoryService.java:[47,24]
package javax.management does not exist

D:\src\adt\apacheds\server-sar\src\main\java\org\apache\directory\server\sar\Dir
ectoryService.java:[65,7] cannot access
javax.management.NotificationBroadcasterSupport
file javax\management\NotificationBroadcasterSupport.class not found
public class DirectoryService extends ServiceMBeanSupport implements
DirectoryServiceMBean, MBeanRegistration
   >>>>
	3. so I commented SAR build out from JDK1.4 profile in
apacheds/pom.xml and "mvn install" worked fine
	4. run failed because of missing xml-apis.jar (again implies release
was done using JDK1.5 in 1.4 compatibility mode as these classes are
built into 1.5), so added a .jar manually and added to apacheds.bat
that I am using to run)
	5. when run it, I traced the ClassCastException back to the patch I
made to GlobalRegistries.java, although I haven't pinned down exactly
how the changes I made are related to the observed behaviour as there
is no logical connection. Anyway, that's definitely my problem to sort
out.
--------------------------------------------------------------------------------------

*** My conclusions
  1. Seems like build/run with JDK1.4 is broken due to extra SAR and
xml-apis dependencies missing for JDK1.4 profile.
   2. Maybe the JDK 1.4 profile could use at least one integration
sanity test as part of the default build (like SSL test run under
JDK1.5) that actually fires up the server so the build breaks when a
runtime problem (like my mysterious ClassCastException) is present.

Mime
View raw message