Release plugin doesn't honor profiles defined in user settings

arnaud@mbp-arnaud:~/Code/eXo/cloud-management (git:develop %)$ mvn release:prepare -DdryRun=true
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
...
[INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ cloud-management-parent ---
[INFO] Resuming release from phase 'run-preparation-goals'
[INFO] Executing preparation goals - since this is simulation mode it is running against the original project, not the rewritten ones
[INFO] Executing goals 'clean verify'...
[WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
[INFO] [INFO] Scanning for projects...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Reactor Build Order:
...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Building eXo Cloud Management :: Parent 1.1-M4-SNAPSHOT
[INFO] [INFO] ------------------------------------------------------------------------
...
[INFO] [INFO] --- maven-license-plugin:1.9.0:check (check-headers) @ cloud-management-parent ---
[INFO] [WARNING] The POM for org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 is missing, no dependency information available
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Reactor Summary:
[INFO] [INFO] 
[INFO] [INFO] eXo Cloud Management :: Parent .................... FAILURE [1.257s]
...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD FAILURE
[INFO] [INFO] ------------------------------------------------------------------------
...
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [WARNING] The requested profile "exo-central" could not be activated because it does not exist.
[INFO] [WARNING] The requested profile "local-properties" could not be activated because it does not exist.
[INFO] [WARNING] The requested profile "exo-private" could not be activated because it does not exist.
[INFO] [WARNING] The requested profile "exo-staging" could not be activated because it does not exist.
[INFO] [ERROR] Failed to execute goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check (check-headers) on project cloud-management-parent: Execution check-headers of goal com.mycila.maven-license-plugin:maven-license-plugin:1.9.0:check failed: Plugin com.mycila.maven-license-plugin:maven-license-plugin:1.9.0 or one of its dependencies could not be resolved: Failure to find org.exoplatform.cloud-management:cloud-build-tools:jar:0.1-M1 in http://repository.exoplatform.org/public was cached in the local repository, resolution will not be reattempted until the update interval of exo-fr-mirror has elapsed or updates are forced -> [Help 1]
[INFO] [ERROR] 
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[INFO] [ERROR] 
[INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles:
[INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] eXo Cloud Management :: Parent .................... FAILURE [5.210s]
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
...
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) on project cloud-management-parent: Maven execution failed, exit code: '1' -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException