On 2012-04-20 15:52:39 (+0200), Ludwig Nussel
Johannes Weberhofer wrote:
A great thing would be, when the OBS could run the maven tool using it's download feature! The the complete packaging process could be done in OBS very easily, but external jars would be downloaded from their maven repos.
What about patching that tool to produce .spec file for those deps instead? Similar to how perl module packages are created these days.
Not quite the same: * perl builds can pull dependencies from CPAN when you build, similar to Maven, in a way, but that is _not_ what we make spec files from: * we let perl module builds break on missing dependencies and then generate spec files for those manually, one by once, using metadata from CPAN Patching Maven to produce spec files is very different from what we do with Perl modules. There are several things that we can do, of course, such as to extract dependency information from POM files. It's just XML. I did a proposal and even a naive implementation (as a Perl script) that uses that data to create RPMs of java bits using binaries. (as a proposed intermediate solution) It is difficult to do anything like that at build time though. You run mvn to package some Java library. Maven analyses the POM file to see which dependencies are needed. It pulls those dependencies (binary bytecode, not sources that it will build too, it's not gentoo's "make world" ;)) from the internet or from custom Maven repositories. So then we would need to implement some mechanism on Maven that, instead, would say "okay, stop here, we don't have this, package this first". That would then be similar to how we handle Perl modules (or Ruby gems or Python .. erm.. bits of cheese for that matter). Would be a bit awkward though, as we'd transform or even remove one of the key elements of Maven :) cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- we haz green _\_v http://fosdem.org -- we haz conf