Re: [jdf-dev] JBDS in the Getting Started Developing Applications Guide
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.
We've been incrementally automating our release procedure, and if we have to file a
bunch of JIRAs every time we release Errai, this will be a step in the wrong direction for
that effort. (I know, we could automate this too.. and we will if we have to!) :)
-Jonathan
----- Original Message -----
From: "Pete Muir" <pmuir(a)redhat.com>
To: jdf-dev(a)lists.jboss.org
Cc: "Fred Bricon" <fbricon(a)redhat.com>, "Max Rydahl Andersen"
<manderse(a)redhat.com>
Sent: Tuesday, July 24, 2012 6:48:07 PM
Subject: Re: [jdf-dev] JBDS in the Getting Started Developing Applications Guide
Note, I already updated the archetypes section to work like this.
http://www.jboss.org/jdf/stage/quickstarts/jboss-as-quickstart/guide/Arch...
Aerogear team, Errai team, RichFaces should we include the other project types, like
HTML5, Errai and RichFaces in this section of the guide (archetypes)? I would like to do
this for all, or none :-)
Also, should we have tutorials for the kitchensink versions of HTML5, Errai and RichFaces
apps?
On 24 Jul 2012, at 23:25, Pete Muir wrote:
All
ATM the guide discusses using Maven from the command line to work with the quickstarts,
and then presents JBDS as an option, suggesting people import the quickstart via m2e.
Since I originally wrote this guide JBoss Central has been added to JBDS, and incorporates
many of the quickstarts that the guide discusses in the "Project Examples".
I propose that I rework the guide to present using the Project Examples first and
foremost, and present the command line, with the quickstarts download, as an option.
This does mean we're going to have push the quickstarts to JBDS more actively, and
decide on what should be included.
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?
Pete
_______________________________________________
jdf-dev mailing list
jdf-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jdf-dev
_______________________________________________
jdf-dev mailing list
jdf-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jdf-dev