Dear Fop-Devs,
Jeremias is right - you actually need to use the output of these
reports. At this time there are:
1849 checkstyle violations
18702 pmd violations
possible (find)bugs.
Many of these could be automatically solved using the eclipse
cleanup tools (which can actually be called
https://issues.apache.org/bugzilla/show_bug.cgi?id=45189
Summary: No line-wrapping when using keep-together in table-row
Product: Fop
Version: 1.0dev
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: major
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-fop has an issue affecting its community integration.
This issue affects 1
https://issues.apache.org/bugzilla/show_bug.cgi?id=45189
--- Comment #1 from Sean Griffin [EMAIL PROTECTED] 2008-06-12 05:52:17 PST
---
I'll leave it to the liberty of the FOP developers to mark this as invalid, but
it's invalid. If you're setting the keep-together=always then I believe
https://issues.apache.org/bugzilla/show_bug.cgi?id=45189
Jeremias Maerki [EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
That's obviously Retroweaver that causes the failure here. The fix in
[1] is easy but: Max, why did you add retroweaver to Trunk while we were
not yet in agreement if the experiment should be done in a branch or not?
I clearly stated my preference.
[1]
I'm scared by the thought of having a program clean our source code
changing lots of files. I prefer the approach that the devs shall try to
improve the code while they are working on it.
BTW, I think there's one or two rules in our Checkstyle file that
probably should/could be removed. For
https://issues.apache.org/bugzilla/show_bug.cgi?id=45189
--- Comment #3 from Sven Schneider [EMAIL PROTECTED] 2008-06-12 07:57:33 PST
---
Thanks, you're right, of course. It's not a bug, it's a feature :-)
A feature, which was missing in 0.94, so I didn't realize ;-)
Now I'm happy again
Jeremias,
I've removed the reference to retroweaver to fix this bug.
What I tried to do was to add the verify task of retroweaver, not
the weave task. Verify will check if all the classes are available
in 1.4, which is something we should definitely to, even for the
current trunk. It was
Oh, I see. Forgive my ignorance of the various capabilities of
Retroweaver. In that case, I've added (rev667213) the necessary entries
to the Gump descriptor. You see, Gump is special. It doesn't just use
the bundled dependencies but always takes the newly created builds from
the projects FOP
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project xml-fop has an issue affecting its community integration.
This issue affects 1
11 matches
Mail list logo
