On 2/24/16, 2:01 PM, "Linux on 390 Port on behalf of Pavelka, Tomas" <[email protected] on behalf of [email protected]> wrote:
>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 Yep, I assumed that but wondered when it was searching for these artifacts that it might check if it’s available on the system already. I assume I’m missing a POM file somewhere that should get installed with the log4j RPM so that maven can find things. > >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. The mock environment “should” have network access but that’s a good thing to check. Thanks! > >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. ---------------------------------------------------------------------- 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/
