I ran
find . -name *archetype*
at the root of my not-completely-updated geronimo checkout and found
these, eliminating most branches and tags
samples/trunk/geronimo-samples-archetype
sandbox/restructure/maven-plugins/testsuite-archetype-plugin
server/trunk/buildsupport/geronimo-assembly-archetype
server/trunk/buildsupport/geronimo-plugin-archetype
server/trunk/buildsupport/testsuite-archetype-plugin
My main conclusion is that the norm is that when someone finishes
some work in a sandbox or branch and merges it into trunk or releases
a server version, they don' t clean up after themselves so we get
infinite numbers of copies of dead code.
My second conclusion is that we've found all the archetypes.
thanks
david jencks
On Feb 28, 2008, at 11:29 AM, Hernan Cunico wrote:
yeah, I know of that one. Worked with Prasad on this, however this
does not apply to all the sample apps we have, does it?
Cheers!
Hernan
Jason Warner wrote:
Doesn't samples have an archetype? Is that not within the scope
of the conversation? I just noticed it when I was poking through
the samples. On Thu, Feb 28, 2008 at 12:38 PM, David Jencks
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
AFAIK the only ones are the module (which should probably be
called
plugin) and assembly archetypes, and they are only in 2.2 so far.
Does eclipse provide ways to set up bits of maven project such
as by
running archetypes?
Can you get this page into a prominent and appropriate part of
the
documentation? I'd like this to be seen as the preferred way to
deploy stuff for serious development use.
thanks
david jencks
On Feb 28, 2008, at 8:25 AM, Hernan Cunico wrote:
> Hi All,
> question regarding the http://cwiki.apache.org/GMOxDOC21/
> constructing-a-special-purpose-server-using-maven.html doc
>
> Is there a way to identify all the maven archetypes we
provide and
> their purpose? I think we should cover that somewhere in
the doc.
>
> Cheers!
> Hernan
--
~Jason Warner
