Re: [Scala] Let's get version 11.0 going

1. Perform the release build. 2. Build the site. 3. Upload the site to where we can view it. 4. Vote on it. 5. When it passes upload the site to a directory adjacent to the log4j2 site directory. Something like log4j-scala/log4j-scala-11.0. Once you have that we can modify the links

[Scala] Let's get version 11.0 going

I'm starting a new project at work using Scala 2.12, and I'd like to not depend on a snapshot version of the API. The maven site generates fine as far as I can tell from the Jenkins job, but I'm not sure how to appropriately integrate it into the core site. I'd like to start a release candidate

Re: Scala

ven-site-plugin to generate the Scala site. That's > just the easy way to do it in theory, though I find it cumbersome. If you > know of any better documentation generator that we could use there (or even > in log4j-core), please let us know! > > On 3 April 2017 at 04:0

Re: Scala

We don't have to use maven-site-plugin to generate the Scala site. That's just the easy way to do it in theory, though I find it cumbersome. If you know of any better documentation generator that we could use there (or even in log4j-core), please let us know! On 3 April 2017 at 04:06, Mikael

Re: Scala

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 S

Re: Scala

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 mad

Re: Scala

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

Re: Scala

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

Scala

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

Re: Roadmap for log4j-api-scala 11.0

jars > from all the sub projects. Obviously, the Scala distribution will only > contain the Scala jars. So the assembly xml file needs to be modified to > only include what is being released. The distribution source and zip are > what the ASF actually considers to be the release.

Re: Roadmap for log4j-api-scala 11.0

The distribution zip and tarball contain all the artifacts that are being released - i.e. the jars. The Log4j distribution includes all the jars from all the sub projects. Obviously, the Scala distribution will only contain the Scala jars. So the assembly xml file needs to be modified to only

Re: Roadmap for log4j-api-scala 11.0

I am a bit lost here. On Thu, Mar 9, 2017 at 4:56 PM, Mikael Ståldal wrote: > Change to what? > > On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers > wrote: > >> The instructions for what will be in the zip and tar balls will have to >> change.

Re: Roadmap for log4j-api-scala 11.0

Change to what? On Thu, Mar 9, 2017 at 4:32 PM, Ralph Goers wrote: > The instructions for what will be in the zip and tar balls will have to > change. > > Ralph > > On Mar 9, 2017, at 8:01 AM, Matt Sicker wrote: > > If you have time before the

Re: Roadmap for log4j-api-scala 11.0

The instructions for what will be in the zip and tar balls will have to change. Ralph > On Mar 9, 2017, at 8:01 AM, Matt Sicker wrote: > > If you have time before the weekend, you could try copying over the > log4j-distribution section from the main pom files. The "release"

Re: Roadmap for log4j-api-scala 11.0

If you have time before the weekend, you could try copying over the log4j-distribution section from the main pom files. The "release" maven profile should activate it I believe, so you should see the generated zips and tarballs. On 9 March 2017 at 03:01, Mikael Ståldal

Re: Roadmap for log4j-api-scala 11.0

Nice! Tell me if there is anything I can do to help out. On Thu, Mar 9, 2017 at 5:07 AM, Matt Sicker wrote: > We've established that this will need to be released before we can > officially remove the equivalent modules from the main log4j repository > (and release cycle).

Roadmap for log4j-api-scala 11.0

We've established that this will need to be released before we can officially remove the equivalent modules from the main log4j repository (and release cycle). Since the artifacts are no longer tied directly to log4j-api/core, we've also agreed that it makes sense to version it separately as well.

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

the next release. > Setup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 >

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

my time. > Setup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 >

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

, I think so. I'm not exactly sure on how to deploy a partial site like this or how releases of Log4j versus Log4j Scala API would coordinate site updates. > Setup build process for new Git repo logging-log4j-scala, including s

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

? > Setup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 >

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

of logging-log4j-scala into the main Log4j web site. The root site of logging-log4j-scala is not very useful. > Setup build process for new Git repo logging-log4j-scala, including site > > > Key:

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

which would be the best way to do so, but here are some ideas on how: * Make the Log4j Scala API site its own subdirectory like Log4j Boot will be and just include prominent links on the main Log4j site (and the Logging Services site). I kind of prefer this option because it's easier to implement

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

