[jdf-dev] QSTools - Quickstarts tooling automation update to meet remote quickstarts

[Rafael Benevides]

Hi all, Sande and Pete,

One significant change in JDF Quickstarts repo is the use of git 
submodules to bring remote quickstarts to JDF. But... Sometimes remote 
quickstarts doesn't ( and don't want/need to ) follow JDF Contributing 
guide ( 
https://github.com/jboss-jdf/jboss-as-quickstart/blob/master/CONTRIBUTING.md 
).

There are some requirements from QSTools ( 
https://docspace.corp.redhat.com/docs/DOC-132902 ) that I believe that 
we should update to split in two categories ( desired and mandatory ).

The definitions bellow are what I see differences across JBoss projects:
  - package and groupId name (of course) - We already defined that using 
org.jboss.quickstarts.(eap|wfk|...) is optional from other Quickstarts 
(not JDF) but should be consistent within the product
  - License Headers
  - Spacing and Indentation formats

What do you think? Is it it desired to be more or less restrictive for 
other quickstarts and also turn it in an automated pattern?

I'm bringing this discussion mainly because it is a recurrent discussion 
for remote projects like
- Infinispan: 
https://github.com/infinispan/jdg-quickstart/pull/20#issuecomment-20968520
- GateIn: 
http://transcripts.jboss.org/channel/irc.freenode.org/%23jboss-jdf/2013/%23jboss-jdf.2013-06-21.log.html#t2013-06-21T13:39:31
- And probable new others like BRMS, Fuse and Switchyard Quickstarts.

-- 
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576

Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jdf-dev/attachments/20130715/84da28a3/attachment.html