RFR: 8153654: Update jdeps to be multi-release jar aware

Paul Sandoz paul.sandoz at oracle.com
Wed Aug 31 15:51:11 UTC 2016


> On 30 Aug 2016, at 19:58, Steve Drach <steve.drach at oracle.com> wrote:
> 
> new webrev addressing issues below: http://cr.openjdk.java.net/~sdrach/8153654/webrev.09/ <http://cr.openjdk.java.net/~sdrach/8153654/webrev.09/> <http://cr.openjdk.java.net/~sdrach/8153654/webrev.09/ <http://cr.openjdk.java.net/~sdrach/8153654/webrev.09/>>
> 
> 
>>> Hi,
>>> 
>>> Please review the following two changesets that enables jdeps to use multi-release jar files.  The output from the tool shows versioned dependencies by prefixing them with “version #/“ where version # is 9, 10, etc.
>>> 
>>> webrevs: http://cr.openjdk.java.net/~sdrach/8153654/webrev.08/ <http://cr.openjdk.java.net/~sdrach/8153654/webrev.08/>
>> 
>> This looks quite good.  JDK-8163798 and JDK-8164665 will define public APIs to get the versioned entries and real name which I think are useful for tools.  It’s fine to proceed with this change and update jdeps to use the public APIs when available.
> 
> The product team has decided not to move forward on those two issues for now, they will remain unresolved.
> 

There appear to be a number of use-cases pulling on versions streams with slightly different requirements. That made me uncomfortable and I am concerned about the time taken to churn on such a public API, so rather that trying to get the API right at this point i felt it more expedient to focus on internal implementations, and when those implementations settle we can stand back and see how to expose as a public API.

Paul.


More information about the core-libs-dev mailing list