If my post appears twice, accept my appologies.. I am not sure my previous message was posted. Some kind if strange behaviour....
Anyway, the question was about deploying bundles to an instance of Virgo web server through Eclipse. I am wondering what happens behind the scene when deploying a new bundle, either by Add or Remove link on the context menu of the server, or drag&drop a project to the server instance.
The reason why I am asking this question is that I have noticed that the jar that is copied to the stage directory of Virgo is not the jar that is generated by my maven build. To be more specific : the MANIFEST file inside the jar under stage, and the one embedded in the jar generated by maven is different. So I'm wondering where this jar comes from? Is it automatically build by Virgo? How does Maven interacts in this process?
The Eclipse-based Virgo tooling puts the bundle in the stage directory and drives Virgo's JMX Deployer interface to deploy the bundle. So this behaviour seems to be due to the tooling. I would normally try the usual Eclipse "dances" to get back to a predictable state. (Once we have the tooling donated to Eclipse, we'll be in a better position to debug these kinds of issues.)