[richfaces-issues] [JBoss JIRA] (RF-13274) Use QSTools:archetypeSync to keep the kitchensink archetype synchronized with the kithensink-rf quickstart

[Brian Leathem (JIRA)]

    [ https://issues.jboss.org/browse/RF-13274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934596#comment-12934596 ] 

Brian Leathem commented on RF-13274:
------------------------------------

QE: please make sure the project generated from this archetype still works for both the community and enterprise use cases (I've only checked the community use case myself).
                
> Use QSTools:archetypeSync to keep the kitchensink archetype synchronized with the kithensink-rf quickstart 
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: RF-13274
>                 URL: https://issues.jboss.org/browse/RF-13274
>             Project: RichFaces
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Leathem
>            Assignee: Brian Leathem
>              Labels: needs-qe
>             Fix For: 4.3.5
>
>   Original Estimate: 3 hours
>  Remaining Estimate: 3 hours
>
> As per [~rafabene]'s description in IRC:
> {quote}
> use QSTools:archetypeSync to keep your Archetype Synchornized with the kithensink-rf Quickstart as we did for our Archetypes
> look at an example here: https://github.com/jboss-developer/jboss-eap-archetypes/blob/master/jboss-javaee6-webapp-archetype/pom.xml#L82-L106
> you tell where the quickstart is projectGitRepo projectPath
> tell what's your branch or commit or tag
> them what's your rootPackage
> you can configure expression that will be replaced by $\{artifactId} with archetypeExpressionReplaceValues
> so every fix that you make on Quickstarts will be available on your next Archetype build
> call me if you have any issues with QSTools:archetypeSync
> {quote}

--
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