[
http://jira.codehaus.org/browse/MOJO-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MOJO-1407.
--------------------------------
Resolution: Fixed
Assignee: Robert Scholte
Moved to sandbox
> setup-maven-plugin
> ------------------
>
> Key: MOJO-1407
> URL: http://jira.codehaus.org/browse/MOJO-1407
> Project: Mojo
> Issue Type: New Feature
> Components: _Plugin Submission
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Attachments: setup-maven-plugin.zip, setup.zip
>
>
> Hereby a start of a new plugin I've been working on lately. I called it the
> setup-maven-plugin.
> It's goal is to help users (especially newbies) to setup maven settings and
> other configurationfiles.
> The idea started after introducing maven to several companies, and letting
> the developers set their environment to a network repository.
> Getting started with maven might be some sort of struggle. And what if you
> even have to create a .m2 folder (pretty hard under windows) and build your
> own settings.
> In my opinion it shouldn't be much more complicated then a *mvn
> setup:userSettings* in any directory. This should help anyone settings it's
> maven.
> It's a start, so let me be the first one to be critical:
> - right now this plugin supports 3 kinds of settings: the
> user/global-settings, scm-settings and settings-security. Especially the scm
> requires a lot of dependencies, which is a lot of overhead for the other
> goals.
> - The same goals is some sort of 2-step rocket. The first time you run it you
> will probably get the template in your current directory. The next time it
> will be copied to or merged with the target-file. This is done to keep the
> name of the goals as simple as possible, but I'm not sure if this is the
> right way to go.
> - I've created two goals (setup:settings and setup:scm) which should help the
> user step by step to run the proper goal (interactive). It's just an idea,
> hasn't been worked out completely.
> - I couldn't get access to some File properties of
> DefaultMavenSettingsBuilder, so I had to use reflection.
> - for almost every scm-version I had to write a SettingsUtils and a
> xpp3Writer. For cvs and git I couldn't get access to the targetfile (is
> inside some method), so testing was impossible. I've create already some
> tests, called them ....Testless. so they will be skipped by maven, although
> not by eclipse.
> - there are some issues of dependencies which hasn't been released yet, so I
> had to rewrite some of that code inside some classes.
> - I'm not happy with the expressions of the goals yet, requires a second look.
> There are also some site-pages which might explain the strategy of these
> goals a little bit.
> One wish is to have this plugin be available in at least codehaus, so newbies
> don't have to run an extreme long goal.
> I've already had positive responses, so I thought by now it's time to submit
> the plugin and see what kind of remarks the community will make. Meanwhile
> I'll optimize the project, I have some other nice features in mind so I won't
> be done yet.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
