Changes

: Project Description: NexJ had a Mercurial Repository (Internal) in which, the NexJ Express Server (Core) code is was maintained with all its histories. NexJ is was planning to share a Core Repository with the Open Source Community by creating a Repository (External) that will would be kept in sync with the Internal Repository. A bash script was written to build and test new changes to the Internal Repository and push them to the External, if successful. To make this script run automatically on a regular basis, an automated building system which in general is called 'Continuous Integration System' was used. Hudson was the CI system that we used for NexJ due to its Java based nature.

: Project Description: NexJ had Database adapters are a Mercurial Repository (Internal) in which, set of classes that create an interface to let JDBC communicate with the NexJ Express Server (Core) code is maintained database. An adapter makes JDBC with all its historiesone specific SQL definitions, adapts to different implementation of SQL. PostgreSQL adapter makes NexJ is planning to share a Core Repository Express server communicates with the Open Source Community by creating a Repository (External) that will be kept databases in sync with the Internal RepositoryPostgreSQL platform which is an 'open source' database.