[Bug 167525] Review Request: cpptasks

[bugzilla at redhat.com]

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=167525


Jerry James <loganjerry at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|fedora-review?              |fedora-review+




--- Comment #10 from Jerry James <loganjerry at gmail.com>  2009-08-28 14:07:21 EDT ---
> Well, I don't know. It needs the clirr plugins, so it isn't going to build at
> the moment. I must admit I find maven somewhat opaque, and am not overly keen
> on packaging clirr. If it gets packaged, I will update however.

I've had a look, and clirr just isn't going to happen for Fedora.  First, it's
a dead project.  Second, it only builds with maven1, NOT maven2.  But it's not
needed for building the manual, anyway, is it?  I think we can just patch the
clirr-related parts out of build.xml.

> >Is there a reason for not building with gcj? 
> Sorry, not sure why this needs to be done.  If licencing is the concern, Sun's
> javac has been free (as in software) for quite a while now, I believe since F9.
> I note that packages such as maven2-plugin-release use OpenJDK in preference to
> gcj...

Last I heard, OpenJDK on PPC/PPC64 is 1 or 2 orders of magnitude slower than
gcj-generated code.  GCJ support is not a MUST item, so I won't block the
review on this point.  Personally, I'd be happy to see gcj-compiled code go
away and all Java packages become noarch.  For that to happen, though, the
speed problems with OpenJDK need to be fixed.  I don't know who is working on
that or what the status is.

So, going over the list again, java-devel still isn't a BR, but it's pulled in
by ant, so I guess that's okay.  Everything else is fixed, so this package is
APPROVED.

-- 
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.