Folks,

we are pleased to announce the second release candidate of MICO 2.3.12!
You can download it here:

http://www.mico.org/snapshots/mico-2.3.12RC1.tar.gz
http://www.mico.org/snapshots/mico-2.3.12RC1.zip

(only one of these two files is necessary)

The list of changes since the first release candidate is below. Please test it on your platform and send success/failures reports to the [email protected] mailing list (you need to be subscribed before sending anything there, if you are not subscribed and wouldn't like to be, please send your reports directly to me).

Cheers,
Karel


- fix assert when generating IDL containing CORBA::Principal type
  (Heiko Jansen)
- fix GIOPConn::initialize_reader_key method to initialize key only
  once
- fix IDL compiler dependency builder for inheritance and circular
  dependency issue
- fix name service to properly initialize Binding object returned from
  `next_one' operation
- fix warning about missing virtual dtor by adding it to the
  GIOPConnMgr class
- fix MICO::IIOPProxy::make_conn method memory leak w.r.t. profile
  cloning
- fix CORBA::IOR::copy method to initialize active profile correctly
- update certificates for test/mt/stress test
- fix to serialise calls to gethostbyname/gethostbyaddr functions
  (issue reported by Jose Luu)
- merge from Wireless MICO branch (Jaakko Kangasharju)
  - update MANIFEST file
  - update the Wireless TODO file
  - remove profile registration from LTP profile
  - remove the Wireless README file
  - remove --relative-paths from Wireless IDL compilation
  - create POA later in Wireless CORBA bridges
  - correct Bluetooth for non-wireless use


------------------------------------------------------------------------
Karel Gardas, Principal Software Engineer, ObjectSecurity Ltd.
St John's Innovation Centre, Cowley Rd., Cambridge CB4 0WS, UK
Tel. +44 1223 420252, Fax. +44 870 762 6041 USA: Tel.+1-800-898-9148, Fax +1-360-933-9591
[EMAIL PROTECTED], www.objectsecurity.com
------------------------------------------------------------------------
_______________________________________________
Mico-devel mailing list
[email protected]
http://www.mico.org/mailman/listinfo/mico-devel

Reply via email to