tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Cassidy" <>
Subject Re: Two modest proposals about common\lib
Date Thu, 28 Oct 2004 13:35:52 GMT

i normally resolve this with symlinks. Means I can have 'my' common stuff like database drivers
in any place I like. (ie in a versioned directory like dbdrivers/database/version/....jar

Kind regards

David Cassidy

                      Margulies"               To:       <>
                      <bim2004@basistec        cc:                                    
            >                   Subject:  Two modest proposals about common\lib
                      28/10/2004 14:22                                                   
                      Please respond to                                                  
                      Developers List"                                                   

Based on all the recent traffic from people tying themselves into
pretzels with global resources, I have two concrete ideas. I would try
to concoct patches (at least for the first) if there was tentative
acceptance for either.

1) Configure the 'common' classpath in an editable location. By default,
this path would be the current set of common directories. However, an
admin could add additional directories shaped like common.

This would be an improvement in administration. As things are, if I want
to distribute/deploy common resources, I have to mix my stuff in with
the standard stuff. A new release of Tomcat requires me sort it all out
over and over. It would cleaner if I could keep 'my' stuff off in
separate directories, and just configure it into Tomcat. If I had
multiple packages from multiple sources that needed to go into common, I
could keep them separate.

2) Some sort of optional classpath conflict checker. Many people seem to
get into deep trouble by ending up with copies of 'the same thing' in
both a webapp class path and the common class path. I'm thinking of an
off-to-one-side tool that would inventory the contents of a webapp, and
check for conflicts with common, and report them. Perhaps this would be
a candidate for merely 'contrib' status if someone coded it.

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


This e-mail may contain confidential and/or privileged information. If you are not the intended
recipient (or have received this e-mail in error) please notify the sender immediately and
destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.

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

View raw message