Skip to content

decouple xlsb from xmlbeans#1043

Open
tballison wants to merge 2 commits intoapache:trunkfrom
tballison:decouple-xlsb-from-xmlbeans
Open

decouple xlsb from xmlbeans#1043
tballison wants to merge 2 commits intoapache:trunkfrom
tballison:decouple-xlsb-from-xmlbeans

Conversation

@tballison
Copy link
Copy Markdown
Contributor

This attempts to decouple xmlbeans from xlsb.

The one area of concern I have is the public api change:

XSSFSheetXMLHandler.SheetContentsHandler.cell(String, String, XSSFComment) → cell(String, String, Comment)

This is:

  • Source-compatible: Comment is a supertype of XSSFComment, so existing implementations that reference XSSFComment just need to change their parameter type and recompile
  • Binary-incompatible: Any compiled code implementing SheetContentsHandler will need recompilation against the new version

If this is a bridge too far, we can try to refactor in another way.

* @see #doubleCell(String, double, Comment, ExcelNumberFormat)
*/
void stringCell(String cellReference, String value, XSSFComment comment);
void stringCell(String cellReference, String value, Comment comment);
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these are breaking changes - we have a policy of deprecating APIs and later removing them

Can we keep the XSSFComment methods and deprecate them adding the Comment overloads?

Add @Removal annotation to the deprecated methods (v7.0.0 removal). @since 6.0.0 to the new methods.

If methods are not public then it is ok to change them without this deprecate and overload approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants