On 2010-05-11 15.46, Philippe Van Dyck wrote:
Definitely ! But do you really plan to drag and drop jars file on a
production env ? I mean, how much time do you plan for the scripts ? ;-)

When we deploy in production it should be enough to just copy all bundles into the "modules" directory to install/run it.

I found no 'fully mavenized' solution ( I looked at pax:runner )
enabling redeployment and class reloading on a "shared" server...
Maven really simplifies configuration management... do you plan to use
it to deploy your server ?

BTW why do you plan to share the dev server if it is so lightweight ?

I'm not planning on having a shared dev server. Not sure where you got that idea. Each developer will have their own.

And IMHO Edward is right, osgi is really about composing "feature
bundles" together (may I say stories ?) that was the idea of the
pax:wicket project. Quite a challenge !

True, but Qi4j seems to be quite prepared for it, especially with the idea of 1 Module = 1 bundle.

I'll just have to try to find out I think.

/Rickard

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to