Rafael, I agree we need to decide soon. I don't think the current
changes impact the EAP 6 docs, but I do know the team is always
asking me if there are any quickstarts that demonstrate specific
technologies. That's why I hate to remove any Java EE 6 quickstarts
from the EAP builds that might be useful for documentation.
On 12/11/2012 02:38 PM, Rafael
Benevides wrote:
I think that we should define this asap.
There several quickstarts issues opened:
https://issues.jboss.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+JDF+AND+issuetype+%3D+%22Feature+Request%22+aND+component+%3D+quickstarts+and+labels+%3D+deltaspike+and+status+%21%3D+closed+ORDER+BY+key&runQuery=true&clear=true
Some of them (JDF-144, JDF-159 and JDF-165) were "ready for
review" and this decision can make them to be remade.
If this impact the existing documentation I believe that we should
keep the existing ones and create another copy with deltaspike-*
prefix.
Em 11-12-2012 16:08, Sande Gilda escreveu:
I've noticed quite a few quickstarts are being modified to use
DeltaSpike, changing the target from EAP to WFK. My only concern
is that the quickstarts are mentioned frequently in the EAP 6
documentation. Sometimes they point to the quickstarts for
examples on how to code things. I did a quick search and it
appears the following quickstarts are mentioned (I may have
missed 1 or 2):
- bean-validation
- cluster-ha-singleton
- ejb-remote
- ejb-security
- greeter
- helloworld
- helloworld-ws
- kitchensink
- logging-tools
- numberguess
- wsat-simple
- wsba-coordinator-completion-simple
- wsba-participant-completion-simple
I'm just mentioning this so we are aware that changes like this
could impact the EAP 6.1 docs.
Thanks,
Sande