On Wed, Aug 31, 2011 at 9:45 AM, Simone Tripodi <simonetrip...@apache.org> wrote: > Hi all guys, > I noticed that properly setting the 1.5 as target compliance level, > there are some @Override annotations that in cases of interfaces > methods implementation should be dropped. Do you agree on it?
Yes, @Override from interfaces is supported only in 1.6 > > Moreover, I'd like to propose to split the chain component, for v2.0, > in a multi-module project: > > - core APIs; > - XML configuration APIs (depends from Digester); > - servlet (depends from Servlet APIs); > - portlet (depends from Portlet APIs); > - faces (depends from Faces APIs). > > in that way users interested on core APIs only don't need to bring > unused code; that looks to me a cleaner common approach used in > various projects inside the ASF (cocoon3, for example) and outside > (i.e. slf4j). What's your opinion about it? > Totally agree. Picking through optional dependencies can be difficult. Though I would like to see the Chain API 2.0 javadoc aggregate all those sub-projects together. I don't think it helps the user if we break things down but can't get the documentation to show the full picture. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
