Return-Path: Delivered-To: apmail-maven-dev-archive@www.apache.org Received: (qmail 85913 invoked from network); 10 Nov 2008 22:25:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Nov 2008 22:25:43 -0000 Received: (qmail 10585 invoked by uid 500); 10 Nov 2008 22:25:47 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 10520 invoked by uid 500); 10 Nov 2008 22:25:47 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 11490 invoked by uid 99); 10 Nov 2008 18:57:27 -0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Message-Id: <2AB20ACC-7339-4166-98C8-7D9EA74C1919@apache.org> From: Brett Porter To: "Maven Developers List" In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Subject: Re: new plugin proposal: maven-setup-plugin Date: Mon, 10 Nov 2008 11:56:31 -0700 References: X-Mailer: Apple Mail (2.929.2) Sender: Brett Porter X-Virus-Checked: Checked by ClamAV on 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