Maven 3 script changes

[Stanislav Ochotnicky]

I just built a new maven 3 package. It provides one more script called
mvn-rpmbuild.

mvn-rpmbuild should be used in spec files. It does same magic as
previously mvn-local (and mvn-jpp) did. I runs maven in offline mode and
therefore will not download artifacts under any circumstances, but it
will use those available in /usr/share/java. You also don't have to set
maven.repo.local variable, it is set automatically to $(pwd)/.m2. This
should save you a few keystrokes when writing spec files.

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. Nothing bad will happen, but it won't work anymore :-)
mvn-local uses $HOME/.m2 for artifacts so it should not conflict with
upstream maven too much if used together.

Another change is "maven.jpp" prefix change to "maven.local"  for
properties. This means that -Dmaven.jpp.depmap.file=XXX will have to be
changed if you've been using it. Other than that I don't expect any
changes should be necessary.

FYI, maven 3 can now rebuild itself so expect proposal to change
guidelines so that we'll start using maven 3 to build packages unless
it's not compatible.

Happy java packaging :-)

-- 
Stanislav Ochotnicky <sochotnicky(a)redhat.com&gt;
Associate Software Engineer - Base Operating Systems Brno

PGP: 7B087241
Red Hat Inc.                               http://cz.redhat.com

[Guido Grazioli]

2011/2/10 Stanislav Ochotnicky <sochotnicky(a)redhat.com&gt;:
>  I just built a new maven 3 package. It provides one more script
> called
>  mvn-rpmbuild. 
>  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?

Cheers

-- 
Guido Grazioli <guido.grazioli(a)gmail.com&gt;
Via Parri 11 48011 - Alfonsine (RA)
Mobile: [phone] (10-18)
Key FP = 7040 F398 0DED A737 7337  DAE1 12DC A698 5E81 2278
Linked in: http://www.linkedin.com/in/guidograzioli

[Stanislav Ochotnicky]

On 02/10/2011 02:47 PM, Guido Grazioli wrote:
>  2011/2/10 Stanislav Ochotnicky <sochotnicky(a)redhat.com&gt;:
> > I just built a new maven 3 package. It provides one more script called
> > mvn-rpmbuild.
>  
> > 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&gt;
Associate Software Engineer - Base Operating Systems Brno

PGP: 7B087241
Red Hat Inc.                               http://cz.redhat.com

[Mat Booth]

On 10 February 2011 13:35, Stanislav Ochotnicky <sochotnicky(a)redhat.com&gt; wrote:
>  I just built a new maven 3 package. It provides one more script
> called
>  mvn-rpmbuild.
>
>  mvn-rpmbuild should be used in spec files. It does same magic as
>  previously mvn-local (and mvn-jpp) did. I runs maven in offline mode and
>  therefore will not download artifacts under any circumstances, but it
>  will use those available in /usr/share/java. You also don't have to set
>  maven.repo.local variable, it is set automatically to $(pwd)/.m2. This
>  should save you a few keystrokes when writing spec files.
>
>  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. Nothing bad will happen, but it won't work anymore :-)
>  mvn-local uses $HOME/.m2 for artifacts so it should not conflict with
>  upstream maven too much if used together.
>
>  Another change is "maven.jpp" prefix change to "maven.local"  for
>  properties. This means that -Dmaven.jpp.depmap.file=XXX will have to be
>  changed if you've been using it. Other than that I don't expect any
>  changes should be necessary.
>
>  FYI, maven 3 can now rebuild itself so expect proposal to change
>  guidelines so that we'll start using maven 3 to build packages unless
>  it's not compatible.
>
>  Happy java packaging :-)
>  

Cool, I will try to remember to use this the next time I update a package. :-)


-- 
Mat Booth
http://fedoraproject.org/get-fedora