Adam R. B. Jack wrote:
Metadata:
3) Do we need per version metadata? Hmmm... :(
I guess it's doable, tools could easily provide. The per *.md5 or *.asc
are such metadata.
I think per version metadata can be just another TYPE of artifact
stored in the repo
/commons-beanutils/meta/depen
Adam R. B. Jack wrote:
Metadata:
Since we need/want programmable I doubt we'll get disagreement on XML.
Static or dynamic is more interesting.
I think we should have meta data, but I would like a repo to still be
usable at some level with out any. Just drop files in a dir on a
webs
Metadata:
Since we need/want programmable I doubt we'll get disagreement on XML.
Static or dynamic is more interesting.
Questions:
1) Do we need server side metadata?
I suspect yes, for referencing the 'version' of the repository spec being
followed, if nothing else. That said,
Thats fine.
I think the "repository" list was created to define the layout and
metadata for the asf server. And by side effect - it may affect the
release process and naming in many apache projects.
IMHO a lot of XML and complexity is a bad idea for the repository.
But I agree that some
On Thu, 6 Mar 2003, Andrew C. Oliver wrote:
I don't really intend to have an english discussion on this, I would
rather discuss in Java. I'm approximately 3-5 days away from having
this done...
I have a feeling that if people would first discuss things in english
we wouldn't have the current me
Nick Chalko wrote:
This seems like a whole lot of XML for what is implicit in the URI
and the manifest.
You mean the very specific to one server and one layout? Your goals may
differ. Thats fine.
-Andy
This seems like a whole lot of XML for what is implicit in the URI and
the manifest.
This seems like a whole lot of HTML for what is implicit in the URI and
the manifest.
:-( oh man... did ya have to?
I don't really intend to have an english discussion on this, I would
rather discuss in Java. I'm approximately 3-5 days away from having
this done...
The code goes and grabs a version of a jar based on 4 XML descriptors
(don't take these as gospel, they are chang
What are the requirements for MetaData
The meta data should support:
* identifectoin of dependineces
* version information
* JDK level requirements
* integrity check
What else/
Costin Manolache wrote:
On Thu, 6 Mar 2003, Nick Chalko wrote:
I'll start the discussion with what John Toohey said.
In both html and xml format
* list of available versions,
* their MD5's,
* dependencies,
* perhpas a
* code for licenses
Html format - I suppose you mean a eas
On Thu, 6 Mar 2003, Nick Chalko wrote:
> I'll start the discussion with what John Toohey said.
>
> In both html and xml format
>
> * list of available versions,
> * their MD5's,
> * dependencies,
> * perhpas a
> * code for licenses
Html format - I suppose you mean a easy-to-
I'll start the discussion with what John Toohey said.
In both html and xml format
* list of available versions,
* their MD5's,
* dependencies,
* perhpas a code for licenses
--
Nick Chalko Show me the code.
Centipede
Ant +
I'll start the discussion with what John Toohey said.
In both html and xml format
* list of available versions,
* their MD5's,
* dependencies,
* perhpas a
* code for licenses
--
Nick Chalko Show me the code.
Centipede
14 matches
Mail list logo
