[logback-dev] volunteer to work out the steps for building logback with M2Eclipse.
gordillo.ramon at gmail.com
Thu Feb 25 22:23:52 UTC 2016
First, the project structure makes a little difficult to set up everything.
You need to import the subprojects (logback-core, logback-classic, etc).
I have run in some test failures in Eclipse Mars on Centos 7.1 for
expected:<7> but was:<8>
Tests run: 515, Failures: 2, Errors: 0, Skipped: 6
Other than that, Eclipse does not like pretty much when you mix different
languages in the same project. I have this kind of issues not in the build,
which I have not been able to do because the previous tests errors but on
the class resolution. It happened in logback-classic (java and groovy
clases), not in logback-access.
2016-02-25 17:12 GMT+01:00 Ceki Gulcu <ceki at qos.ch>:
> Hello all,
> As a longtime user of the Maven eclipse:eclipse plugin to create Eclipse
> .project and .classpath files, I rarely rely on the m2eclipse plugin. The
> However, most Eclipse users prefer to use M2Eclipse. I have recently made
> an attempt to build logback with the Maven nature, i.e. with M2Eclipse.
> Unfortunately, I ran into compilation problems with groovy related classes.
> For what it is worth, the steps required to building logback using files
> generated with Maven eclipse:eclipse plugin are described in
> It would be nice if a knowledgeable volunteer could help work out the
> steps for building logback with M2Eclipse.
> Best regards,
> logback-dev mailing list
> logback-dev at qos.ch
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the logback-dev