Using SBT would help to avoid having to duplicate the source code for each Scala version. However, I'm not sure about how to do the Maven site stuff with SBT.
On Sun, Apr 2, 2017 at 10:41 PM, Matt Sicker <boa...@gmail.com> wrote: > I'm not too experienced with it, but now that the Scala APIs are in their > own repo, it might be easier to use SBT instead of Maven for it. Just a > thought for a future release. > > On 2 April 2017 at 15:27, Matt Sicker <boa...@gmail.com> wrote: > >> And don't mind the site commit I made earlier. That was from a snapshot, >> so I have to commit it again anyways. >> >> On 2 April 2017 at 15:25, Matt Sicker <boa...@gmail.com> wrote: >> >>> No, I figured I'd do log4j-core first. Still working on that right now, >>> had to restart the build from the tag because a test randomly decided to >>> fail at the worst possible time. >>> >>> On 2 April 2017 at 15:11, Ralph Goers <ralph.go...@dslextreme.com> >>> wrote: >>> >>>> Has a Scala release been performed? The site needs to be deployed >>>> before I can modify the log4j page(s) to point to it. >>>> >>>> Ralph >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org >>>> For additional commands, e-mail: log4j-dev-h...@logging.apache.org >>>> >>>> >>> >>> >>> -- >>> Matt Sicker <boa...@gmail.com> >>> >> >> >> >> -- >> Matt Sicker <boa...@gmail.com> >> > > > > -- > 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.
