[Bug 594416] Review Request: json-lib - JSON library for Java

bugzilla at redhat.com bugzilla at redhat.com
Fri Jul 23 17:35:26 UTC 2010


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=594416

--- Comment #8 from Lubomir Rintel <lkundrak at v3.sk> 2010-07-23 13:35:25 EDT ---
(In reply to comment #6)
> Oh, while you're at it:
> BuildRequires:  maven2-plugin-compiler
> BuildRequires:  maven2-plugin-install
> BuildRequires:  maven2-plugin-jar
> BuildRequires:  maven2-plugin-resources
> 
> These are maven-X-plugin in rawhide now (old names are provided...but it's
> still best not to introduce them in new packages)    

I usually care more about my source packages (including those from rawhide)
being as "portable" that about cleanliness (e.g. I still don't drop BuildRoot
tag unless I'm absolutely sure there's no chance the package will ever be built
on el5).

Thus, for the time f13 is supported I'd like to leave it as it is (might it be
a good idea to bulk-fix it in all packages afterwards?). If el6 is going to
ship 2.0.8 maven (or whichever version is one that precedes f14), I'd like to
keep it as it is for its lifetime.

That said, and probably off topic of this bug, more than week ago I asked the
owners of the packages of the maven stack (ccing the java list) for help
including maven2 stack in EPEL-6, but did not get a reply for most, thus I'm
probably going to push the packages there myself. If I understand correctly
you've been much involved in refreshing the maven stack in Fedora recently,
thus you probably could be of tremendous help getting maven stack (either f13
or f14 one) into EPEL for el6. What's your opinion on that?

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the package-review mailing list