[svn:bz-4.x] 16256: Do some build cleanup on the BlazeDS/4.x branch.

Question

Revision: 16256
Revision: 16256
Author:   [email protected]
Date:     2010-05-20 10:50:31 -0700 (Thu, 20 May 2010)
Log Message:
Do some build cleanup on the BlazeDS/4.x branch. I had just intended to update the build scripts to exclude xalan.jar from the WEB-INF/lib directory of a bunch of the webapps but while I was doing this I found a number of other problems that I attempted to fix. Here is a breakdown of what I changed.
Update build scripts to not add xalan.jar to the WEB-INF/lib directory of those webapps that were including it. As far as I can tell we don't need to/shouldn't be shipping xalan.jar in the WEB-INF/lib directory of any of the webapps. I also updated the build scripts to not add fxgutils.jar to the WEB-INF/lib directory of those webapps that were including it. I also can't see any reason for us to be shipping fxgutils.jar with any of the webapps. This jar file is part of the Flex SDK and we're no longer shipping BlazeDS with the Flex SDK. 
The clean target in the main build.xml file was not calling clean on the ds-console webapp. It was also calling clean on the qa-regress webapp twice and never calling clean on qa-manual which was probably a typo. Fixed the build so clean now gets called for ds-console and qa-regress.
The samples webapp had hsqldb.jar checked into its WEB-INF/lib directory in svn. The build script for the samples webapp was also copying hsqldb.jar from the <blazesd-home>/lib/hsqldb directory. I cleaned this up by deleting hsqldb.jar from the samples/WEB-INF/lib directory in svn so now we will just get the jar from the <blazeds-home/lib/hsqldb directory. 
After removing hsqldb.jar from the samples/WEB-INF/lib directory none of the webapps in BlazeDS have anything checked into their WEB-INF/lib directories in svn. Most of the BlazeDS webapps were using properties from the top level build.properties file to determine which jars to delete from the WEB-INF/lib directory. This is problematic because unless we do a good job of keeping these lists of jars up to date files wind up not being cleaned from the WEB-INF/lib directory and we could potentially ship files that are no longer part of the build. I fixed this issue by updating the build scripts for all of the webapps to delete everything from the WEB-INF/lib directory as part of the clean target.
Checkintests: passed
Modified Paths:
    blazeds/branches/4.x/apps/blazeds/build.xml
    blazeds/branches/4.x/apps/blazeds-spring/build.xml
    blazeds/branches/4.x/apps/ds-console/build.xml
    blazeds/branches/4.x/apps/samples/build.xml
    blazeds/branches/4.x/apps/samples-spring/build.xml
    blazeds/branches/4.x/apps/team/build.xml
    blazeds/branches/4.x/build.properties
    blazeds/branches/4.x/build.xml
    blazeds/branches/4.x/qa/apps/qa-manual/build.xml
Removed Paths:
    blazeds/branches/4.x/apps/samples/WEB-INF/lib/

Answer 1

Found solution after many hours of search and test:
I have Launch2Net Premium 2.6.2 obn my system to get USB 3G Modem stick to work. It install many files into /System/Library/Extensions. All files are SierraDIPService.kext SierraFSPService.kext SierraDevSupport.kext.
Remove SierraDIPService.kext from the above Extensions folder allow MobileDevice.pkg and othe installer that need to update system extension like soundflower.pkg to work properly.
So, Sierra driveris the culprit!! I have to uninstall Launch2Net off my system. But my USB Stick Modem will not work anymore
I have written to Nova System, the developer of Launch2Net to get fix to this problem
Will update if there is any progess