tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: Publishing zips to the maven repo
Date Fri, 14 Oct 2011 16:09:02 GMT

On Oct 14, 2011, at 4:06 AM, Mark Thomas wrote:

> On 14/10/2011 09:15, Konstantin Kolinko wrote:
>> 2011/10/14 David Blevins <>:
>>> We've been using plain Tomcat zips for creating TomEE in the
>>> OpenEJB maven build for a while now.  So far that has been done by
>>> publishing the Tomcat zips to a maven repo in svn.  Not the best
>>> idea to have them in svn, so we're trying to get them in the actual
>>> maven repo.
>> Can't maven be taught to download them from proper ASF mirrors?
> +1
> There is already a world-wide distribution system in place for the
> file(s) concerned so it makes sense that it should be used.
> Adding the full .zip archive to any Maven repo just seems wrong to me
> (and using the ASF svn server for this is definitely a very bad idea)
> but if the folks managing the main Maven repo are happy with this then I
> have no objection.
> 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.

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 using a non-tomcat groupId
is the only choice I'd keep the openejb copy in apache svn.

david jencks

> Mark
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message