The work to configure and get the module only needs to be done
      ones - a module will never "unresolve" unless you undeploy it.
11:18:05 PM) tdiesler:
          Nihility, for osgi the behavior for a bundle deployment that
          cannot resolve would be such that the deployment does not fail
          but it hangs in some pre_module phase. you could deploy
          additional stuff and retry to resolve/start the thing through
          the console. It is metadata valid and stays in the runtime as
          such. 
(11:18:54 PM) tdiesler:
          That would solve all ordering issues I think
(11:19:42 PM) Nihility:
          yeah so like if we had a dep on another deployments MODULE
(11:20:03 PM) tdiesler:
          you dont get an error
(11:20:08 PM) Nihility:
          that would do what you are talking about
(11:20:13 PM) tdiesler:
          yes
(11:20:13 PM) Nihility:
          it just waits
(11:20:29 PM) Nihility:
          of course we have a circularity problem to think about 
(11:20:37 PM) Nihility:
          I'm not sure if we support this today or not
(11:20:58 PM) Nihility:
          but i wonder if a.jar (dependency b) b.jar (dependency a)
          works for modules
(11:21:04 PM) Nihility:
          we make it work for class-path
(11:21:15 PM) Nihility:
          since Class-path is supposed to allow it
(11:21:32 PM) Nihility:
          it works in jboss modules
(11:21:41 PM) Nihility:
          but as a deployment module dep I'm not sure
(11:21:51 PM) Nihility:
          stuartdouglas: would know, are you up?
(11:22:19 PM) Nihility:
          tdiesler: i take it thats completely invalid with bundles
          right, circularity?
(11:22:39 PM) tdiesler:
          Nihility, it works in osgi. because the resolver knows the
          complete set of metadata. and when triggered to resolve a set
          of bundles and it finds a cosistent solution we go to the
          jboss-modules PAI
(11:23:10 PM) tdiesler:
          Nihility, I don't think so
(11:23:24 PM) Nihility:
          ah ok
(11:23:37 PM) tdiesler:
          Require-Bundle is of course discouraged anyway, but it should
          work 
(11:23:58 PM) Nihility:
          tdiesler: you can do it with packages too right?
(11:24:12 PM) tdiesler:
          yes
The default behaviour for a bundle deployment would be "don't
      fail on cannot resolve". For other deployment types it could be
      different as it is now. An explicit start op would take the
      deployment past the resolve phase and through the activate phases.
      If it still cannot resolve you'd get an error.

      
      On the CLI you can do:

      
      > deploy foo.jar --no-start (which means it is ok that foo
      cannot resolve)

      > deploy bar.jar

      > start foo.jar (which means that foo must resolve and start
      without error)

      > stop foo.jar (which means that foo runs back through the
      activate DUPs only - it stays resolved and keeps the module)

      
      The cleanup issue only becomes a problem if you want to do
      repeated start ops.

    
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx