Hi Sergio, Thank you for your reply >> What would you recommend to make those modules available to the >> community ? and what do we technically need to do ? > >I'd say create individual repositories at github with each module. Or
>even better, group all together under a common repository that includes >a marmotta webapp launcher with your modules. Well, it was good for me to create a fork from beginning, being able to consult Marmotta's source which did inspire me for some functionalities, and finally I do have one file from Marmotta that was modified to add a new feature in the LD-Client, so I would like to keep the current fork which is available here: https://github.com/FabianCretton/marmotta > >> As a simple test, I did download the new Marmotta 3.3.0 installer, >> but when I add the module's .jar file to >> "apache-tomcat-7.0.53\webapps\marmotta\WEB-INF\lib", then Marmotta >> will fail to start-up. I guess this is normal. > >No, it should load the modules, as soon as you also copied all required >dependencies. Any stacktrace to debug the issue? Thank you Sergio, it does work, I was missing one of the library but now my modules run in Marmotta 3.3.0 with very little "effort" >> Also, the modules need their own folders in Marmotta's home. When >> starting the service of the module, those folder will be created by >> the module if they don't exist yet. But some files will be required >> in those folders and I would like to know if their is any "easy" way >> to distribute those files on the first launch (for instance copying >> them from the .jar content), or if an installation programm would be >> more "clean" ? > >I guess we do not provide the basic infrastructure for such tasks. But >you can easily implement it observing the SystemStartupEvent. Although >it's for something else, the code for copying a custom template might be >relevant for you (I guess it's the same business): >http://wiki.apache.org/marmotta/Customizing#Templates > >> The simplest solution if someone would like to test/use the modules >> would be: just place the .jar in "\webapps\marmotta\WEB-INF\lib", >> but maybe that can't be so simple ? > >The problem is the dependencies, as I pointed above. As I don't have much time to work on such modules distributions, I was thinking about a very simple solution, please tell me how it sounds: I will add one "distribution" folder to my github, in this folder I will simply have one folder for libraries to put in "WEB-INF\lib", namely my own modules, their dependencies, and also the corresponding "ldclient-provider-rdf-3.3.0.jar", and one subfolder that should be placed in %marmotta-home%. By copying those 2 folders, one would install very simply the modules in Marmotta 3.3.0. Does it sound reasonable ? it seems the less time consuming for me and very easy for users. I do have another question about my version of "ldclient-provider-rdf-3.3.0.jar". I understand currently this way of doing things, namely to have added RDFFileProvider/RDFFileEndpoint might not be very practical for further updates. One thing that annoy me is that there is no way to know which version of the file is in the "lib" folder by looking at its name, as both, Marmotta's file and overLOD version are called "ldclient-provider-rdf-3.3.0.jar". Is there something I could improve here ? Thank you for your advices Fabian > >Let's keep talking how to support you on this. > >Cheers, > >-- >Sergio Fernández >Senior Researcher >Knowledge and Media Technologies >Salzburg Research Forschungsgesellschaft mbH >Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria >T: +43 662 2288 318 | M: +43 660 2747 925 >[email protected] >http://www.salzburgresearch.at > >-- >Sergio Fernández >Partner Technology Manager >Redlink GmbH >m: +43 660 2747 925 >e: [email protected] >w: http://redlink.co >
