I'm thinking that the log4j-scala site and docs can be generated on its own, and then we can add links in the sidebar of the core site. I'm not too experienced with the maven site plugin either.
On 9 November 2016 at 06:46, Mikael Ståldal <mikael.stal...@magine.com> wrote: > How do we move forward with this? I am not very experienced with Maven > site stuff. > > On Tue, Nov 8, 2016 at 4:03 PM, Matt Sicker <boa...@gmail.com> wrote: > >> We still need to figure out how to properly link and integrate the >> log4j-scala sites from the main one. I'd imagine the integration should >> look similar to how it already does now as a seamless experience. >> >> On 8 November 2016 at 06:26, Mikael Ståldal <mikael.stal...@magine.com> >> wrote: >> >>> I have now populated the new Git repo logging-log4j-scala with the Scala >>> stuff from the main repo, and also added Scala 2.12 support. The new >>> project will require Java 8 to build. >>> >>> I set the main Log4j 2 project as parent, is that OK? >>> >>> Have I missed anything? >>> >>> Can we create a Jenkins build for this? >>> >>> (I will remove the Scala stuff from the main repo when we have verified >>> that the new repo is OK.) >>> >>> -- >>> [image: MagineTV] >>> >>> *Mikael Ståldal* >>> Senior software developer >>> >>> *Magine TV* >>> mikael.stal...@magine.com >>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >>> >>> Privileged and/or Confidential Information may be contained in this >>> message. If you are not the addressee indicated in this message >>> (or responsible for delivery of the message to such a person), you may >>> not copy or deliver this message to anyone. In such case, >>> you should destroy this message and kindly notify the sender by reply >>> email. >>> >> >> >> >> -- >> Matt Sicker <boa...@gmail.com> >> > > > > -- > [image: MagineTV] > > *Mikael Ståldal* > Senior software developer > > *Magine TV* > mikael.stal...@magine.com > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > > Privileged and/or Confidential Information may be contained in this > message. If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply > email. > -- Matt Sicker <boa...@gmail.com>
