On 3/19/2014 10:00 AM, [email protected] wrote:
https://issues.apache.org/bugzilla/show_bug.cgi?id=56282
--- Comment #4 from Marco Lehmann-Mörz <[email protected]> ---
(In reply to Nick Burch from comment #3)
As the FAQ states, if something is missing, we need a unit test that uses
the missing part, then it'll get included in future. Bonus marks if the unit
test checks something useful :)
I think we don't understand each other:
If STTextFontAlignType$Enum.class is included, STTextFontAlignType.class MUST
be included for the very same reason(s).
He understands, but what you don't understand is that if nothing (no
unit test) tests anything in the missing class, the build process
doesn't think that class is necessary. If there is a unit test that
uses the class, then it will be included. As he said, if the unit test
does something useful beyond just checking the existence of a class,
then that's a bonus.
What I try to achieve:
We have an Eclipse RCP application where we need to create OOXML files.
I want to build an OSGi bundle / Eclipse Plug-in that contains org.apache.poi +
ooxml-extensions.
To compile all classes and build a proper bundle I need poi-ooxml-schemas.jar
(which I do reference in my maven/tycho build).
The compilation fails with complaints about the missing class I mentioned
above.
Unfortunately, I already deleted my experiment and switched back to my working
version 3.9. :-(
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
