Brian Leathem commented on Feature Request JDF-592

I was thinking of a comment syntax we could use that qstools could uncomment, however this would complicate the pom of the quickstart which defeats the usefulness of the quickstarts as a learning tool.

<applyPatch/> would be brittle, with the patch file having to be adjusted as changes are made to the pom. However if we used a custom patch syntax, where the substitution was made accoding to commented markers in the pom then it would be more robust. Something like:

pom.xml
<!-- #enterprise versions of the BOM dependencies -->
        <version.richfaces>${richfaces-enterprise-version}</version.richfaces>
        <version.jboss.bom.eap>${jboss-bom-enterprise-version-eap}</version.jboss.bom.eap>
        <version.jboss.bom.wfk>${jboss-bom-enterprise-version-wfk}</version.jboss.bom.wfk>
<!-- /#enterprise versions of the BOM dependencies -->
substitutions.xml
<enterprise>
#if ($enterprise == "true" || $enterprise == "y" || $enterprise == "yes" )
        <version.richfaces>${richfaces-enterprise-version}</version.richfaces>
        <version.jboss.bom.eap>${jboss-bom-enterprise-version-eap}</version.jboss.bom.eap>
        <version.jboss.bom.wfk>${jboss-bom-enterprise-version-wfk}</version.jboss.bom.wfk>
#else
        <version.richfaces>${richfaces-version}</version.richfaces>
        <version.jboss.bom>${jboss-bom-version}</version.jboss.bom>
#end
</enterprise>

In this proposal, the <Unable to render embedded object: File (-- #enterprise --> ... <) not found.-- /#enterprise --> comments mark the boundary of the substitution with the id enterprise. The substitutions file then provides the replacement code identified by the substitution code.

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