On Thu, Oct 20, 2016 at 4:47 PM, Gilles <gil...@harfang.homelinux.org> wrote:
> Hi Artem. > > Would you be willing to create a branch containing actual > files? > Yes, will do it today. > > If so, since the break-down into modules I'm thinking of is > not the one you've taken below,[1] I suggest that you create > an "all-example" module, into which you'd move _all_ the code. > > I'd think that you should start from > https://svn.apache.org/repos/asf/commons/proper/weaver/trunk/pom.xml > as suggested by Matt. > Going to take a look into it. > > Then, I expect that > $ mvn clean site > will run smoothly, and produce everything which the current > config does.[2] > > Please let me know if you don't have the time to do it, or if > you run into any problem that would prevent this goal to be > achieved quickly.[3] > > I should be able to do it soon. > > Thanks, > Gilles > > [1] I'm still convinced that the "utils" (referred to in the > other thread) should be a separate component. But we could > nevertheless create modules in "Commons RNG" that would > clearly stress the separation between the low-level RNG > algorithms, the high-level interfaces and the "simple API". > Then later on, the "utils" component could choose to only > depend on the "core" algorithms and provide its own API. > [2] In that case, I'll give a try at splitting the codebase. > [3] In that case, I'll start the release process tomorrow, with > what we have now. > Best regards, Artem Barger.
