> I do want to add a blast from the past to this thread: > > On 02/17/2012 10:49 AM, Carlo de Wolf wrote: > > I just would like to see maven artifacts 'properly' installed in > > /usr/share/maven/repository. > > Then we can let upstream maven (and other tools) use that. > > > > Carlo > > It would need an extension to be able to use that repo if we let the pom > fall in unchecked. > Something like https://github.com/fmvn/foss-maven. > > But ultimately such a repository should be fully valid to the rules of > Maven. > We could use a tool like https://github.com/jdcasey/repository-validator > to assert that. > > The only and very important gap is getting from 'world consuming' poms > to sanctioned repo poms in some sort of automated way. > > Ultimately it would fall in the area of concern your tool is covering. I agree it would be best if we could easily create a valid Maven repository from our RPMs and I am not discarding this at all. But maybe having incremental step is easier to implement and moves the requirement to install Maven artifacts away from package maintainers and in the control of system-wide script. That way when we figure out a safe and sane way to create said Maven repo, it's going to be just one mass-rebuild away. It's possible I am overanalysing problems with creating that Maven repo, but in any case it's possible to just build on top of mvn-rpminstall and create our repository one step at a time. -- Stanislav Ochotnicky <sochotnicky@xxxxxxxxxx> Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc. http://cz.redhat.com -- java-devel mailing list java-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/java-devel
