Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xpp fixes #22

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Xpp fixes #22

wants to merge 3 commits into from

Conversation

wltjr
Copy link

@wltjr wltjr commented Feb 1, 2017

Fixes a few issues with xpp. Ran into several abstract methods not implemented from XmlStartTag in ProxyXmlStartTag. Renamed removeAtttributes -> removeAttributes. Implemented missing removeAttributeByName and removeAttributeByRawName. This PR fixes those issues and allows it to compile.

Correcting method name to implement abstract method
removeAtttributes() -> removeAttributes()
Implemented abstract method boolean removeAttributeByName(String,String)
Implemented abstract method boolean removeAttributeByRawName(String)
@wltjr
Copy link
Author

wltjr commented Feb 4, 2017

I see why this failed and it is odd. Pulling current sources and compiling them I run into an opposite error, thus the patches. Gradle only shows a dep of xpp3, but I have to have xpp2 in addition to xpp3 to compile this package. Not sure what is going on there. But these patches were necessary to get dom4j 2.0 to compile from source on Gentoo. https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/dev-java/dom4j/dom4j-9999.ebuild

@FilipJirsak FilipJirsak self-assigned this Feb 4, 2017
@FilipJirsak FilipJirsak added this to the 3.0.0 milestone Jun 18, 2017
@ebourg
Copy link

ebourg commented Oct 25, 2017

I think the patch should also update the version of pull-parser:pull-parser in build.gradle to 2.1.10

@FilipJirsak
Copy link
Contributor

dom4j 2.1.x branch stay on pull-parser:pull-parser:2 and xpp3:xpp3:1.1.4c versions. Move to pull-parser:pull-parser:2.1.10 and org.ogce:xpp3:1.1.6 is incompatible change, I schedule it to dom4j 3.0.

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

Successfully merging this pull request may close these issues.

None yet

3 participants