Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 51847 invoked from network); 16 Mar 2009 17:41:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Mar 2009 17:41:39 -0000 Received: (qmail 85213 invoked by uid 500); 16 Mar 2009 17:41:39 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 84738 invoked by uid 500); 16 Mar 2009 17:41:38 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 84729 invoked by uid 99); 16 Mar 2009 17:41:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Mar 2009 10:41:38 -0700 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.136.44.57] (HELO smtp102.prem.mail.sp1.yahoo.com) (98.136.44.57) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 16 Mar 2009 17:41:30 +0000 Received: (qmail 49235 invoked from network); 16 Mar 2009 17:41:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Mime-Version:Subject:Date:References:X-Mailer; b=pvZScHVGPC4OOQMIv7/ds9PRHX3tuTMjqcoZNaUcf6rQ1aHi+xPXaRG+/H9bPxjcHbHMDy3YTydqkqX7cT6hXXWkji3GWUHCVBjqTDCNUwuHuzesp8A6BlN1yCF0OfKZWchoLm9gDeZtQ67W0FtbUuljpTb+NW5fgdCjXb0Ub0U= ; Received: from unknown (HELO ?10.11.55.44?) (david_jencks@76.76.148.215 with plain) by smtp102.prem.mail.sp1.yahoo.com with SMTP; 16 Mar 2009 17:41:08 -0000 X-YMail-OSG: 94Zwjf8VM1kXuoGb2oauKTVivFCv_JSPY5hUdhZ5vqLFPyWg.lgauvX6XHgvyYxf4n8b8tTxIkdRJDcIMYJm_oOUeFkoBYLk2fIc_ZEzrz3MF1Lu6fy1B0mv6vAmdRjqSNK5ZZfsrpZqbJFl2Bzld9hFxOjXWZI11ExcSAOaal7kR7wOjapzcF8FnWNAUjEclHFNxtpowffobXS.2D97vKZk9gwqrrVihW4FLypVYDxH0r_GqWTtbbLconce X-Yahoo-Newman-Property: ymail-3 Message-Id: <31AE2F64-E11F-4C04-A059-34F98FAD5A7B@yahoo.com> From: David Jencks To: dev@geronimo.apache.org In-Reply-To: Content-Type: multipart/alternative; boundary=Apple-Mail-86--927453659 Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: [DISCUSSION] to create a set of maven archetypes for applications running on geronimo ? Date: Mon, 16 Mar 2009 10:41:07 -0700 References: X-Mailer: Apple Mail (2.930.3) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-86--927453659 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On Mar 16, 2009, at 12:18 AM, Shawn Jiang wrote: > Maven archetype is a powerful tools to make life easier when > developers want to create a project from scratch. Currently, > Geronimo is using archetype to create new testsuite/assembly/plugin/ > quickly. > > 1: local -> geronimo-archetype-testsuite (testsuite) > 2: local -> geronimo-assembly-archetype (geronimo-assembly-archetype) > 3: local -> geronimo-plugin-archetype (geronimo-plugin-archetype) > 4: local -> xmlbeans-maven-plugin (xmlbeans-maven-plugin) > > Which can only help geronimo developers/contributors when they want > to create their new testsuite/assembly/plugin. There's no archetype > for geronimo users who want to create their geronimo Apps/Assets > easily from scratch. I'm wondering if geronimo could provide a set > of new archetypes for Apps/assets running in geronimo. Some initial > candidates are: > > 1, war-geronimo-archetype > A simple war which contains the geronimo deployment plan. > > 2, ear-geronimo-archtype > A maven project that contains 4 modules: > 1, a war module > 2, a ear module > 3, a ejb module > 4, a client module. > > 3, datasource-geronimo-archtypes > There should be many sub archtypes to create different datasources > plan. > > 4, security-geronimo-archtypes > There should be many sub archtypes to create different(properties/db/ > ldap) realms. > > 5, GBean-geronimo-archtype > A simple GBean development archtype with two mode: normal/annotation > > Any comments ? I don't quite understand yet what these archetypes would provide. The most plausible thing would be to add a "fill in the blanks" plan template. I'm not sure an archetype is the best way to do this, but I'm certainly open to seeing how it works. Our existing plugin and assembly archetypes are rather obsolete and don't use the current archetype infrastructure. I wonder if a more practical project would be to update especially the plugin archetype to figure out what kind of thing you are building a plugin for and include the appropriate plan template and add the appropriate dependencies and car-maven-plugin configuration. I guess if we could figure out how to this more or less the same logic could be used to modify an existing javaee maven project to insert the appropriate geronimo plan template in the appropriate directory. I don't think that dupicating the war, ear, etc archetypes is likely to be worth the effort. Anyway I'd certainly like to know more about what you have in mind and am very glad someone else is thinking about maven archetype support! thanks david jencks > > > > -- > Shawn > --Apple-Mail-86--927453659 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
On Mar 16, 2009, = at 12:18 AM, Shawn Jiang wrote:

Maven = archetype is a powerful tools to make life easier when developers want = to create a project from scratch.  Currently, Geronimo is using = archetype to create new testsuite/assembly/plugin/ quickly.

1: = local -> geronimo-archetype-testsuite (testsuite)
2: local -> = geronimo-assembly-archetype (geronimo-assembly-archetype)
3: local -> = geronimo-plugin-archetype (geronimo-plugin-archetype)
4: local -> = xmlbeans-maven-plugin (xmlbeans-maven-plugin)

Which can only help = geronimo developers/contributors when they want to create their new = testsuite/assembly/plugin.  There's no archetype for geronimo users = who want to create their geronimo Apps/Assets easily from scratch. =   I'm wondering if geronimo could provide a set of new archetypes = for Apps/assets running in geronimo. Some initial candidates are:
=
1, = war-geronimo-archetype
A simple war which contains the = geronimo deployment plan.  

2, ear-geronimo-archtype
A maven = project that contains 4 modules:
 1, a war module
 2, = a ear module
 3, a ejb module
 4, a client = module.

3, datasource-geronimo-archtypes
There should be many = sub archtypes to create different datasources plan.

4, = security-geronimo-archtypes
There should be many sub archtypes = to create different(properties/db/ldap) realms.

5, = GBean-geronimo-archtype
A simple GBean development archtype = with two mode: normal/annotation

Any comments = ?

I don't quite understand yet what these = archetypes would provide.  The most plausible thing would be to add = a "fill in the blanks" plan template.  I'm not sure an archetype is = the best way to do this, but I'm certainly open to seeing how it = works.

Our existing plugin and assembly = archetypes are rather obsolete and don't use the current archetype = infrastructure.  I wonder if a more practical project would be to = update especially the plugin archetype to figure out what kind of thing = you are building a plugin for and include the appropriate plan template = and add the appropriate dependencies and car-maven-plugin = configuration.

I guess if we could figure out = how to this more or less the same logic could be used to modify an = existing javaee maven project to insert the appropriate geronimo plan = template in the appropriate directory.  I don't think that = dupicating the war, ear, etc archetypes is likely to be worth the = effort.

Anyway I'd certainly like to know more = about what you have in mind and am very glad someone else is thinking = about maven archetype = support!

thanks
david = jencks




-- =
Shawn


= --Apple-Mail-86--927453659--