Confusing message during the boot up of proactive-server

[paraita]

When starting proactive-server (/bin/proactive-server):

The resource manager with 2 local nodes created on pnp://172.20.10.2:6473[0/143]
The scheduler created on pnp://172.20.10.2:64738/
Starting the web applications...
mac os x
The web application /automation-dashboard created on http://172.20.10.2:8080/automation-dashboard
The web application /studio created on http://172.20.10.2:8080/studio
The web application /notification-service created on http://172.20.10.2:8080/notification-service
The web application /cloud-automation-service created on http://172.20.10.2:8080/cloud-automation-service
The web application /catalog created on http://172.20.10.2:8080/catalog
The web application /proactive-cloud-watch created on http://172.20.10.2:8080/proactive-cloud-watch
The web application /scheduler created on http://172.20.10.2:8080/scheduler
The web application /scheduling-api created on http://172.20.10.2:8080/scheduling-api
The web application /connector-iaas created on http://172.20.10.2:8080/connector-iaas
The web application /rm created on http://172.20.10.2:8080/rm
The web application /rest created on http://172.20.10.2:8080/rest
The web application /job-planner created on http://172.20.10.2:8080/job-planner
*** Get started at http://172.20.10.2:8080 ***
Executing tools/LoadPackages.groovy

The last message can be confusing for the user as it implies something is running prior to readiness.
I propose the following improvements (non exclusive):

• Put the Executing <script_name> verb tense to the past or completely remove this message from the standard output (it is already present in the Scheduler.log)
• Let the *** Get started at <whatever> *** be the final message of the boot up of the proactive-server. This brings closure to the start phase of the scheduler from a user point of view.

This still happens as of the day of creation of this issue and is independent of the platform.