Hi Neale, I would guess that the issue is that the Maven repository is a different thing than an RPM repository: https://maven.apache.org/guides/introduction/introduction-to-repositories.html
I am also guessing there isn't anything that could turn the RPM repo to a Maven repo, but I have not tried looking for such thing. The standard practice is to simply allow maven download from Maven Central. Alternatively, if you want to have full control over what packages are used you could use something like Artifactory for your own remote Maven repo. But I think in either case you would have to give your mock build (assuming you are using mock) network access. There is also the local Maven repo which serves as a cache for the remote ones, but I don't know how you would populate it in any automated way. HTH, Tomas Tomas Pavelka CA Technologies Sr Software Engineer CA CZ, s.r.o V Parku 12, 148 00 Praha Czech Republic Office: +25996 | [email protected] Id. Císlo 25694073, z obchodního rejstříku, vedeného Městským soudem v Praze, oddíl C, vložka 61808 / Id. No. 25694073, registered in the Commercial Register maintained by the Municipal Court in Praque, Section C, File 61808 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
