----- Original message ----- > Hi Reto > > Currently we are not using sourcebundles because of different > problems.(Amongst others, issues mentioned in the other thread: > storing BLOBs in a graph): sourcebundles is independent of where the js,css and ssp are stored. The recommended for every bundle is to place web resources in CLEREZZA-INF/web-resources which causes them to be large literals in the graph. > > - updating ssp, js and css is slow (takes about 5-10sec) yes, as mentioned in my previous mail we could add a mechanism to allow a CLEREZZA-INF/web-resources folder on an fs location.
> - no support with java or No documentation how to do it in a java > project containing ssp. True, dynamic compilation is harder to implement with java, we might use a sling bundle for this. > - we are not using clerezza console because of instability. Also on > our server it is risky because there are no possibility to restrict > the functional range of the console for admins (e.g. admin can delete > all graphs from the console). There is an argument not so start a console shell, maybe this should be the default. But admins can destroy things with the felix-console as well (uninstall tdb.storage) > futhermore if somthing is executing on > the clerezza console it is not possible to enter other commands. You can have multiple shell by connecting via ssh. In general i think the clerezza console is great during development, administrative tasks on a production system are easier using the felix webconsole > - We have no experience with source bundle and how to use it. At the > moment the process to install and use it seems to be quite complicated > for an unexperienced developer. > I'm focusing on making this easier. You launch clerezza, you enter a command with a path to a directory and you start playing. > => Using file:/// to install bundles and thus reference files from the > file systen is still the best way for us (requesting a resource via > browser compiles the ssp and retrieves the current js and css). > > > > This looks identical to the existing project in archetypes, do you > > > know how > > to make an actual maven prototype out of it? > > I am not sure what Oli and your are talking about. Is there a > missunderstanding? Oli are you talking about something related with > the maven archetype plugin? (check: > http://maven.apache.org/guides/mini/guide-creating-archetypes.html) exactly, i was wondering if such an archetype to be used with maven to create the skeleton is still needed if such a skeleton can be create on the console. Apparently it still is, so it would be great if somebody could improve the project to be an archetype and show up in maven when a new project is to be created. Reto > > Cheers > Tsuy > > > On Tue, Mar 15, 2011 at 9:45 AM, Oliver Strässer > <[email protected]> wrote: > > oh, sry > > I have no idea, how to generate such a project structure with a > > skeletin ________________________________________ > > Von: Oliver Strässer > > Gesendet: Montag, 14. März 2011 12:40 > > An: [email protected] > > Betreff: AW: Skeleton projects and maven archetypes or from > > command-line > > > > yes > > > > -----Ursprüngliche Nachricht----- > > Von: [email protected] [mailto:[email protected]] Im Auftrag von Reto > > Bachmann-Gmuer Gesendet: Montag, 14. März 2011 10:08 > > An: [email protected] > > Betreff: Re: Skeleton projects and maven archetypes or from > > command-line > > > > On Mon, Mar 14, 2011 at 9:29 AM, Oliver Strässer < > > [email protected]> wrote: > > > > > goog idea reto > > > > > > don't forget a ontology project. > > > I think, all skeleton needs to be available as maven prototyype as > > > well. so that we could create all clerezza necessary projects > > > structures in netbeans or an alternative DIE, too. > > > > > > is the following projectstructure possible?: > > > > > > main project (group) > > > module core > > > src > > > pom.xml > > > ... > > > > > > module ontology > > > pom.xml > > > .... > > > pom.xml > > > > > > This looks identical to the existing project in archetypes, do you > > > know how > > to make an actual maven prototype out of it? > > > > Cheers, > > Reto > > > > > > > > > > cheers > > > oli > > > > > > > > > > > > > > > -----Ursprüngliche Nachricht----- > > > Von: [email protected] [mailto:[email protected]] Im Auftrag von Reto > > > Bachmann-Gmuer > > > Gesendet: Samstag, 12. März 2011 11:45 > > > An: [email protected] > > > Betreff: Skeleton projects and maven archetypes or from command-line > > > > > > Hello > > > > > > I'm writing some code to be able to create skeleton projects from the > > > clerezza console, this is specially usefull in combination with > > > sourcebundles as the newly created project is installed as > > > source-bundle and > > > you can start playing seeing the effect of your source-code changes > > > right away. > > > > > > I'm not sure if I should support multiple project types like this > > > and/or if some of these should also be available as maven prototype. > > > I'm thinking to support the following project types > > > - scala with activator > > > - scala with declarative services > > > - java with ssp > > > > > > the last project is what we currently have as skeleton project, as > > > it uses java it doesn't yet work with source-bundles. So I'm not > > > sure if its better to keep this make this a maven archetype (as > > > planned, but I think some magic > > > is still needed for it to be an archetype) or if it should be > > > created via a command-line command (I think it might be hard to > > > support both ways without code duplication). > > > > > > Cheers, > > > Reto > > > > >
