+++ This bug was initially created as a clone of Bug #906667 +++

Description of problem:
In maven-client-2.0.2-SNAPSHOT, defaultProjectType become an mandatory option.
However, this is interfering the project maintainers' work flows.

Quite a few project maintainers work create a new project using following method:
1. Copy zanata.xml of other project.
2. Change the project name and version (they seldom need to change project type, as they usually deal with just one type).
3. Using either zanata client to create project.

After the introduce of defaultProjectType, now not only it breaks the existing automation scripts, but also project maintainer now need to type redundant information to command line options.

Version-Release number of selected component (if applicable):
Maven client 2.0.2-SNAPSHOT

How reproducible:
Always

Steps to Reproduce:
1. Copy a existing working zanata.xml
2. Change the project id to "PushTest" or other id that haven't been used.
3. mvn -e zanata:put-project
4. mvn -e zanata:put-version
  
Actual results:
[ERROR] Failed to execute goal org.zanata:zanata-maven-plugin:2.0.2-SNAPSHOT:put-version (default-cli) on project null: The parameters 'versionProject', 'versionSlug' for goal org.zanata:zanata-maven-plugin:2.0.2-SNAPSHOT:put-version are missing or invalid -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.zanata:zanata-maven-plugin:2.0.2-SNAPSHOT:put-version (default-cli) on project null: The parameters 'versionProject', 'versionSlug' for goal org.zanata:zanata-maven-plugin:2.0.2-SNAPSHOT:put-version are missing or invalid
                                        
Expected results:
Version in zanata.xml is used to create version without error.