Hello Devrim,
I've got a functioning spec-file, but I have a question which I think needs to be answered before contributing my spec-file changes (which I'm not quite sure how to do for pgrpms-- I couldn't find a mail-list).
The question has to do with the new build being dependent on maven instead of ant.
Typically, with a spec file it is expected that we could address this with the following line:
BuildRequires: maven >= 3.0.0
However, there's a problem. Maven isn't generally packaged as an RPM. In fact, even the official RHEL docs point to the maven project site for installation, and that's via tarball unzipping. I found an abandoned java project where somebody tried RPM-ing maven, but they abandoned the project somewhere with maven 2.x, and personally I could not get it to build.
So, I figured I'd try another approach. The other method that I've seen for setting a dependency is to do something like the following:
BuildRequires: /usr/bin/mvn
However, even that doesn't work for me. I keep getting that the dependency isn't found, when it's definitely there on my system. Note that I have seen that syntax under a "Requires" line (not BuildRequires) in a couple of spec files before, but they were in an ifdef block, so they may not have even been a valid syntax that was tested.
I guess I'm not sure what the right approach here is. If I leave the maven dependency off, that's not the correct answer, as it's definitely a requirement (more specifically, maven 3.x). However, I'm not sure what I can do to make the spec-file recognize this build dependency.
Note that I'm happy to take this to another list if that's appropriate, or have an offline discussion if that makes sense.
Thank you,
-John
