Agree for option (disagree it is not common but that's not important) just
because there is no real choice else we would need to handle all libraries
and all versions which is clearly a no go for me.
Just a side note on the shared code: fully agree until log is exposed in
the API and can be reused
Once again thanks for feedback.
In order to finish discussion and not return to this topic again I will try
to update documentation about logging in Maven plugins ... so I see the
message, as Tamás wrote
- Maven core and ecosystem uses SLF4J.
- Maven Plugin code should use Plugin Api for logging
> perfectly valid solution (classloader)
This is a workaround any plugin developer hates to be honest.
Guillaume started to make the plugin ClassRealm more customizable, this can
be an option but still, means we don't leak slf4j.
I fully agree the issue is how we expose it to plugins and extension
So, you see problems in some plugins (again, what is the ratio we speak
about?)
using some frameworks, and then you tell the perfectly valid solution
(classloader)...
And regarding slf4j, should I reiterate what Ceki repeated several times?
Sorry, but these are non-issues IMHO.
Or to rephrase: w
Le ven. 4 nov. 2022 à 13:17, Tamás Cservenák a écrit :
> Howdy,
>
> Will we keep asking the same questions over and over again? Until we get
> the "wanted" answer?
>
> Maven core and ecosystem uses SLF4J API. Full stop.
>
> Just use SLF4J API, and you will get a pre-configured back-end as well.
>
Howdy,
Will we keep asking the same questions over and over again? Until we get
the "wanted" answer?
Maven core and ecosystem uses SLF4J API. Full stop.
Just use SLF4J API, and you will get a pre-configured back-end as well.
Done.
Now,. this story keeps popping up: "plugin developers using fram
Hi,
+1 for JUL, it is the most portable and less intrusive solution since it is
built-in, graalvm friendly (mvnd) and any backend compatible (slf4j,
logback directly, log4j2, ...).
It is always a pity for a solution which can embedded user code -
mojo/extensions - to force a logging library IMHO s
And let's not forget that Log4j also is a facade API:
https://logging.apache.org/log4j/2.x/manual/api-separation.html
Gary
On Fri, Nov 4, 2022, 06:56 Slawomir Jaranowski
wrote:
> Hi,
>
> I want to start ( again :-) ) a discussion about logging in Maven plugins.
>
> First I agree that plugin de
Hi,
I want to start ( again :-) ) a discussion about logging in Maven plugins.
First I agree that plugin developers should use logging methods provided by
Plugin api.
But we can not expect plugin developers to write everything from scratch.
In many cases they may want to use an external library
+1
I will fix the IT tests for next. release
śr., 2 lis 2022 o 12:54 Slawomir Jaranowski
napisał(a):
> Build locally from source-releases.zip - tests failed ... the same
> situation on Jenkins
>
> Is it acceptable?
>
>
> czw., 27 paź 2022 o 13:11 Guillaume Nodet napisał(a):
>
>> Hi,
>>
>> I've
10 matches
Mail list logo
