During our POC, I came across an issue I am not sure how to resolve.
Our build process loads bundles/features into a local maven repo we host here. I have set up my default profile in the fabric registry to use these repositories to load bundles and features from. This works fine to deploy them out to the various containers.
However, if I make a change to a bundle (or feature) project and run 'mvn clean install deploy' to deploy it out to the repository, I cannot seem to get the fabric to redeploy the updated version to the containers that are using it. My guess is, that the fabric server sees it already has a local copy and uses that to push out to the containers.
We cannot use the maven proxy to deploy to the fabric server, since we need to store the artifacts in a maven repository so that other organizations can pull from there as well.
This is going to be critical for us during development.
What is the recommended approach for dealing with this issue?
