HannesWell commented on issue #277: URL: https://github.com/apache/maven-archetype/issues/277#issuecomment-2919872206
Nothing per se, it's just the fact that it's a dependency (which again has dependencies), while the JDK provides something out of the box, which seems to be a direct replacement. And therefore I was wondering if there is a reasons to stay on jdom2, besides that somebody has to do the migration? For example in the Eclipse simulations release we have `jdom2` and `jaxen`, just because M2E bundles maven-archetype and it depends on jdom2. And while there is nothing wrong with it in particular, I think it's good to reduce dependencies where reasonably possible. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
