On 02/10/2011 02:47 PM, Guido Grazioli wrote:
2011/2/10 Stanislav Ochotnicky <sochotnicky(a)redhat.com>:
> I just built a new maven 3 package. It provides one more script called
> mvn-rpmbuild should be used in spec files. It does same magic as
> previously mvn-local (and mvn-jpp) did.
> mvn-local on the other hand changed so that it WILL download artifacts
> from remote repositories if they are not available locally. This is a
> change compared to previous maven 3 packages. Please don't use mvn-local
> in spec files.
I switched my maintained packages to build with mvn-local last week.
(everything worked very smoothly, good work!).
Did the new maven3 package hit rawhide before or after the mass rebuild?
Should i change and rebuild my packages asap?
I built it just now so it didn't hit rawhide before mass rebuild. If
you've already built your package with mvn-local there is no need to
build with mvn-rpmbuild since mvn-rpmbuild is just renamed mvn-local
script from previous version.
If your (general you, not just Guido :-) ) package uses mvn-jpp, it
would be great if you could rebuild it with mvn-rpmbuild instead. But I
don't think it makes sense to rebuild your package just for sake of
rebuilding, because there is nothing gained by that (only verification
it works). So if you have a pending update, FTBFS or something
similar...try mvn-rpmbuild for a change :-)
Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Associate Software Engineer - Base Operating Systems Brno
Red Hat Inc. http://cz.redhat.com