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 in the
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
o 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 Ståldal <mai
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:
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 wrote:
> I'm not too experienced with it, but now that the Scala APIs are i
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 wrote:
> And don't mind the site commit I made earlier. That was fr
a test randomly decided to
> fail at the worst possible time.
>
> On 2 April 2017 at 15:11, Ralph Goers wrote:
>
>> Has a Scala release been performed? The site needs to be deployed before
>> I can modify the l
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 wrote:
> Has a Scala release been performed? The site needs to be
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
e 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. The source distribution
> shoul
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
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.
>>
>> Ralph
>>
>> On Mar 9, 2017, at 8:01 AM, Matt Sicke
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 weekend, you could try copying over the
> log4j-dis
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" maven
> profile sh
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 wrote:
> Nice! Tell me if
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). Since the artifacts ar
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.
done before we make the next release.
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira
eems to be sucking up my time.
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira
this, but in theory, yeah, 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-scal
main Log4j site 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
&g
site for the modules 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, includi
I'm not exactly sure 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 bec
now integrate 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
>
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 January 2017 at 18:
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:
> >
> > introduced
> >
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 Jan 29, 2017, at 4:13, mat
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: log4j-dev-unsubscr...@loggin
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: log4j-dev-
I just realized that I added that this brings in log4j-core by default, but
it doesn't. We were discussing this before, but I don't remember if we
decided whether or not to do that.
-- Forwarded message --
From:
Date: 28 January 2017 at 13:27
Subject: logging-log4j
; 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: Lo
ding. The site looks 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
>
>
>
[
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
7;s do it here.
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira/browse/LOG4J2-1691
>
set up is a common 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
>
>
>
for configuring CI 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, includi
[
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
[
https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikael Ståldal resolved LOG4J2-1741.
Resolution: Not A Problem
> scala: add support for creating custom plug
8 for the whole log4j2-scala repo.
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org
9 PM:
---
I think 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
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 like to add.
I
o be done in the log4j-scala repo now?
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira
5 PM:
---
I've 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
5 PM:
---
I've 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
5 PM:
---
I've 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
iles 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 Scala sites (which cou
3 PM:
---
I've 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
[
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
aven-site-plugin for the scala repo.
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org
f build: KafkaLog4jAppender = new KafkaLog4jAppender(getName, getFilter,
getLayout)
}
}
{code}
> scala: add support for creating custom plugins
> --
>
> Key: LOG4J2-1741
> URL: https://issues.apache.org/j
ut") layout: Layout[_ <: Serializable],
@PluginElement("Filters") filter: Filter): KafkaLog4jAppender = {
new KafkaLog4jAppender(name, filter, layout)
}
}
{code}
> scala: add support for creating custom plugins
>
k we should use Builders 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 cu
[
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
[
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
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.ap
[
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
[
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
nder in Scala, and it worked without
problems:
{code}
import org.apache.logging.log4j.core.appender.AbstractAppender
import org.apache.logging.log4j.core.config.plugins.{Plugin, PluginAttribute,
PluginElement, PluginFactory}
import org.apache.logging.log4j.core.{Filter, Layout, LogEvent}
@Pl
[
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
king 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
>
[
https://issues.apache.org/jira/browse/LOG4J2-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755010#comment-15755010
]
Mikael Ståldal commented on LOG4J2-1741:
As far as I can see, the Scala comp
[
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
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
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
aven site build 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.apa
like that.
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira/browse/LOG4J2-1691
>
0 PM:
---
Sorry - I have been swamped at work. I have never used Travis.
was (Author: ralphgoers):
Sorry - I have been swamped at work.
> Setup build process for new Git repo logging-log4j-scala, includi
work.
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira/browse/LOG4J2-1691
>
avis?
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira/browse/LOG4J2-1691
>
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
>
the weekend.
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira/browse/LOG4J2-1691
>
uild to work. [~ralphgoers]?
> Setup build process for new Git repo logging-log4j-scala, including site
>
>
> Key: LOG4J2-1691
> URL: https://issues.apache.org/jira
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
wrote:
> Now that we have a populated Scala repo, shall we remove the Scala modules
> from the main repo?
>
> Gary
>
> --
> E-Mail: g
eck 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/re
Now that we have a populated Scala repo, shall we remove the Scala modules
from the main repo?
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&camp=1789&cr
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&camp=1789&a
[
https://issues.apache.org/jira/browse/LOG4J2-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657473#comment-15657473
]
Mikael Ståldal commented on LOG4J2-1690:
In Git master (logging-log4j-scala
[
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
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
d to get the build 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: Improvem
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
Very cool!
On 10 November 2016 at 04:47, Mikael Ståldal
wrote:
> 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 Stockho
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 co
t; Ralph
>
> On Nov 9, 2016, at 7:53 AM, Matt Sicker 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
> experienced with the maven site plugin either.
>
&g
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 wrote:
>
> I'm thinking that the log4j-scala site and docs can be generated on its own,
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
wrote:
> How do we move forward with this?
[
https://issues.apache.org/jira/browse/LOG4J2-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650841#comment-15650841
]
Mikael Ståldal commented on LOG4J2-1661:
Adding Scala 2.12 support to new l
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 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
> l
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
wrote:
> I have now populated the new
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
8 PM:
-
Seems 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
from require Java 8 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
>
cala-lang.org/
> Support Scala 2.12.0
>
>
> Key: LOG4J2-1661
> URL: https://issues.apache.org/jira/browse/LOG4J2-1661
> Project: Log4j 2
> Issue Type: Improvement
> Components: AP
at 08:30, Mikael Ståldal
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 > wrote:
>
>> I am OK with moving the Scala modules to a separate Git repository and
>> build, give
ttps://github.com/scala/make-release-notes/blob/2.12.x/projects-2.12.md
> Support Scala 2.12.0
>
>
> Key: LOG4J2-1661
> URL: https://issues.apache.org/jira/browse/LOG4J2-1661
> Project: Log4j 2
>
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
wrote:
> 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
>
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
I don’t have a problem with it using the same groupId.
Ralph
> On Nov 3, 2016, at 1:06 PM, Matt Sicker 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 continue releasing the
n the components themselves remain untouched.
On 3 November 2016 at 17:13, Gary Gregory wrote:
> 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 wrote:
>
>> Can we get a new git repo in the logging pro
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 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 continue releasing these
&g
1 - 100 of 275 matches
Mail list logo