the sites for the modules in this repo into the main Log4j web site? > Setup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://is

Re: logging-log4j-scala git commit: Update README to be similar to logging-log4j2

I fixed that typo in the commons-build-plugin template as well. Looks like all the Commons projects have that exact typo! On 29 January 2017 at 10:52, Matt Sicker wrote: > Thanks! That's what I get for copying things from Commons instead of > writing them myself! :P > > On 28

Re: logging-log4j-scala git commit: Add intro to README

I noticed that right after I pushed it. Fixed in subsequent commit, thanks. On 28 January 2017 at 18:47, Remko Popma wrote: > Spelling nag: > introduced as in Log4j 2.8.1 -> introduced in > > Sent from my iPhone > > > On Jan 29, 2017, at 4:27, mattsic...@apache.org wrote:

Re: logging-log4j-scala git commit: Update README to be similar to logging-log4j2

Thanks! That's what I get for copying things from Commons instead of writing them myself! :P On 28 January 2017 at 18:25, Remko Popma wrote: > Spelling nag: > discuss you're changes -> your > (Contributing.md) > > > (Away from pc) Remko > > Sent from my iPhone > > > On

Re: logging-log4j-scala git commit: Add intro to README

Spelling nag: introduced as in Log4j 2.8.1 -> introduced in Sent from my iPhone > On Jan 29, 2017, at 4:27, mattsic...@apache.org wrote: > > introduced > +as in Log4j 2.8.1 - To unsubscribe, e-mail:

Re: logging-log4j-scala git commit: Update README to be similar to logging-log4j2

Spelling nag: discuss you're changes -> your (Contributing.md) (Away from pc) Remko Sent from my iPhone > On Jan 29, 2017, at 4:13, mattsic...@apache.org wrote: > > discuss you're changes - To unsubscribe, e-mail:

Fwd: logging-log4j-scala git commit: Add intro to README

ubject: logging-log4j-scala git commit: Add intro to README To: comm...@logging.apache.org Repository: logging-log4j-scala Updated Branches: refs/heads/master 7699ccc05 -> fe7b1334c Add intro to README Project: http://git-wip-us.apache.org/repos/asf/logging-log4j-scala/repo Commit: http:

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

ess for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 > Project: Log4j 2 >

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

a little messed up, though, because of some path assumptions: https://builds.apache.org/job/Log4jScala/site/ > Setup build process for new Git repo logging-log4j-scala, including site > > > Key:

[jira] [Closed] (LOG4J2-1428) Scala friedly overloading in MessageFactory(2)

