Felix Meschberger wrote:
Hi Carsten,
Am Dienstag, den 29.04.2008, 17:28 +0200 schrieb Carsten Ziegeler:
Hi,
So, wrapping up:
a) "commons" is a place for common code/bundles which is not directly
tied to Sling (but used by Sling)
b) We move the stuff from the "osgi" dir to "better places"
c) osgi/assembly -> sandbox
d) osgi/commons -> commons/osgi-util
e) osgi/console-web -> Apache Felix
f) osgi/log -> commons/log
g) osgi/obr -> sandbox
We might want to (1) offer this also to Apache Felix and (2) rewrite it
as a "plugin" for the sling console ??
Ah, yes, good ideas.
There is one more sling ehrm thing: the maven-sling-plugin contains
multiple goals, which we might want to split into separate plugins:
(1) assembly: This would be a maven-assembly-plugin which would
have to be placed near the assembly module. We might create
a .../whiteboard/assembly folder and place the assembly bundle
and the new maven-assembly-plugin in there
+1
(2) install: installs a bundle into a running Sling instance.
This is somehow related to the console as it uses the "Web API"
of the console. Shouldn't we also offer this part to Apache
Felix ?
+1
(2) deploy: deployes bundles into a Sling OBR server. This is
related to the obr bundle. If the obr bundle is redone as a
console plugin, we might offer this part together with the
install part to Apache Felix.
+1 - isn't the maven-bundle-plugin able to do this already as well?
(3) install-properties (in the WarMojo class): What is this used
for ??
That's related to the assembly stuff...it adds the required assemblies
for a webapp to the properties file.
Does this make sense?
+1. Thanks for taking this up.
I'll add some jira issues and start work on them asap.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
