#251 Changing of BR: maven to BR: maven-local
Closed: Fixed None Opened 11 years ago by sochotni.

As mentioned on devel mailing list[1], Maven maintainers would like to move things away from using BR: maven to using BR: maven-local. That will allow us to provide much better experience using Maven in Fedora 19+.

Packages will not see any change for their builds. Scripts were just moved to maven-local. Currently maven Requires maven-local to pull in those scripts and build requires.

Ideally we'd like to coordinate this change with Mass rebuild that's supposed to happen on 8th February so we don't cause unnecessary rebuilds (around 500 packages are affected[2]).

[1] http://lists.fedoraproject.org/pipermail/devel/2013-February/178017.html
[2] https://fedoraproject.org/wiki/Fedora_19_Maven_Rebuild


If maven already Requires: maven-local , then what's the rush?

In particular, what's the harm for packages that continue to do BuildRequires: maven instead ?

(As for guildelines update, I'm ok with the one line fix, +1 )

Here's a part of maven spec file:
{{{

Require maven-local for now to allow a smooth transition from maven

to maven-local. Once packages start requiring maven-local directly

the Requires below should be removed.

Requires: maven-local
}}}

Requirement on maven-local is temporary only to allow smooth transition. In Fedora 19 we would like to remove this dependency to keep maven package as small as possible, without any extra dependencies.

If we just removed the dependency from maven package then most of 500 Java packages would FTBFS. An automated mass migration from maven to maven-local is the best solution IMO.

Do you have any provenpackagers in java-sig that can help implement this?

Otherwise, I'd strongly suggest keeping that Requires around for f19 release, remove in f20 time-frame.

meh, maybe not strongly, but you get the idea. i've no qualms about doing it sooner, provided there's enough folks able and willing to fix all the packages in time.

Yes, we have several provenpackagers (including me and sochotni).

We have already customized and tested mass-rebuild script used by release engineering.
We can easily use it to do the mass change, but we need this to be approved.
Provenpackager policy explicitly allows this as long as the mass change is a result of updated guidelines and announced in advance. We already made the announcement and we would like the guidelines change to be approved by FPC to keep strict compliance with the policy.

It's basically impossible with this change to break applications. If they don't build they would not build without the change either. But of course we'll be looking out for failing builds. There are more packagers in Java SIG who might be able to help if needed. Current list contains 9 people, few of them are not that active lately though (but few are missing). Still 4-5 proven packagers around.

I've had a talk with dgilmore about this and we agreed on an approach if this change is approved by FPC. To not cause issues we would not run builds after this change, just commit/push the changes into all packages and let mass-rebuild do the builds themselves.

We talked about it a bit in an emergency SIG[1] meeting and general agreement was in favour of this change (noone was opposed really).

[1] http://meetbot.fedoraproject.org/fedora-meeting/2013-02-05/java_sig.2013-02-05-16.05.log.html#l-34

Approved (+1:8, 0:0, -1:0)

Announcement:

Changed the Java Guidelines to reflect BuildRequires: maven-local (instead of maven).

https://fedoraproject.org/wiki/Packaging:Java#maven_3

Metadata Update from @sochotni:
- Issue assigned to spot

7 years ago

Login to comment on this ticket.

Metadata