Based on couple of questions over the usage of deploy folder on production
seems to be not a good option.
Though I got that, I'm trying to understand the implications of using
deploy folder for production deployment instead of features.
What is the underlying cause for suggesting features.xml ins
Hi Satish,
Deploy is usable in production but I strongly advice only for atomic
artifacts. For instance, a bundle that requires bunch of dependency
bundles can be painful (deployment order, etc) in the deploy folder. kar
are mostly fine.
My preferred approach is to use features and deploy it
The main reason, as hinted by Jean-Baptiste is the fact that when using the
deploy folder, there's a much more limited control over the deployment
order of the bundles.
For example if you need to deploy 10 bundles, you copy them to the deploy
folder, but the scanner may run while copying, so it may
