commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <brit...@apache.org>
Subject Re: commons-monitoring?
Date Wed, 13 Feb 2013 11:36:03 GMT
2013/2/13 Paul Libbrecht <paul@hoplahup.net>

> Benedikt,
>
> On 13 févr. 2013, at 08:49, Benedikt Ritter wrote:
> > Commons components usually don't have any dependencies. How would you
> > implement this under this restriction?
>
>
>
> I've never seen this written before. Have you?
>

Yes, on the commons website [1]:

"Commons developers will make an effort to ensure that their components
have minimal dependencies on other libraries, so that these components can
be deployed easily."

But you're right If you wanted to point out, that this is not an absolute
must-have. We can have minimal dependencies.
I guess (but I don't know!) it would be okay to have a dependency to the
AOP alliance jars, for example to define a new MethodInterceptor [2] for
monitoring. But IMHO it would be rather strange to have dependencies to
org.springframework.aop to define a new MethodBeforeAdvice [3] for
monitoring.

Makes sense? :)

Benedikt

[1] http://commons.apache.org/
[2]
http://aopalliance.sourceforge.net/doc/org/aopalliance/intercept/MethodInterceptor.html
[3]
http://static.springsource.org/spring/docs/3.0.0.M1/javadoc-api/org/springframework/aop/MethodBeforeAdvice.html


>
> paul
>
>
>
>


-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message