Hello all! I just want to share some experience that I had when dealing with all the distribution packaging. One of the first questions that come up when dealing with the packaging approach is probably the one that targets the appropriate tooling (e.g. the best maven plugin)
In the past, I've been using two different kind of plugins to package: (1) Tools that are directly tight to your OS and require certain commands such as "ln", "touch", "ls", ... (2) Tools that abstract all OS specific commands within their framework and can be executed on any OS Depending on where to place the packaging in the karaf build tree, it makes either sense to go with option (1) that may automate some parts of the packaging, e.g. the generation of control or spec files, or with option (2) where those files need to be maintained manually. Has anyone a specific idea, where to place the packaging projects? Kind regards, - Christoph On Jul 15, 2013, at 8:13 PM, Roedl Lukas wrote: > Hi! > > I know that I also could use the karaf distribution directly - but in my > setup I assemble a custom distribution (Karaf and preconfigured features and > a database template, ...) with the karaf distribution you suggested and > package it as zip/tar.gz first and then - as second step - as a windows > installer and as a debian package. So a custom distribution seemed to be the > best option to me... > > best regards, > > Lukas
