I have fixed the OSGi problem and made the changes you recommended. Please make
sure all the OSGi stuff is correct now. I believe there are still problems
with the release notes and I will be addressing those.
Ralph
> On Jun 17, 2023, at 10:11 AM, Ralph Goers wrote:
>
> Yes, I started on the
Yes, I started on the fix for what you reported and ran into this. I had to
introduce a dependency for the plugin annotation processor to log4j core to
ensure it was created prior to log4j-core being built. That causes a dependency
to be added to the processor in OSGi, but that isn’t an OSGi mod
Hi Ralph,
On Fri, 16 Jun 2023 at 22:37, Ralph Goers wrote:
>
> Any chance you can commit a fix?
Sure, I'll commit a fix. For some (other?) reason the tests in
`log4j-osgi` are failing on the CI. Not sure what is the problem.
Piotr
I'm ok either way, this is an alpha after all.
Gary
On Fri, Jun 16, 2023, 15:16 Matt Sicker wrote:
> I agree the OSGi metadata should be fixed for this release.
>
> > On Jun 16, 2023, at 1:41 PM, Piotr P. Karwasz
> wrote:
> >
> > Hi Ralph,
> >
> > On Thu, 15 Jun 2023 at 22:12, Ralph Goers
>
Any chance you can commit a fix?
Ralph
> On Jun 16, 2023, at 11:41 AM, Piotr P. Karwasz
> wrote:
>
> Hi Ralph,
>
> On Thu, 15 Jun 2023 at 22:12, Ralph Goers wrote:
>>
>> This is a vote to release Log4j 3.0.0-alpha, the first release the Log4j 3.x
>> series.
>>
>> Please download, test, an
I agree the OSGi metadata should be fixed for this release.
> On Jun 16, 2023, at 1:41 PM, Piotr P. Karwasz wrote:
>
> Hi Ralph,
>
> On Thu, 15 Jun 2023 at 22:12, Ralph Goers wrote:
>>
>> This is a vote to release Log4j 3.0.0-alpha, the first release the Log4j 3.x
>> series.
>>
>> Please do
Hi Ralph,
On Thu, 15 Jun 2023 at 22:12, Ralph Goers wrote:
>
> This is a vote to release Log4j 3.0.0-alpha, the first release the Log4j 3.x
> series.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
I a
Hi all,
On Fri, 16 Jun 2023 at 06:15, I wrote:
> > Changes in this version include:
> > (...)
> > • Update Apache Flume from 1.7.0 to 1.8.0. (for LOG4J2-2082 by Gary
> > Gregory)
> > • Update Eclipse javax.persistence from 2.1.1 to 2.2.0. (for
> > LOG4J2-2083 by Gary Gregory)
> >
This was already addressed in `log4j-tools` 0.3.0 with the new
`release.changelogEntryCount` index template property introduced. Using
that we can skip effectively empty releases in the changelog index. I have
updated the `src/changelog/.index.adoc.ftl` in both `2.x` and `main` to
take advantage of
I thought I fixed that. Unfortunately, the plugin moves stuff from the 3.x
directory to the release directory and leaves the 3.x directory there. Then
when you run the site build it includes that empty 3.x directory. To fix that I
have to delete the 3.x directory and then recreate it after the
Hi Ralph,
On Thu, 15 Jun 2023 at 22:12, Ralph Goers wrote:
>
> This is a vote to release Log4j 3.0.0-alpha, the first release the Log4j 3.x
> series.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
>
>
11 matches
Mail list logo
