I plan on moving log4j-server back into the main repo. There is some odd Maven cycle thing going on ATM that breaks the main repo build. It also makes no sense to me in tools, which should for _tools_ like the DAT file plugin we talked a while ago that would collect various DAT files and make them one, handy when shading.
Gary On Fri, Jul 21, 2017 at 5:18 AM, Mikael Ståldal <mi...@apache.org> wrote: > The repository is not ready for release. > > > > On 2017-07-20 22:26, Matt Sicker wrote: > >> Is the repo ready for release? I can probably be the RM for it. These >> smaller modules take quite a bit less time to make RCs for than the main >> repo (which is why we're working on splitting it up in the first place). >> >> On 20 July 2017 at 14:48, Mikael Ståldal <mi...@apache.org> wrote: >> >> The SocketServer stuff is now in the new log4j-server module, which is in >>> the new log4j-tools repo. >>> >>> Is anyone going to release this new repo in conjuntion with the 2.9 >>> release of the main repo? If not, the SocketServer stuff will be gone. >>> >>> If we want to have a binary release of the SocketServer stuff we need to >>> either release the new repo, or move the log4j-server module to the main >>> repo before the 2.9 release. >>> >> >
