On Jul 8, 2011, at 9:23 PM, Jürgen Jakobitsch wrote: > hi all, > > before i'd commit to some stanbol core stuff, i'd like to offer > some serious refactoring of the existing code. > > 1. as mentioned during our hackathon : logging (there are huge amounts of > system.out || .err .print, printStackTraces and the like) > i'd try to find some consensus on log-levels (like for example here > http://thejoyofcode.com/Logging_Levels_and_how_to_use_them.aspx) > 2. pom-refactoring : > 2.1 taking a look at some of the poms, i'd say this is a fine example of > "growing code" and copy and paste. > do for example an > - egrep -rl "junit" . --include=pom.xml > - egrep -rl "felix" . --include=pom.xml > in the root of the checkout. > junit for example is in the trunk-parent pom, so there's no need > anywhere else. chances are somebody will even use another version at > some point. > 2.2. another thing that strikes : > there's nearly every slf4j binding that exists in dependencies > somewhere and additionally the pax stuff.
These are good remarks. If you can help, that would be appreciated. > 2.3. are things like the hermit maven-repo in the checkout really a good > idea? i have never seen it being done that way. Yes, it's also cruft from the past, though I also think there are licensing issues here. > 3. maven has this incredibly cool feature of maven-sites, why not use it.. I think we choose to use the Apache Foundation "CMS" instead. That's another sensible option. S. -- Stefane Fermigier, Founder and Chairman, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com/ - +33 1 40 33 79 87 - http://twitter.com/sfermigier Join the Nuxeo Group on LinkedIn: http://linkedin.com/groups?gid=43314 New Nuxeo release: http://nuxeo.com/dm54 "There's no such thing as can't. You always have a choice."
