Stefano "Kismet" Lenzi wrote:
There is also a missing wizard that would need to accept Maven SCM
urls.
Why do the user have will have to type in the SCM URL? I think that it
would be more usable if the SCM is generated by inspecting the POM of
the Maven project selected by groupId:artifactId:version:type. An SCM
URL could be useful for non-maven project (but it is a different story
I think)
When you'll have ScmHandler for corresponding SCM type, Maven
Materialization [1] will just work
[1] http://www.jroller.com/eu/entry/maven_project_materialization
But it is possible that project is not deployed anywhere or repository
it is deployed at is not indexed. So user should be allowed to specify
either SCM URL directly or specify location of the Maven pom.
It would be similar to the current Subclipse wizard, but simpler,
because we can't provide advanced UI, such as browsing repositories and
commit history using present Maven SCM API. I am actually planning to
consolidate multiple existing import Maven project wizards into one, so
the SCM import will be part of it, but we'll need some extension points
to allow to plug in advanced UI like I've implemented for Subclipse.
I worrying that adding too many option and different behavior to a
single Import Wizard will be make it harder to learn and use.
There isn't really that many options out there. The first wizard page
will just allow to specify where project is imported from (local fs,
maven artifact or pom url, or scm url). I believe it is better to have
single entry point when going from the File / Import... UI.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
