Publish and fetch a modular jar to a repository
Paul Sandoz
paul.sandoz at oracle.com
Mon Jul 16 09:21:36 PDT 2012
On Jul 16, 2012, at 5:50 PM, Alan Bateman wrote:
> On 16/07/2012 11:18, Paul Sandoz wrote:
>> Hi Alan,
>>
>> Thanks for looking at this.
>>
>> Here is an update:
>>
>> http://cr.openjdk.java.net/~psandoz/jigsaw/repo-add-jar/webrev.1/
> I see there's a webrev.2 with additional comments from Chris so I looked at that.
>
> On Repository.ModuleType I see you've changed it to add a constructor to take the extension type so that looks better although I do think the enum values should in uppercase.
OK, converted to upper case. I have no strong preference on the style, just wanna be consistent, like with code formatting (but wanna automate that bit):
http://cr.openjdk.java.net/~psandoz/jigsaw/repo-add-jar/webrev.3/
>
> Otherwise I don't have any issues, I think Chris is going to help you get this in.
>
Yes.
>> :
>>
>> IMHO the catalog needs to be in an extensible format that is easily consumable i.e. it is something that is likely to be consumed by many clients, in various languages, for various purposes. To me that means a textual format. That does not rule out other optimized formats. One can use HTTP content negotiation and/or there can be a services document, served by the root resource, that tells the client what there is and how to get to it (no need to hard code all URIs).
>>
> I agree it needs to be easy to consume, also we have to assume it will change or be extended over time. Also need to thing through use-cases, like modules moving to be another repository, etc. I think it will be useful to also look at existing and well-established repositories as this isn't new ground.
>
Agreed, given my moderate RESTafarian background we may be able to do some interesting stuff.
Paul.
More information about the jigsaw-dev
mailing list