Hide Forgot
Title: Customizing OSE cartridge template needs to modify its pom.xml Describe the issue: If we cutomize the JBoss EWS or EAP cartridge by following documentation step[1], its groupId, artifact, etc in pom.xml have "template". The doc should say that and how to solve it. I linked [2], since I think [2] is good reference to fix doc. [1] https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html/Deployment_Guide/chap-Customizing_OpenShift_Enterprise.html [2] http://sosiouxme.wordpress.com/2014/02/18/customizing-openshift-jboss-confs-without-customizing-the-cartridge/ ~~~ Edit the pom.xml file. This is optional, but you may want to use a different groupId, artifactId, etc. than just the “template” app name. It’s possible to use env vars here, e.g. <groupId>${env.OPENSHIFT_APP_DNS}</groupId> ~~~
While it's true: ~~~ It’s possible to use env vars here, e.g. <groupId>${env.OPENSHIFT_APP_DNS}</groupId> ~~~ ... please note the caveats that come after that too :) (eternal maven warnings and possible removal of the feature). It works fine, probably will continue to do so, but people should know to expect the results.
This issue will be addressed in the next docs publication, should be within the next week, or at least end of current sprint (4/10/15). Will update status here again when published.
Updated docs have been published: https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#Creating_an_Application_Template