About repository structure

[Nicolas De Loof <ni...@capgemini.com>]

I'm trying to "cleanup" my company private maven repository. It is used 
to store java API jars.

Current structure is

/jdbc/jars/jdbc-2.0.jar
/jaxr/jars/jaxr-api-1.0.jar
... and so on

As they're lot's of java API (...), I've two options
- put all java standard API in "sun" or "java" groupId
- use a two levels structure :

sun
    /jdbc/jars/jdbc-2.0.jar
    /jaxr/jars/jaxr-api-1.0.jar
    /jta/...

Second options sound good and seems to work fine (using 
groupId=sun/jdbc) , but this isn't the "standard" used on ibiblio or 
other public repository.

Do you think this is a bad design for repository ?

What about wagon way to do it for maven next releases ?

Nico.

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.


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