Thank you for this infos.
Nico.
Maczka Michal a �crit :
-----Original Message-----
From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
Sent: Friday, March 18, 2005 9:44 AM
To: Maven Developers List
Subject: About repository structure
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 ?
If it works for you and you find it resonable - you can surly use it for
your intranet repo.
"/" in groupIds should work with both m1 and m2.
m2 gives you also the possibility of using "." as separators in paths (they
are replaced by "/" to construct valid paths for wagon)
but I personally find it less natural then "/" which should also work.
The aspect what should be used as groupId and how it affects repository
layout was really never standarized.
You can expect that sooner or later this will happen and also the layout for
sun jars even if they wont be in the repository
will be standarized (correposnding poms can be deployed to the repository
even in jars are missing)
Probably repository paths will contain segments corresponding to
organizationId, groupId, version and artifactId.
Both organzationId and groupId will be specified by the single <groupId>
attribute of dependecy and both can be mulilevel.
I'd love to see something like this as groupId:
www.foo.com/project/subproject/subsubproject/myArtifact/0.15/myArtifact-0.15
.jar
but most likly it will be something else.
What about wagon way to do it for maven next releases ?
It was never cleary communicated what wagon is.
Wagon provides generic, protocol independent transfer layer and nothing
more. Mapping between attributes of dependencies and repository paths
is implemented in maven core and is out of the scope of wagon. Wagon just
works with paths (urls) and "/" is used as separator. Generation of those
paths requires very arbitraty decison how to make a mapping.
michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
