To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=80723
                 Issue #|80723
                 Summary|jfreereport build uses prebuilt jars - shouldn't
               Component|utilities
                 Version|680m225
                Platform|All
                     URL|
              OS/Version|Linux
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|oj
             Reported by|rene





------- Additional comments from [EMAIL PROTECTED] Thu Aug 16 08:04:13 +0000 
2007 -------
Hi,

I always wondered where jcommon-1.0.10.jar and sac-jar came from as I didn't see
them being built but I just thought I oversaw something...

But now, while updating Debians libjcommon-java package (jcommon) and package
the rest (flute, jfreereport, etc) to be able to just use them I know why. 

Many of the lib*.zip source include jcommon as binary jar in their lib/ 
directory,
and some do include flute etc which they then use to build.

Equally bad, e.g. flute included sac.jar with sac.jar built nowwhere.

At least jcommon and sac should be built itself; bonus points for making
the "normal" flute build use that sac instead of the one shipped in lib/,
and the same for jcommon and other libs used by the process ( junit? )

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to