You are viewing a plain text version of this content. The canonical link for it is here.
Posted to community@apache.org by Nick Chalko <ni...@chalko.com> on 2003/03/01 20:06:22 UTC

[ASF-Repository]Jars with/without version. was Re: [proposal] daedalus jar repository

Craig R. McClanahan wrote:

>On Sat, 1 Mar 2003, Stefano Mazzocchi wrote:
>  
>
>>dion@multitask.com.au wrote:
>>    
>>
>>>Having a file encode <project>-<artifact>-<version>.type has been very
>>>useful for us.
>>>
>>>Yes, it's often different from what the project creates and distributes,
>>>but I (and others) have been bitten by
>>>commons-logging.jar, struts.jar, junit.jar so many times, that seeing
>>>log4j-1.2.5.jar is a godsend.
>>>      
>>>
>>I totally share this experience and support the concept.
>>
>>    
>>
>
>I've gotten bit by the opposite problem (changing version number in a JAR
>filename causing broken build scripts) just as often.
>
>Wouldn't a reasonable approach to this problem be to make searches for
>"commons-foo.jar" return the latest released version, while searches for
>"commons-foo-x.y.jar" would return that particular version?  Then, you can
>have it either way.  On the former, one might also support a mode that
>grabs the latest nightly instead of the latest reslease.
>  
>
Two problems here

    * The uri to find a needed jar.
    * How to store the jar on the local filesystem

I think we should handle these cases

    * uri to find
          o Specific version
          o latest released.  (blank )
          o latest nightly
    * Jar name on local filesystem
          o with complete version
          o without version.

Seems like a straight forward enough to handle all of these on the 
client or the server side.

R,
Nick



---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org


RE: [ASF-Repository]Jars with/without version. was Re: [proposal] daedalus jar repository

Posted by "Noel J. Bergman" <no...@devtech.com>.
Craig,

> If we make the two choices (which version and which local name)
> independent request parameters, we've covered all the
> combinations and permuations.

The idea I had was for the request URI to be project based.  The response to
that stable URI would be descriptor content.  Part of the descriptor content
would provide version and package naming information (I expect that this
would all be XML-based, but it just needs to be some standard format).  With
a static content server, the client parses the response, locates the desired
version, pulls out the necessary download URI.  The mapping from package and
version strings is not required to be encoded within the download URI.

ref:
http://archives.apache.org/eyebrowse/ReadMsg?listName=community@apache.org&m
sgNo=1781

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org


Re: [ASF-Repository]Jars with/without version. was Re: [proposal] daedalus jar repository

Posted by "Craig R. McClanahan" <cr...@apache.org>.

On Sat, 1 Mar 2003, Nick Chalko wrote:

> I think we should handle these cases
>
>     * uri to find
>           o Specific version
>           o latest released.  (blank )
>           o latest nightly
>     * Jar name on local filesystem
>           o with complete version
>           o without version.
>
> Seems like a straight forward enough to handle all of these on the
> client or the server side.
>

If we make the two choices (which version and which local name)
independent request parameters, we've covered all the combinations and
permuations.

> R,
> Nick

Craig

---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org


RE: [ASF-Repository]Jars with/without version. was Re: [proposal] daedalus jar repository

Posted by "Noel J. Bergman" <no...@devtech.com>.
Nick,

> Two problems here
>     * The uri to find a needed jar.
>     * How to store the jar on the local filesystem

Does the URI (request) and descriptor (response) solution I proposed not
address those goals?  That approach decoupled the naming systems.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: community-unsubscribe@apache.org
For additional commands, e-mail: community-help@apache.org