[ https://issues.apache.org/jira/browse/LOG4J2-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1428. -- > Scala friedly overloading in MessageFactor

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

tup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 > Project: Log4j

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

parent pom with infrequent releases due to difficulties in sharing snapshot parent poms. > Setup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 >

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

for this? Or should I just include it here? I set up Jenkins for Log4j Boot which was pretty simple, and we can use basically the same setup for this repo (just using JDK 8 instead of JDK 7). > Setup build process for new Git repo logging-log4j-scala, including s

[jira] [Closed] (LOG4J2-1741) scala: add support for creating custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1741. -- > scala: add support for creating custom plug

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

[ https://issues.apache.org/jira/browse/LOG4J2-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15790936#comment-15790936 ] Mikael Ståldal commented on LOG4J2-1691: I think it's OK to use JDK 8 for the whole log4j2-scala

[jira] [Comment Edited] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

the menus (in site.xml for each module) need to be copied from logging-log4j2 so that the site has a consistent left side navigation bar regardless of which component you're in. Other than that, I don't think anything else is needed in the log4j-scala repo other than any other documentation you'd

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

to be copied from logging-log4j2 so that the site has a consistent left side navigation bar regardless of which component you're in. Other than that, I don't think anything else is needed in the log4j-scala repo other than any other documentation you'd like to add. I did recently learn that maven-site

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

-scala repo now? > Setup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 >

[jira] [Comment Edited] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

imported the base config files from logging-log4j2 into the logging-log4j-scala repo. I've also copied over the docs from the Log4j manual into this repo. The site build works the same as the Log4j one: {{mvn install site site:stage}}. What still remains is: * Configure Log4j site to link to Log4j

[jira] [Comment Edited] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

imported the base config files from logging-log4j2 into the logging-log4j-scala repo. I've also copied over the docs from the Log4j manual into this repo. The site build works the same as the Log4j one: {{mvn install site site:stage}}. What still remains is: * Configure Log4j site to link to Log4j

[jira] [Comment Edited] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

imported the base config files from logging-log4j2 into the logging-log4j-scala repo. I've also copied over the docs from the Log4j manual into this repo. The site build works the same as the Log4j one: {{mvn install site site:stage}}. What still remains is: * Configure Log4j site to link to Log4j

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

into the logging-log4j-scala repo. I've also copied over the docs from the Log4j manual into this repo. The site build works the same as the Log4j one: {{mvn install site site:stage}}. What still remains is: * Configure Log4j site to link to Log4j Scala sites (which could probably be committed

[jira] [Comment Edited] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

imported the base config files from logging-log4j2 into the logging-log4j-scala repo. I've also copied over the docs from the Log4j manual into this repo. The site build works the same as the Log4j one: {{mvn install site site:stage}}. What still remains is: * Configure Log4j site to link to Log4j

[jira] [Assigned] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

[ https://issues.apache.org/jira/browse/LOG4J2-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-1691: --- Assignee: Matt Sicker > Setup build process for new Git repo logging-log4j-scala, includ

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

for the scala repo. > Setup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 >

[jira] [Commented] (LOG4J2-1741) scala: add support for creating custom plugins

ild: KafkaLog4jAppender = new KafkaLog4jAppender(getName, getFilter, getLayout) } } {code} > scala: add support for creating custom plugins > -- > > Key: LOG4J2-1741 > URL: https://issues.apache.org/jira/

[jira] [Commented] (LOG4J2-1741) scala: add support for creating custom plugins

ut[_ <: Serializable], @PluginElement("Filters") filter: Filter): KafkaLog4jAppender = { new KafkaLog4jAppender(name, filter, layout) } } {code} > scala: add support for creating custom plugins > -- > >

[jira] [Commented] (LOG4J2-1741) scala: add support for creating custom plugins

when we (Log4j devs) write code examples to promote future proofing for binary compatibility. It might be a bit of YAGNI, but I've not met an Appender yet that does not another feature at some point. > scala: add support for creating custom plug

[jira] [Updated] (LOG4J2-1741) scala: add support for creating custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PJ Fanning updated LOG4J2-1741: --- Attachment: log4j2-sample.zip > scala: add support for creating custom plug

[jira] [Updated] (LOG4J2-1741) scala: add support for creating custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PJ Fanning updated LOG4J2-1741: --- Attachment: (was: log4j2-sample.zip) > scala: add support for creating custom plug

[jira] [Updated] (LOG4J2-1741) scala: add support for creating custom plugins

at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.findFactoryMethod(PluginBuilder.java:224) > scala: add support for creating custom plugins > -- > > Key: LOG4J2-1741 > URL: https://issues.apache.

[jira] [Updated] (LOG4J2-1741) scala: add support for creating custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1741: --- Labels: scala (was: ) > scala: add support for creating custom plug

[jira] [Assigned] (LOG4J2-1741) scala: add support for creating custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1741: -- Assignee: Mikael Ståldal > scala: add support for creating custom plug

[jira] [Commented] (LOG4J2-1741) scala: add support for creating custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760862#comment-15760862 ] Mikael Ståldal commented on LOG4J2-1741: I just tried to write a simple appender in Scala

[jira] [Reopened] (LOG4J2-1741) scala: add support for creating custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reopened LOG4J2-1741: > scala: add support for creating custom plug

[jira] [Closed] (LOG4J2-1741) scala: add support for creating custom plugins

and in the end, it was easier for me to use logback. > scala: add support for creating custom plugins > -- > > Key: LOG4J2-1741 > URL: https://issues.apache.org/jira/browse/LOG4J2-1741 > Project: Log4j

[jira] [Commented] (LOG4J2-1741) scala: add support for creating custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15755010#comment-15755010 ] Mikael Ståldal commented on LOG4J2-1741: As far as I can see, the Scala compiler generates

[jira] [Closed] (LOG4J2-1742) scala: add support for creating custom plugins

