Cannot load LogbackConfigListener on JDK 6 about logback-extensions

[magixsource]

Yes,How to make compile version low than 1.7 ?

In the parent pom.xml file at https://github.com/qos-ch/logback-extensions/blob/master/pom.xml, the JDK version is specified as

<jdk.version>1.7</jdk.version>

If you update it to
<jdk.version>1.5</jdk.version>
you will be able support more JDK versions and the project will be more usable.
Thanks.

[oysteinhagenpettersen]

Any plans to support java 6?

Thanks.

[mikereinhold]

The Logback team polled the dev and user community a while back asking
about migrating the project to a newer Java specification in order to be
able to take advantage of new language features at the cost of
compatibility. At that point in time, there was little to no pushback from
the community because Oracle has had Java 5 & 6 in an End of Support state
for quite a while.

Depending on what newer language features have been used by commits merged
into the project since that time, just changing the JDK version in the pom
will most likely break the build.

Is there a particular reason your project is stuck on JDK 5 or 6 so you can
use the most recent versions? If you absolutely need JDK 5 or 6, you'll
have to use an older version of Logback that was built prior to the change
(not sure which version had that off the top of my head, but you can find
it in the release notes I'm sure).

Regards,
Mike

On Thu, Feb 5, 2015 at 9:44 AM, oysteinhagenpettersen <
[email protected]> wrote:

Any plans to support java 6?

Thanks.

—
Reply to this email directly or view it on GitHub
#25 (comment)
.

Mike Reinhold | Co-Founder

[oysteinhagenpettersen]

Thanks for you comment. Cannot move away from Java6 at the moment. Will review the release notes and use an older version.

Regs
Oystein

[tony19]

@magixsource, to rebuild logback-extensions with a different JDK version, specify jdk.version=<version> from the command line. For example, to specify 1.6:

mvn clean package -Djdk.version=1.6

[tony19]

@mikereinhold, the poll you mention was specific to logback proper IIRC. It seems logback-extensions should at least match the JDK versions that logback supports to maintain compatibility. And that's a trivial change with minimal impact.