tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <>
Subject Re: Mavenized tomcat build
Date Sat, 11 Jul 2009 15:38:10 GMT
I think there are few separate issues:

1, If there is a patch that needs to be applied by geronimo to use
tomcat or they are blocked by missing something from a release - we
should review this again. I think we can do a tomcat-geronimo release
specifically for them as worse case ( well, we did it for j2ee ref
impl in the old days - all we need is a branch ), or make sure it gets
in the next release,

2. For Maven support - if maven can support building tomcat, I don't
see any problem. But moving the code around and changing code just so
we can be built by maven - I don't like that. The current patch is
even worse - it seems to create 2 different source trees for tomat,
and since maven can also checkout the source and people may use the

3. For having maven-like 'modules' with strict build and runtime
dependencies - been there. There are plenty of large projects using
tomcat approach - i.e. allow circular dependencies between packages
and build either one big jar or few jars. I think the benefits of more
reuse and code sharing are bigger than the problems - i.e. mostly not
able to break into many directories and build with maven, and arcane
ways to break circular dependencies.


On Fri, Jul 10, 2009 at 11:43 PM, Mladen Turk<> wrote:
> Filip Hanik - Dev Lists wrote:
>> If Geronimo needs a better way to download and integrate Tomcat's JAR's
>> lets focus on that, and not make this into another Maven vs ANT topic, cause
>> I don't think that was the intention.
> Agreed.
> However we should really find a way to deal with eclipse
> repository since they tend to change the download system
> quite often (only external dependency).
> Since we cannot copy that to the ASF due to license issue
> we could reuse the backup system on (like we did
> for Tomcat Native until ASF resolved the crypto software issues)
> to allow the historic builds.
> I somehow doubt Maven can solve this problem anyhow, and
> downloading a repo with 10+ eclipse JDT's would be insane
> just to build eg. 6.0.20 in 5 years from now.
> Other things is trivial, just testing the
> with as fallback for the remaining
> dependencies.
> Regards
> --
> ^(TM)
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message