Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
jar dependency match with json report #743
Since there are 3 roots to resolve, the tree is correct. One
Now look at the json output:
Now, there is no way to tell which it needs, because all it knows is just
Add classifier to dependencies
I think it depends, as we may not need to surface all attributes passed on command line into the json report. @baroquebobcat will be working on this and proposed to use
That said, option 1 could be an intermediary step, before Pants can fully adopt the full maven spec.
I plan to add documentation on json report and versioning and to highlight the json report is not stable yet. (#749)
One thought I had here is that with either option I think we ought to adopt Maven's coordinate structure instead of
By using the above scheme we don't have to have an explicit value for
I don't know enough about the currently accepted schema to be sure that this'll work, but I'd appreciate some feedback.