Hi, We are in need of a RPM repository that is yum accessible, where all the RPMs are produced by Maven, and I wanted to check if anyone else is interested in the same thing? Note that this same type of proposal could apply to Solaris, Debian, etc. and these could be paralell efforts with the RPM effort. So where I use RPM specific terminology and tools, just substitute with the other OS's equivalent features :-).
Here's a brief proposal: PRIMARY GOAL To be able to produce yum installs of Apache and other servers/applications that were built using dependencies from a Maven repository that is synchronized with the RPM repository. There will be a layer on top of this that ensures Maven best practices with respect to dependency management and plugin management of the poms that are used to produce the RPM spec file (Later I want to combine it with the Archiva server for automatic signature checking). EASE OF USE - A Maven download with preconfigured repository settings pointing to a Maven repository that is synced with the corresponding RPM repository is made available for download. The purpose of this download is to minimize the effort required by developers who wish to write artifacts that will commit RPMs to the repository. Thus it will come with archetypes that produce Java projects and other project which ensure repository quality requirements are met. ONLY MAVEN BUILT ARTIFACTS IN THE REPOSITORY - Only Maven artifacts will be allowed in the RPM repository. The reason for this is to focus quality control automation around a set of Maven plugins. If the project wishes to support manual package customization, those would be done in a "stage 2" repository. ALL RPMS ARE A 1:1 MATCH WITH THE CORRESPONDING MAVEN PROJECT - This is so that RPMS are automatically generated and applications that depend on these RPMS have a 1:1 match with the original dependencies that developers used when creating the application / server. SERVER INSTALL AUTOMATION TOOLS FOR RPM - So that servers built from the maven artifacts can be easily generated and installed. These servers will use an the standard UNIX/LINUX FHS layout, and use best practices with respect to UNIX/LINUX file permissions and ownership. I have a lot of this work done already, I just wanted to see whether there are others interested in this type of approach and whether there are any thoughts on how to go about creating the central location for this type of effort? Cheers, - Ole ____________________________________________________________________________________ Want to start your own business? Learn how on Yahoo! Small Business. http://smallbusiness.yahoo.com/r-index --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
