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. 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. 3. maven has this incredibly cool feature of maven-sites, why not use it.. wkr jürgen -- punkt. netServices ______________________________ Jürgen Jakobitsch Codeography Lerchenfelder Gürtel 43 Top 5/2 A - 1160 Wien Tel.: 01 / 897 41 22 - 29 Fax: 01 / 897 41 22 - 22 netServices http://www.punkt.at
