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

Upgrade to JDOM 2.0.5 #197

Closed
Athou opened this issue Jan 6, 2015 · 6 comments
Closed

Upgrade to JDOM 2.0.5 #197

Athou opened this issue Jan 6, 2015 · 6 comments
Milestone

Comments

@Athou
Copy link
Contributor

Athou commented Jan 6, 2015

See hunterhacker/jdom#112

Note that artifactId changed from jdom to jdom2.

@PatrickGotthard PatrickGotthard added this to the Version 1.6.0 milestone Feb 21, 2015
@PatrickGotthard
Copy link
Member

The latest version of JDOM 2 will be used in Version 1.6.0

@mschipperheyn
Copy link

Any ETA on 1.6.0? Sucks being stuck on dangerous basecode

@mschipperheyn
Copy link

Any updates? Bueller, Bueller?

@mishako
Copy link
Member

mishako commented Dec 23, 2015

This is weird. Patrick has switched to jdom2 in commit 0b9df0e. Several months later Rome 1.5.1 has been released. Quite surprisingly it still depends on jdom [1].

@PatrickGotthard Are you sure your release workflow is not broken?

[1] http://search.maven.org/#artifactdetails%7Ccom.rometools%7Crome%7C1.5.1%7Cjar

@mishako
Copy link
Member

mishako commented Jan 10, 2016

Sorry, I was confused. Rome 1.5.1 was released from a separate branch.

@mschipperheyn I expect Rome 1.6.0 to be released within a month.

@mishako
Copy link
Member

mishako commented Mar 25, 2016

@Athou @mschipperheyn Rome 1.6.0 has been released with this issue fixed.

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

No branches or pull requests

4 participants