Hi

Indeed, and java.util.logging and logback.

My attempts to use SLF4J in OCL have foundered. Migrating the plugins was easy, although RSI-inducing. Test harnesses which represent an 'overall application' must continue to use their log4j proprietary tweaks, but making this work enters a hotchpotch world of fragments and smart class loaders. Eventually I gave up; too time consuming for purely cosmetic value. It is far from clear which of the three rival LOG4J for SLF4J in Orbit is the right one. After major failures with Apache conflicts, I settled on the fragment, whose fragment-host readme-bundles suggests an out of date predecessor to Require-Capability that doesn't seem to work for all the class loaders. AFAICT SLF4J and/or P2 fragment declarations are not yet ready for prime time. I never even got as far as struggling to make the migrated tests work on Tycho.

Wrt Xtext, there will almost certainly be some new magic to ensure that an Xtext application has a fallback Log4j logger rather than the default NOP logger.

Regards

Ed Willink

On 25/01/2020 14:23, Aleksandar Kurtakov wrote:


On Sat, Jan 25, 2020 at 10:56 AM Ed Willink <[email protected] <mailto:[email protected]>> wrote:

    Hi

    I've started to action this for OCL;
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=559532

    and hit a silly problem; who redistributes SLF4J?

    If it's standard, surely the platform should redistribute so that
    a copy
    can be found in e.g. eclipse-SDK-4.14-win32-x86_64.zip ?


Platform doesn't use slf4j nor log4j thus it makes no sense to redistribute them. I should add to the mix that there is the OSGi LogService which might be the proper API to use in OSGi projects as it will not add yet another dependency. I'm not an expert in the area so I would appreciate some more guidance in case what I said is not correct.


    There is no SLF4J there. There is no log4j either. Where does
    log4j come
    form? It turns out that EGit redistributes both log4j and SLF4J. Very
    helpful, but surely not right?

    What is the preferred policy for redistribution of SLF4J? Does every
    project need to redistribute it itself to avoid piggy-backing on
    EGit or
    mandating that users manually add Orbit to their Install sites?

    Regards

    Ed Willink

    _______________________________________________
    cross-project-issues-dev mailing list
    [email protected]
    <mailto:[email protected]>
    To change your delivery options, retrieve your password, or
    unsubscribe from this list, visit
    https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Alexander Kurtakov
Red Hat Eclipse Team

_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to