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
Switch to original Apache Ivy #28
Comments
Are you suggesting that sbt uses Apache Ivy repository (https://svn.apache.org/repos/asf/ant/ivy/core/) and continue the unofficial fork? Is the motivation to avoid duplication of development (for example to adopt to JDK 9/10)? |
The fork appeared because EasyAnt project has created a clone of Ivy SVN repo in GitHub. Meanwhile, Ant project (which Ivy is a part of) converted to Git (https://git.apache.org/ant-ivy.git/) a couple of years ago. All Apache Git repos are cloned at GitHub, inclusive Ivy (https://github.com/apache/ant-ivy). Since Ant project has been discussing a new release of Ivy (tentatively called 2.5.0), maybe there's a chance to merge the development history. We would appreciate your input choosing the baseline for the next release. The current plan is to release 2.5.0 for Java 7 and target Java 8 for next release in order to align the development with Ant. |
sbt uses a fork off of 2.3.x apache/ant-ivy@a83df76, which we call 2.3.x-sbt. I should probably note that there are overwhelming number of people who want to switch the library management implementation away from Ivy, and migrate to Scala based engine called Coursier. sbt/sbt#2997 for example has 172 likes atm. Since Coursier doesn't implement all features of Ivy, we will likely continue to depend on Ivy for a long time, but I as an sbt maintainer would like Ivy to stay as stable LM API implementation; and Coursier implementation can do the cooler things. As per Java is concerned. I am ok with supporting Java 7 as the minimum version, but it's essential that we support Java versions 10 and 11. |
Thanks for the pointer. I am aware of Coursier, and I'm fine with sbt moving to pure Scala. My intent was to understand whether it would make sense to add sbt branch to Apache Ivy in order to make it easier to port improvements. |
Yes, I think that makes sense. |
Would you consider switching to Apache Ivy if we would graft easyant-integration, 2.3.x-sbt and 2.4.x-sbt branches?
The text was updated successfully, but these errors were encountered: