The reinstallation of the shared library should have no effect on already installed artifacts. Components should be shut down and restarted just after that. What kind of problems do you experience ?
Anyway, you're right. Update of pre-installed dependencies should be optional, i guess. Could you raise a JIRA ? On 9/27/06, robottaway <[EMAIL PROTECTED]> wrote:
Would it be possible with the current plugin to specify the exact dependencies that you want deployed when using the 'mvn jbi:projectDeploy' goal? This maybe could solve the problem that stems from the maven goal trying to remove share libraries that are in use on the running Smix instance. Maybe it would be easier to just allow excluding of the ones you wouldn't want to be deployed, or even a command line list passed as a parameter to the plugin. What about the possiblity of having the plugin check for usage of the shared component before it tries to remove it. If it is installed and in use could it just skip trying to remove it? gnodet wrote: > > I guess this comes from some modifications in the jbi-maven-plugin > for handling shared libraries. It only includes artifacts with a "jar" > packaging type, and components are "jbi-components". > Could you try modifying the jbi-maven-plugin and remove the check > for "jar" (in GenerateComponentMojo.java, line 191) and see if it > works better ? > -- View this message in context: http://www.nabble.com/servicemix-jsr181-doesn%27t-get-boundled-in-install-package-tf2345068.html#a6528611 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