[ https://issues.apache.org/jira/browse/LOG4J2-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PJ Fanning closed LOG4J2-1742. -- Resolution: Duplicate > scala: add support for creating custom plug

[jira] [Created] (LOG4J2-1742) scala: add support for creating custom plugins

PJ Fanning created LOG4J2-1742: -- Summary: scala: add support for creating custom plugins Key: LOG4J2-1742 URL: https://issues.apache.org/jira/browse/LOG4J2-1742 Project: Log4j 2 Issue Type

[jira] [Created] (LOG4J2-1741) scala: add support for creating custom plugins

PJ Fanning created LOG4J2-1741: -- Summary: scala: add support for creating custom plugins Key: LOG4J2-1741 URL: https://issues.apache.org/jira/browse/LOG4J2-1741 Project: Log4j 2 Issue Type

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

to work, then we can worry about CI. > Setup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/bro

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

ess for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 > Project: Log4j

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

ess for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 > Project: Log4j 2 >

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

ild process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 > Project: Log4j 2 >

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

epo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 > Project: Log4j 2 > Issue Type: Task

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

tup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 > Project: Log4j

[jira] [Commented] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

. [~ralphgoers]? > Setup build process for new Git repo logging-log4j-scala, including site > > > Key: LOG4J2-1691 > URL: https://issues.apache.org/jira/browse/LOG4J2-1691 >

Re: Scala repo

Yes, when we have the build process (including documentation/site) working for the new repo. On Sun, Nov 13, 2016 at 3:22 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > Now that we have a populated Scala repo, shall we remove the Scala modules > from the main repo? > > Ga

Re: Log4j RAT check fail in Scala module

: > I am seeing a RAT check failure in a Scala module: > > See http://pastebin.com/D1Vbk5px > > Thoughts? > > Gary > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition > <https://www.amazon.com

Log4j RAT check fail in Scala module

I am seeing a RAT check failure in a Scala module: See http://pastebin.com/D1Vbk5px Thoughts? Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8=1789=9325=1617290

[jira] [Assigned] (LOG4J2-1690) Scala wrapper for Context map

[ https://issues.apache.org/jira/browse/LOG4J2-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal reassigned LOG4J2-1690: -- Assignee: Mikael Ståldal > Scala wrapper for Context

[jira] [Created] (LOG4J2-1691) Setup build process for new Git repo logging-log4j-scala, including site

Mikael Ståldal created LOG4J2-1691: -- Summary: Setup build process for new Git repo logging-log4j-scala, including site Key: LOG4J2-1691 URL: https://issues.apache.org/jira/browse/LOG4J2-1691 Project

[jira] [Commented] (LOG4J2-1661) Support Scala 2.12.0

process to work for the new Git repo. > Support Scala 2.12.0 > > > Key: LOG4J2-1661 > URL: https://issues.apache.org/jira/browse/LOG4J2-1661 > Project: Log4j 2 > Issue Type: Improvement > Comp

[jira] [Created] (LOG4J2-1690) Scala wrapper for Context map

Mikael Ståldal created LOG4J2-1690: -- Summary: Scala wrapper for Context map Key: LOG4J2-1690 URL: https://issues.apache.org/jira/browse/LOG4J2-1690 Project: Log4j 2 Issue Type: New Feature

Scala Index

We are now listed here: https://index.scala-lang.org/apache/logging-log4j2 -- [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

Re: New Git repo logging-log4j-scala

te is generated. > > Ralph > > Ralph > > On Nov 9, 2016, at 7:53 AM, Matt Sicker <boa...@gmail.com> wrote: > > 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 > expe

Re: New Git repo logging-log4j-scala

That is pretty much it. The links need to be added to site.xml. You should look in src/site to see how the Log4j 2 site is generated. Ralph Ralph > On Nov 9, 2016, at 7:53 AM, Matt Sicker <boa...@gmail.com> wrote: > > I'm thinking that the log4j-scala site and docs can be g

Re: New Git repo logging-log4j-scala

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 d

[jira] [Commented] (LOG4J2-1661) Support Scala 2.12.0

[ https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15650841#comment-15650841 ] Mikael Ståldal commented on LOG4J2-1661: Adding Scala 2.12 support to new log4j-scala Git repo

Re: New Git repo logging-log4j-scala

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 integr

Re: New Git repo logging-log4j-scala

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

New Git repo logging-log4j-scala

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

[jira] [Comment Edited] (LOG4J2-1661) Support Scala 2.12.0

to be quite easy (apart from requiring Java 8 for the build process), see branch LOG4J2-1661. was (Author: mikaelstaldal): Seems to be quite easy (apart from require Java 8 for the build process), see branch LOG4J2-1661. > Support Scala 2.12.0 > > >

[jira] [Commented] (LOG4J2-1661) Support Scala 2.12.0

for the build process), see branch LOG4J2-1661. > Support Scala 2.12.0 > > > Key: LOG4J2-1661 > URL: https://issues.apache.org/jira/browse/LOG4J2-1661 > Project: Log4j 2 > Issue Type: Improvement >

[jira] [Commented] (LOG4J2-1661) Support Scala 2.12.0

/ > Support Scala 2.12.0 > > > Key: LOG4J2-1661 > URL: https://issues.apache.org/jira/browse/LOG4J2-1661 > Project: Log4j 2 > Issue Type: Improvement > Components: API >Affects Versions: 2.7

Re: New version of Scala?

at 08:30, Mikael Ståldal <mikael.stal...@magine.com> wrote: > If someone create the new Git repo and give me access to it, I can > populate it. > > On Fri, Nov 4, 2016 at 12:18 PM, Mikael Ståldal <mikael.stal...@magine.com > > wrote: > >> I am OK with moving

[jira] [Commented] (LOG4J2-1661) Support Scala 2.12.0

[ https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15636357#comment-15636357 ] Mikael Ståldal commented on LOG4J2-1661: Notify here when done: https://github.com/scala/make

Re: New version of Scala?

If someone create the new Git repo and give me access to it, I can populate it. On Fri, Nov 4, 2016 at 12:18 PM, Mikael Ståldal <mikael.stal...@magine.com> wrote: > I am OK with moving the Scala modules to a separate Git repository and > build, given that we keep the groupId and art

Re: New version of Scala?

I am OK with moving the Scala modules to a separate Git repository and build, given that we keep the groupId and artifactIds, so that the users will not notice any difference. It would probably be a good idea to try to keep the version numbers in sync also. On Thu, Nov 3, 2016 at 11:39 PM, Ralph

Re: New version of Scala?

I don’t have a problem with it using the same groupId. Ralph > On Nov 3, 2016, at 1:06 PM, Matt Sicker <boa...@gmail.com> wrote: > > Can we get a new git repo in the logging project for the Scala extensions > then? > > Also, if we use a different get repo, shou

Re: New version of Scala?

; >> Can we get a new git repo in the logging project for the Scala extensions >> then? >> >> Also, if we use a different get repo, should we continue releasing these >> log4j extras under the same group ID? >> >> On 3 November 2016 at 14:57, Ralph Goers <

Re: New version of Scala?

Same group ID is yes for me. This is just a tool chain issue. Gary On Thu, Nov 3, 2016 at 1:06 PM, Matt Sicker <boa...@gmail.com> wrote: > Can we get a new git repo in the logging project for the Scala extensions > then? > > Also, if we use a different get repo, should we

Re: New version of Scala?

Can we get a new git repo in the logging project for the Scala extensions then? Also, if we use a different get repo, should we continue releasing these log4j extras under the same group ID? On 3 November 2016 at 14:57, Ralph Goers <ralph.go...@dslextreme.com> wrote: > Since we won’t

Re: New version of Scala?

Since we won’t be using Java 8 to perform releases any time soon I suggest the Scala support move to a different git repo with a separate build. Ralph > On Nov 3, 2016, at 8:20 AM, Matt Sicker <boa...@gmail.com> wrote: > > This one will require Java 8 to compile. We'll need to u

Re: New version of Scala?

On Nov 3, 2016 8:55 AM, "Matt Sicker" <boa...@gmail.com> wrote: > >> So yes, it does sound like we'd need a 2.12 module now as well. I'm not >> exactly sure how to best configure maven to do a build like this. >> >> On 3 November 2016 at 10:31, Mikae

[jira] [Updated] (LOG4J2-1661) Support Scala 2.12.0

[ https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1661: --- Affects Version/s: 2.7 > Support Scala 2.12.0 > > >

[jira] [Updated] (LOG4J2-1661) Support Scala 2.12.0

[ https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1661: --- Component/s: API > Support Scala 2.12.0 > > >

  1   2   3   >