Bug 1176970

+++ This bug was initially created as a clone of Bug #1176507 +++

Description of problem:

When force clean build marker is used all the content along with the settings.xml from .m2 directory of the gear is deleted as seen from the code: 

~~~
if force_clean_build_enabled_for_latest_deployment; then
echo "force_clean_build marker found; removing Maven dependencies."
rm -rf ${OPENSHIFT_HOMEDIR}.m2/* ${OPENSHIFT_HOMEDIR}.m2/.[^.]*
fi
~~~

Also, if we configure global maven settings.xml file as mentioned in this article : https://access.redhat.com/solutions/535653 and then create a new gear the .m2 directory  for the gear is populated with a copy of /etc/openshift/skel/.m2/settings.xml  and everything works as expected.

When we enable force clean build, the settings.xml file gets deleted along with the repository that gets created after downloading the dependencies and the next build results in fail. 


Version-Release number of selected component (if applicable):
2.2

How reproducible:
Always

Steps to Reproduce:
1.Configure global maven settings.xml file as mentioned in this article : https://access.redhat.com/solutions/535653
2.Create a new gear having jboss cartridge
3.Enable force clean build

Actual results:
The settings.xml file gets deleted along with the repository directory after enabling the force clean build


Expected results:
The settings.xml file shouldn't be deleted along with the repository directory after enabling the force clean build


Additional info:
The next time when a build is performed the settings.xml file from skel directory must be copied to the .m2 directory.

OR

In short the rm line in the code should be replaced with something like: 

~~~
if force_clean_build_enabled_for_latest_deployment; then
echo "force_clean_build marker found; removing Maven dependencies."
rm -rf ${OPENSHIFT_HOMEDIR}.m2/* ${OPENSHIFT_HOMEDIR}.m2/.[^.]*    ## Replace with: find ${OPENSHIFT_HOMEDIR}.m2/ -type f -not -name 'settings.xml' -delete
fi
~~~

--- Additional comment from RHEL Product and Program Management on 2014-12-22 02:57:30 EST ---

Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.