Yeah, I agree that the behavior is not very intuitive. Note the command should now be able to run from a top level project. In which case, I think all deployable artifacts should be updated, but all dependencies should not unless the -DforceUpdate=true flag is set.
On 8/9/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote: > L.S., > > > By default, this command doesn't seem to update anything that is already > installed/deployed. I would have expected that by default for a service > assembly: > - it installs any dependencies (components and shared libraries) that > aren't already installed, but doesn't update them > - it deploys the service assembly or updates it if necessary > > You can specify -DforceUpdate=true, but this will also update the JBI > components that were already installed (possibly causing other SA to be > restarted in the process) while they probably haven't changed if you're > using a released version of ServiceMix. > > > Gert > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
