Hi Rob Robert Vesse wrote: > There's nothing to stop us making LARQ generate an uber-jar in the same > way we do for Fuseki with maven shade is there? > > This would be sufficient for users if they only had to drop in a single > extra JAR into a directory - most users can manage that ;-)
My 0 hasn't flipped to +1, but if you need that feel free to go ahead. > Yes that is my concern that we're making users jump through a lot of hoops > to extend things Yep. > I thought assemblers can be used to get arbitrary classes loaded so can > you not theoretically have some initializer class for the plugin (whether > LARQ or otherwise) and add lines to the assembler to get it loaded. > > It seems like assemblers would solve other current problems with LARQ such > as the ability to specify custom analyzers, index directories etc. Doing > everything via assembler seems the logical way to go for plugins like LARQ I am by no means an Assembler expert and perhaps you are right. I hope so. If I remember correctly the problem I had was that in order to build a LARQ index, I needed a Dataset, but I did not find a way to get a reference to an object created by another assembler module from the LARQ ones. I hope I explained this clearly enough. Paolo
