2012/6/1 Christian Grobmeier <grobme...@gmail.com>: > On Fri, Jun 1, 2012 at 2:49 PM, Antonio Petrelli > <antonio.petre...@gmail.com> wrote: >> 2012/6/1 Christian Grobmeier <grobme...@gmail.com>: >>> Suggestion: the easy part is to make chainsaw and lf5 classes a >>> module. I have nuked them but Jacob requested they come back :-) These >>> are all GUI related stuff. Next thing I'll do is create the module >>> folders and get the code back to these. >>> Then we can move the rest into a "core" folder and create the parent pom. >>> >>> Do you think this would be an acceptable move? >> >> So if I understand you well, you would like to create a core, simply >> by removing the GUI-related stuff? >> I think that, if a reorganization has to be done, it should be done >> the right way. > > I think like that: > > /pom.xml <-- parent > /core/src/main/java <-- Just logging classes > /lf5/src/main/java > /chainsaw/src/main/java > > etc > The core might need some more extractions but this could be the first step. > > >>> https://github.com/astubbs/log4j/tree/modulriseify >> >> With the exception of directory naming, it seems like a good job. Why >> did'nt you take it in consideration 2 years ago? > > I was not really deep into log4j back then (still fighting) and why > this has not been included: don't know. But better late than never. >
OK. I think I will merge and tweak it. Apparently, it needs only a little of polishing (pointing to apache-master, renaming the directories as the names of modules, using the standard Apache release system [that uses Nexus]). Thanks for the pointer (to Anthony too, if he still reads that). Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
