On Tue, Mar 16, 2010 at 10:08 AM, Marvin Addison <[email protected]>wrote:
> <snip /> > > > You could move log4j but having it there is helpful for tests. > > Servlet API is probably the only one that could realistically move. > > Keeping the parent POM lean is a noble goal, so I'd move out anything > we don't explicitly need. Your points about convenience are well > taken, though. I suppose my main sticking point with the current > state of affairs is compile-time dependencies on a logging engine > (log4j at present). That seems to reduce the benefits of a logging > facade like slf4j since it's impossible to unplug the engine at > runtime. I realize that perf4j requires log4j explicitly, so changing > to another engine like JUL or logback isn't feasible without > additional work. I'm not suggesting we do that work or change > anything at present; simply wanted to point out ickyness that we might > look to clean up if the situation changes in the future. > I'll look at moving the servlet jar. I could reduce log4j to runtime at the parent pom level (or even test) and make it compile-time merely for the webapp project. FYI, Inspektr is now in the Central Repository! Cheers, Scott > > > Spring Core and Context aren't at the parent pom level. > > They probably should be, though, since we use at least the 3 core > Spring libs in every module. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
