I made some basic tests and I feel confortable with the sync made by QSTools, but it's always good that have another review or more tests.
This Pull Request has 3 modifications/commits
1) Remove the Blank Archetype - There's no need to keep the Archetypes on gitrepo since it's generated with release.sh script
2) Added pom.xml config that to use qstools:archetypeSync goal. The main point is that a Archetype could be synched with a branch/tag/commit - The idea is that the archetypes should use a quickstarts .Final tag on each JDF release.
3) The synchronization it self. I tested it but I would like that you test it too before I merge this PR.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
The Archetype are now kept in sync with the origin quickstart. That's made by a QSTools goal.
I would like that the following PR should be reviewed/tested for someone else: https://github.com/jboss-jdf/jboss-as-archetype/pull/15
I made some basic tests and I feel confortable with the sync made by QSTools, but it's always good that have another review or more tests.
This Pull Request has 3 modifications/commits
1) Remove the Blank Archetype - There's no need to keep the Archetypes on gitrepo since it's generated with release.sh script
2) Added pom.xml config that to use qstools:archetypeSync goal. The main point is that a Archetype could be synched with a branch/tag/commit - The idea is that the archetypes should use a quickstarts .Final tag on each JDF release.
3) The synchronization it self. I tested it but I would like that you test it too before I merge this PR.