If a repository does not have a master branch, checking out a project using the Maven SCM Import wizard fails. It first downloads a bare repository to a temporary directory (WORKSPACE/maven.LONGUNIQUESTRING). Since the result is bare, it then give the error:
"No maven projects found. Do you want to create project using new project wizard? Checkout location will be copied to the clipboard."
This behavior occurs even when a branch name is specified in the 'revision' field.
The workaround for this bug is to first clone the repository through egit, then check it out as a maven project, then share the projects with git to re-enable versioning. This requires a dozen extra steps, and is much more difficult to explain to new users.
If a repository does not have a master branch, checking out a project using the Maven SCM Import wizard fails. It first downloads a bare repository to a temporary directory (WORKSPACE/maven.LONGUNIQUESTRING). Since the result is bare, it then give the error:
This behavior occurs even when a branch name is specified in the 'revision' field.
The workaround for this bug is to first clone the repository through egit, then check it out as a maven project, then share the projects with git to re-enable versioning. This requires a dozen extra steps, and is much more difficult to explain to new users.