Stanley,Michael P. wrote:
No, the lookup is unchanged. Its how you get the relative path that is different. Right now, you take the group/version and build a relative path, then append that to remote repo locations. What I would do (given group/version) is build a complete URL, and work back from that to get the relative path, just as if the URL had been specified directly. From there processing continues as before. That's why I'm saying I can actually write the code for this, its not a big leap from here to there.Is this any different than how the lookup works today? local -> remote list
Ok I see what you are talking about with cache's and /different/ URLI think guidelines and structure are good too. I just don't expect to be able to impose it on the world. Also I do happen to think that the benefits of being able to grab jars from anywhere will be a real timesaver. Even being able to just download, unpack and use - without renaming - the stuff under the Sun binary license would be benefit enough for some.
structures. I don't see a benefit to having different repo structures.
I think some naming guidelines (unique namespace for a Project's
Repository Space) is desired.
You solution does address complete repository/directory flexibility, andThe solution makes how we get hold of dependencies independent of future changes to the repository structures, and lets people use existing repositories (the corporate fileserver example was real - we use that for ant based projects right now)
addresses collisions from different repositories. Personally, I don't
see a benefit in this flexibility. I think some restricted structure is
important.
This definitely can coexists with the DNS portion of my proposal.Ok. This is where I reckon the cost lies. I'll believe it when I see it ;)
However, the other part of my proposal is looking for a "standard" base
structure based on groupID (namespaces based on reverse domain names).
The base structure will point to the Project's Repository Space. In
this there will be a default structure and naming convention as well,
but this can be overridden with the presence of a meta file.
Anyway, enough. I need to put up or shut up, I'll get some codingdone.
Nonsense ;-) It is definitely beneficial to talk about design in plain English rather than in code.
- Mike
Privacy and Confidentiality Notice
------------------------------------------------
The information contained in this E-Mail message is intended only for the person or persons to whom it is addressed. Such information is confidential and privileged and no mistake in transmission is intended to waive or compromise such privilege. If you have received it in error, please destroy it and notify us on the telephone number printed above. If you do not receive complete and legible copies, please telephone us immediately. Any opinions expressed herein including attachments are those of the author only. i-documentsystems Ltd. does not accept responsibility for the accuracy or completeness of the information provided or for any changes to this Email, however made, after it was sent. (Please note that it is your responsibility to scan this message for viruses).
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
