I worry that breaking the site up into multiple sub sites is going to make the user experience worse. It may make it difficult for users to find things.
And I'm still not convinced that this will speed up the build.... Sent from my iPhone > On 5 Dec 2016, at 7:30, Apache <ralph.go...@dslextreme.com> wrote: > > I don’t think each of those should be in a separate repository, but it would > make sense to have a single repo with all of them as sub projects. > > We do need to determine how we are going to change the layout of the Log4j > site to accommodate all of this as each repository will have its own Maven > generated site. I would think we might want to have links to them from the > Log4j site that open the referenced site in a new tab? > > Ralph > >> On Dec 4, 2016, at 2:40 PM, Gary Gregory <garydgreg...@gmail.com> wrote: >> >> OK, I have a log4j-sql module split out locally. But it seems we need >> instead: >> >> - log4j-db (commons code, depends log4j-core) >> - log4j-jdbc (JDBC only, depends on log4j-db) >> - log4j-jpa (JPA only, depends on log4j-db) >> >> I would also repackage these out of .core. >> >> Thoughts? >> >> Gary >> >>> On Sun, Dec 4, 2016 at 1:28 PM, Gary Gregory <garydgreg...@gmail.com> wrote: >>> Note the common code in .core.db for .core.db.jdbc and .core.db.jpa. It >>> seems just that little bit should go in its own module or stay in core. >>> >>> Gary >>> >>>> On Sun, Dec 4, 2016 at 1:15 PM, Gary Gregory <garydgreg...@gmail.com> >>>> wrote: >>>> Also: package names, it does not make sense to have JDBC and JPA code >>>> under the .core. package anymore. I would: >>>> >>>> Create the new modules with code not in .core. and deprecate the >>>> equivalent in .core. >>>> >>>> Gary >>>> >>>>> On Sun, Dec 4, 2016 at 1:08 PM, Gary Gregory <garydgreg...@gmail.com> >>>>> wrote: >>>>> Hm... this is also an opportunity to pick more precise names: log4j-jdbc >>>>> and log4j-jpa >>>>> >>>>> Gary >>>>> >>>>>> On Sun, Dec 4, 2016 at 12:56 PM, Matt Sicker <boa...@gmail.com> wrote: >>>>>> As for SQL, the JDBC one doesn't have any dependencies, so that could >>>>>> stay in core if desired, but the JPA one does require additional Java EE >>>>>> APIs, so that'd make sense to separate at the very least. >>>>>> >>>>>> As for the nosql ones, again, it would be nice to split those up so that >>>>>> there aren't optional dependencies. That would either mean a mongo and >>>>>> couch component, or it could also mean an additional nosql-common >>>>>> component (unless the abstract classes were put into log4j-core). >>>>>> >>>>>>> On 4 December 2016 at 12:44, Gary Gregory <garydgreg...@gmail.com> >>>>>>> wrote: >>>>>>> Thoughts on splitting out SQL and MOM (JMS) into their own modules? We >>>>>>> already have a nosql module, having a sql one makes sense. The overall >>>>>>> idea is to make core lighter. >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Matt Sicker <boa...@gmail.com> >>>>> >>>>> >>>>> >>>>> -- >>>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >>>>> Java Persistence with Hibernate, Second Edition >>>>> JUnit in Action, Second Edition >>>>> Spring Batch in Action >>>>> Blog: http://garygregory.wordpress.com >>>>> Home: http://garygregory.com/ >>>>> Tweet! http://twitter.com/GaryGregory >>>> >>>> >>>> >>>> -- >>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >>>> Java Persistence with Hibernate, Second Edition >>>> JUnit in Action, Second Edition >>>> Spring Batch in Action >>>> Blog: http://garygregory.wordpress.com >>>> Home: http://garygregory.com/ >>>> Tweet! http://twitter.com/GaryGregory >>> >>> >>> >>> -- >>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >>> Java Persistence with Hibernate, Second Edition >>> JUnit in Action, Second Edition >>> Spring Batch in Action >>> Blog: http://garygregory.wordpress.com >>> Home: http://garygregory.com/ >>> Tweet! http://twitter.com/GaryGregory >> >> >> >> -- >> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org >> Java Persistence with Hibernate, Second Edition >> JUnit in Action, Second Edition >> Spring Batch in Action >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >
