-M.
Jason van Zyl wrote:
On Fri, 2004-01-16 at 20:00, Mark R. Diggory wrote:
I was just looking over the "dist" directory and having wild thoughts:
1.) most of the projects are in nested directories
ie: jakarta/commons/collections
dist/**/ project/ source/ binary/
2.) maven requires the remote repository to be in the following structure:
repository/ project/ jars/ distribution/
Are there any thoughts on haw the dist directory itself might be maintained as a maven repository. For instance, is it plausible to have maven "projects" nested within the directory structure, or is this a limitation in Maven's Repository Structure?
It's not something we want. If you want to let people use the existing structure then just write to move stuff from the dist structure to a maven repository structure. On a daily basic you could nuke the copied structure so the size wouldn't build to an unmanageable size. Then you can keep your dist structure and just flush new artifacts to ibiblio.
repository/**/ project/ jars/ distribution/
Is it plausible that a project could actually organize where its "distribution" and "jars" directories were actually located?
No. It's not that complicated. Just copy the artifacts into the required structure.
or would it be more logical to have projects eventually migrate to the maven repository structure for deployment (until then, simlinking source and binary contents mainatained in the current process into maven/repository/project/distributions)?
If you want to have it work with Maven then even a temporary structure would work for syncing. All you really want is to move new artifacts to the repository. There is no reason why the existing apache layout for the dist directories can't be maintained as well as shuffling them about to conform to what Maven needs so that a directory can be flushed to ibiblio.
-Mark
Jason van Zyl wrote:
On Fri, 2004-01-16 at 11:03, Mark R. Diggory wrote:
I'm not sure if this got onto the maven groups radar.
I'd like to get feedback from the Maven group (or others who have access to ibiblio for deploying artifacts).
What is your position on managing/maintain a maven ropository locally here on apache servers that will be used to supply the ibiblio mirror with all our "Apache Artifacts"?
I say just get infrastructure to make a directory that is accessible to committers and then it only takes a minute to mail the ibiblio admins to pull from Apache at a 4 hour intervals.
Are there any "local" Maven repositories in standard locations on servers like cvs.apache.org?
Not yet, but you ask infrastructure what you would like and I'm sure they would be happy to service your request.
If you get directory structure happening, I would be happy to contact to ibiblio and give them the details so they can setup the pull.
This would definitely work right now, and if you want to do it in the dist directory so your repo gets mirrored then people can use those as well. They would just simply have to point at their local mirror containing the repository by adding an entry in their build.properties.
Happy to help on the ibiblio end if you get things set up here, but there are no objections here.
-- Mark Diggory Software Developer Harvard MIT Data Center http://osprey.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
