I won't be able to help out with that until next week at the earliest. I'm
preparing a presentation this weekend (coincidentally one about Scala
actually), but things are starting to simmer down finally.
On 7 July 2017 at 13:39, Mikael Ståldal wrote:
> It would be good if you could finalize the
Done.
On 2017-07-05 21:15, Mikael Ståldal wrote:
There are a couple of almost finished PRs on GitHub which would be nice
to include. I'll have a look at LOG4J2-1923 (PR #81) in the comming days.
It would be good if you could finalize the release of
logging-log4j-scala. I am ready to help.
On 2017-07-07 01:04, Matt Sicker wrote:
The code as is should be ready for source and binary artifacts I believe. I
don't recall if there was a distribution zip task already set up, though,
and I beli
The code as is should be ready for source and binary artifacts I believe. I
don't recall if there was a distribution zip task already set up, though,
and I believe that's the minimal required artifacts for an Apache release.
On 6 July 2017 at 17:19, Gary Gregory wrote:
> On Thu, Jul 6, 2017 at 2
On Thu, Jul 6, 2017 at 2:31 PM, Matt Sicker wrote:
> I attempted a release, and we fixed something, but I was still unsure as to
> how to build the website as the site:stage goal fails with missing file
> errors if I recall correctly. Since then, I've been busy with a short term
> work project ea
I attempted a release, and we fixed something, but I was still unsure as to
how to build the website as the site:stage goal fails with missing file
errors if I recall correctly. Since then, I've been busy with a short term
work project eating up all my energy, so I haven't had a chance to make
anot
Don’t we still need to get Scala integrated into the web site? Can we do that
before the 2.9 release? Or has a Scala release not been done yet?
Ralph
> On Jul 6, 2017, at 1:15 PM, Mikael Ståldal wrote:
>
> Yes, I think that the 11.0 release of the Scala API should only be what we
> currently
Yes, I think that the 11.0 release of the Scala API should only be what
we currently have in 2.8.2 plus Scala 2.12 support plus the already
implemented ThreadContext wrapper in LOG4J2-1690.
Basically just release what we currently have in the logging-log4j-scala
Git repo.
On 2017-07-05 23:2
With all the compatibility issues with Android Java, it's no wonder Oracle
tried to sue them over it...
On 6 July 2017 at 04:51, Gary Gregory wrote:
> Here is another Java 9 headache WRT Android:
>
> https://issues.apache.org/jira/browse/LOG4J2-1921?
> focusedCommentId=16076259&page=com.atlassia
Here is another Java 9 headache WRT Android:
https://issues.apache.org/jira/browse/LOG4J2-1921?focusedCommentId=16076259&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16076259
Gary
On Wed, Jul 5, 2017 at 2:28 PM, Matt Sicker wrote:
> So 11.0 would have the old
So 11.0 would have the old name, and 12.0 would have the new name? That
would be fine with me. That also gives us an opportunity to look into
Scalameta for simpler macro portability going forward considering I keep
seeing deprecation warnings all over the place in the existing macro API.
On 5 July
But this long package name is already out released for Scala 2.10 and
2.11. I suggest we release for 2.12 with the same package name, and then
maybe change it in the next release.
On 2017-07-05 22:10, Matt Sicker wrote:
I've been using the 2.12 snapshot for now, but I'd rather get a released
I've been using the 2.12 snapshot for now, but I'd rather get a released
solution. I have one thought that our package name in the Scala API is too
long as most Scala libraries I've used do not use the reverse DNS package
naming scheme. We may be better off renaming it to just log4j as the root
pac
An important customer for us is Apache HttpClient for which I already
switched to Log4j2 in the 5.0 (alpha level) branch. I am on the PMC there
as well. Any help to get Android cooking for Log4j modules would be g r e a
t. I am on deadline at work until the end of the month so my time is
limited an
There are a couple of almost finished PRs on GitHub which would be nice
to include. I'll have a look at LOG4J2-1923 (PR #81) in the comming days.
It would be good to do something about LOG4J2-1921 (Android support). I
guess it boils down to what level of support for Android we want. Is it
enou
I'd be alright with that. We'll just have to push back some goals to 2.10.
I have an outstanding properties change I want to merge, but I don't have
time at the moment to go through and make all the documentation updates it
requires, so I can push that for 2.10. Same goes for the Scala repo since I
It should be possible. We need to take a hard look at the bugs that have been
reported. Some seem pretty important.
Ralph
> On Jul 4, 2017, at 2:00 PM, Gary Gregory wrote:
>
> Hi All,
>
> I would live to see our 2.9 at the end of July at the latest. Big deadline
> for me. Is that a possibili
Hi All,
I would live to see our 2.9 at the end of July at the latest. Big deadline
for me. Is that a possibility?
Gary
18 matches
Mail list logo
