add verify call to STO in the migrations

CHANGELOG.md

@@ -8,7 +8,8 @@ All notable changes to this project will be documented in this file.
 ## Changed    
 
 * Fixed `capReached()` which was checking fundsRaised agains cap, but the cap is expressed in tokens.    
-* Constant key variables migrated from the securityToken to ISecurityToken contract.   
+* Constant key variables migrated from the securityToken to ISecurityToken contract.
+* Solidity compiler version get changed to 0.4.23 that leads to the addition of reason string in the `require` and `revert` statements.   
 
 ## Added   
 

migrations/2_deploy_contracts.js

@@ -79,6 +79,11 @@ module.exports = function (deployer, network, accounts) {
       // N) Register the CappedSTOFactory in the ModuleRegistry to make the factory available at the protocol level.
       // So any securityToken can use that factory to generate the CappedSTOFactory contract.
     return moduleRegistry.registerModule(CappedSTOFactory.address, {from: PolymathAccount})
+    }).then(()=>{
+      // G) Once the CappedSTOFactory registered with the ModuleRegistry contract then for making them accessble to the securityToken
+      // contract, Factory should comes under the verified list of factories or those factories deployed by the securityToken issuers only.
+      // Here it gets verified because it is deployed by the third party account (Polymath Account) not with the issuer accounts.
+      return moduleRegistry.verifyModule(CappedSTOFactory.address, true, {from: PolymathAccount})
     }).then(() => {
         console.log('\n')
         console.log('----- Polymath Core Contracts -----')