https://bugzilla.redhat.com/show_bug.cgi?id=830933
--- Comment #4 from Michel Alexandre Salim <michel+fdr(a)sylvestre.me> ---
Hi Stanislav,
As discussed in the Java SIG list, sure, I understand the reasoning. Listing
several questions I asked on the mailing list, as they relate to this request:
1. any estimate for when the guideline changes will be voted on? The Clojure
feature for F18 is stalled waiting on this
2. I identified several subpackages currently generated from maven2 that are
actually broken without the compatibility maven-artifact and maven-settings --
presumably they'd have to follow these guidelines too
3. Given that the subpackages are shipped together with the Maven tarball, do
you foresee maintaining these *within* the Maven2 srpm, just with updated
packaging rules, or do you want to maintain them as separate SRPMs? As I
mentioned on the list, these subpackages are configured to pick up the version
number of the Maven used to build them, so maintaining them separately is a
hassle (as Maven2 is not installable on F17, see below)
4. Should we fix the maven package as well not to provide and obsolete maven2?
That's preventing maven2 from actually being installed at all, in which case,
we might as well only ship the compatibility subpackages and not maven2 itself.
Thanks, and sorry for all the questions!
--
You are receiving this mail because:
You are on the CC list for the bug.