Felix Meschberger wrote:
Hi,
Am Montag, den 21.04.2008, 15:38 +0200 schrieb Carsten Ziegeler:
Felix Meschberger wrote
I don't know - perhaps we could define this in a separate pom and then
use the assembly plugin, or we can write a custom plugin. I've written a
plugin that assembles all used bundles (from the dependencies) and puts
them into a folder.
... from the dependencies ... : Which dependencies ? Transitive ? Would
this list then be "correct" ?
Sure, my plugin is not able to create something "incorrect" :)
The app (standalone, webapp) could have a dependency to another maven
project that just lists all contained bundles. The plugin is invoked on
the app, traverses the deps (including transitive ones) and adds the
found bundles.
The list is nearly correct, only if you have a provided dependency on a
lib that is not a bundle, the corresponding wrapper bundle needs to be
added manually. But I think, we don't have this case in Sling.
I have top admit, that this sounds fragile ... Have you considered - as
Betrand suggested - using special scopes ?
No, I haven't - and I think it wouldn't make a difference. Today you use
POMDs (plain old maven dependencies) and the plugin inspects them if
they're bundles. A special scope would do the same but require the
developer to use this scope.
It's true that we nearly never had problems with our assembly scope
itself, but on the other hand, if it's not required, it makes things easier.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
