You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Robert Scholte <rf...@hotmail.com> on 2008/11/09 17:52:51 UTC
new plugin proposal: maven-setup-plugin
When introducing Maven during some projects, I see the same problem every time.
They've heard of Maven, but find it a bit too difficult to start with.
So I've been thinking of creating an maven-setup-plugin.
It should be able write a settings.xml file (although: I'm not able to access userSettingsFile or globalSettingsFile of the DefaultMavenSettingsBuilder or any plexusproperties, where these files are defined)
You can use the Prompter to ask some questions.
You could create some templates to prefill your settings.xml, i.e. the required Nexus-config for your company.
If you can detect if 'mvn' is running for the first time, you could ask for setting up maven.
There are several ways to access such file:
- Add a /conf/setup.xml file to your maven-package before distributing it within your company.
- Publish a setup-file. You can prompt for it, or run 'mvn setup -Dfile=http://somedomain/setup.xml'
Using maven shouldn't be more than unpacking the distribution, setting M2_HOME and path-variable.
Everything afterwards should be possible by maven-commands self.
This way it would be much easier to introduce Maven in any company.
Just let me know if you like the idea.
Kind regards,
Robert Scholte
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: new plugin proposal: maven-setup-plugin
Posted by Barrie Treloar <ba...@gmail.com>.
On Tue, Nov 11, 2008 at 5:26 AM, Brett Porter <br...@apache.org> wrote:
> This sounds useful to try.
>
> There are two things I'd do if you're building this:
> - be cautious about letting it get too complicated (trying to be everything
> to everyone)
> - break the parts out into components that can be reused (eg, IDE
> integration). These could perhaps be brought back into Maven at some point
> if we need settings file management beyond what is already there.
As a general rule, I find that people who use maven stay just as users.
They just don't understand (and are even confused) by how it works
even though it is simple to understand. The reason for this is that
once maven has been setup it just works they dont have a need to
increase their knowledge.
Whereas those people who are users of Ant tend to have a greater
technical understanding because they are forced to have this
understanding.
So for setting up maven in our company I just point them at our Wiki page.
It describes:
* how to download
* how to install
* how to configure
* common trouble shooting steps
And where necessary a boiler plate with "TODO" included where user
specific data needs to be modified. However I find that most of the
files can be copied verbatim and we have a complicated environment.
I've yet to see any automated process return a better ROI than this
simple process.
And it is so different across environments that I can't see how a tool
will help with the process. Unfortunately that means the local Maven
expert has to set this up but its not much effort.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: new plugin proposal: maven-setup-plugin
Posted by Brett Porter <br...@apache.org>.
This sounds useful to try.
There are two things I'd do if you're building this:
- be cautious about letting it get too complicated (trying to be
everything to everyone)
- break the parts out into components that can be reused (eg, IDE
integration). These could perhaps be brought back into Maven at some
point if we need settings file management beyond what is already there.
Cheers,
Brett
On 09/11/2008, at 9:52 AM, Robert Scholte wrote:
>
> When introducing Maven during some projects, I see the same problem
> every time.
> They've heard of Maven, but find it a bit too difficult to start with.
> So I've been thinking of creating an maven-setup-plugin.
> It should be able write a settings.xml file (although: I'm not able
> to access userSettingsFile or globalSettingsFile of the
> DefaultMavenSettingsBuilder or any plexusproperties, where these
> files are defined)
> You can use the Prompter to ask some questions.
> You could create some templates to prefill your settings.xml, i.e.
> the required Nexus-config for your company.
> If you can detect if 'mvn' is running for the first time, you could
> ask for setting up maven.
>
> There are several ways to access such file:
> - Add a /conf/setup.xml file to your maven-package before
> distributing it within your company.
> - Publish a setup-file. You can prompt for it, or run 'mvn setup -
> Dfile=http://somedomain/setup.xml'
>
> Using maven shouldn't be more than unpacking the distribution,
> setting M2_HOME and path-variable.
> Everything afterwards should be possible by maven-commands self.
>
> This way it would be much easier to introduce Maven in any company.
>
> Just let me know if you like the idea.
>
> Kind regards,
>
> Robert Scholte
>
>
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's
> FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org