On 25 Jul 2012, at 17:52, Jonathan Fuerth <jfuerth(a)redhat.com> wrote:
> Yes, this does make sense.
>
> Is there an automatic process available for updating our archetypes in JBDS and JBT?
As I recall, the process we've been using is to file a JIRA for each archetype update
we'd like.
Not yet, thats the stack.yml efforts.
> We've been incrementally automating our release procedure, and if we have to file
a bunch of JIRAs every time we release Errai,
It's one jira, not a bunch if i'm correct ;)
And its not *everytime* you do a release afaik, its when you have a release that you
feel is compatible and tested enough to work with AS 7.1/EAP 6.0 to be put front and
center in JBT and/or JBDS.
>> Fred/Max, I know what appears in the list is controlled centrally. Can you point
us at it, so that we can understand where we are at, today?
Fred is on vacation/honeymoon right now (got married saturday) - but he sent around this
https://community.jboss.org/wiki/TestArchetypesInJBossCentral
a while ago which describes how to test/setup archetype info.
There is also
https://community.jboss.org/wiki/MavenArchetypeCreationGuidelines stating
the guidelines for the archetypes.
The actual files are at
http://download.jboss.org/jbosstools/examples/
I believe the JBT 3.3 is
http://download.jboss.org/jbosstools/examples/project-examples-maven-3.3.xml