On 14/10/2011 17:09, David Jencks wrote: > > On Oct 14, 2011, at 4:06 AM, Mark Thomas wrote:
>> Since the requirements for this are driven by the OpenEJB project >> and - as far as I am aware - they are the only folks with this >> requirement, I suggest that OpenEJB runs with this and publishes >> the .zip to the main Maven repo under the OpenEJB group id. >> >> To ensure that no confusion is caused by this publishing I would >> ask that: - the zip published is an exact copy of that on the >> mirror system - the zip is not made available via Maven any earlier >> than it is available via the mirrors > > I really hope that just because the main tomcat developers don't see > the benefits of the maven ecosystem they don't throw away this > opportunity to make tomcat relate better to it and make life > significantly easier for projects that are built using maven and use > tomcat as an integration test prerequisite. I've seen quite a few > projects where a lot of the build is not automated because you have > to track down an appropriate tomcat distro, unpack it, start it, and > tell the maven build where it is.... then you can run the build > including the integration tests that use this tomcat server you > installed by hand. It the distro were in the maven central repo, > this could all be automated easily without using little-known > "download a single file from a non-standard location" techniques. This is the first time that I can recall that anyone has stated that there is a requirement for this. Granted, the Tomcat project currently has no interest in using Maven as a build system but that doesn't mean Maven is ignored. A lot of work went into improving the Maven artefacts for Tomcat 7. > Publishing to maven central the official tomcat distro under any > other groupid than the tomcat one seems calculated to confuse > everyone in every way possible. If there is a wider demand for this than just the OpenEJB project then publishing under the Tomcat groupid as part of the existing Tomcat 7 Maven publishing script does seem like a better approach. It looks like an abuse of the Maven repos to me but if the folks managing the Maven repos are happy with this then I don't see a problem. As always, patches welcome. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
