Why no new Ivy version yet?#68
Why no new Ivy version yet?#68chinhodado wants to merge 1 commit intoapache:masterfrom chinhodado:patch-1
Conversation
|
There will be one soon. There's a discussion going on, in the mailing list to work towards a release soon. |
|
We have a PR where we lack a consensus for (#57) because it adds a new method to an important interface. To break the logjam, it could be postponed to the next release if that targets Java 8 which allows default method implementations in an interface. There are a couple of PRs (#55 and #60) that change UX by use of vector graphics; those can be postponed as well and synced with introduction of vector graphics in Ant (there's a SVG logo for Ant out there). Could somebody review the rest of PRs, please? |
|
Tested this with the latest release (2.4.0) and also a build of the latest master. Fetching all dependencies of: Most of the dependencies are just fetched fine but it doesn't fetch all necessary dependencies from organisation='org.lwjgl' Tested this with Maven and Gradle. Both fetch the dependencies correctly. |
|
What's missing? |
|
I used the code below to download all dependencies. You see the output at the very bottom. Here are the 13 direct compile dependencies it should download: It only downloads some OSX jars for lwjgl. Also the content of those jars is somehow wrong when you open them. Here is the correct jar for content comparison: http://central.mav en.org/maven2/org/lwjgl/lwjgl/ 3.1.2/lwjgl-3.1.2.jar Very confusing. The file ivy2.xml looks like this:
`import java.io.File; import org.apache.ivy.Ivy; public class IvyApiExperiments { // File dependencyFile = new File("./ivy-2.0.xml"); } `:: resolving dependencies :: apache#hello-ivy
:: retrieving :: apache#hello-ivy |
|
Oh, I see. We're looking at the same result, except you somehow keep an older version of junit (in my case JUnit 3 is evicted). The bug is (as you stated) that only platform-specific wjgl jars are downloaded. Somehow the presence of classifier makes Ivy ignore the artifact withouth them. |
|
True. The JUnit3 part is strange. My example above wasn't with the current master but the ivy-2.4.0.jar. Maybe that's the reason. Ignoring the platform-specific wjgl jars is only one part of the problem. Please go in the .ivy cache and look at the content of for example: org/lwjgl/lwjgl/ 3.1.2/lwjgl-3.1.2.jar Here is the correct jar for content comparison: http://central.mav en.org/maven2/org/lwjgl/lwjgl/ 3.1.2/lwjgl-3.1.2.jar When you look at the content of the jar, it isn't identical with the same jar stored on maven central. |
|
You get the correct name using pattern |
|
|
|
What you download is |
|
What is the naming sceme you suggested fixing?: The dependency lwjgl-3.1.2.jar still gets lost, right? So this is a bug? |
|
Yes, it is. See the list of bug reports above. I'd say we have another blocker, speaking of releases. |
|
Thanks for your help. P.S.: Maybe one pre-release test should download an extensive list of dependencies with Ivy and compare them to what Maven or Gradle is getting. |
|
Unrelated, but maybe you should consider enabling the issue tracker here on github. |
I'm just making this PR because the mailing list is a pain to use and there's no issue tracker here on GitHub for the project...but why isn't there a new release for Ivy yet, given the project has resumed development for so long now?