Re: [orbit-dev] Extending the Orbit Scope

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

For the record, m2e does not want to maintain our own slf4j binding. If
Platform provided functionality we needed (I can elaborate if anyone is
planning to work on this), we'd be more than happy to use that.

For the reference, here is the old cross-project-issues thread where we
proposed slf4j support
https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg05659.html

-- 
Regards,
Igor

On Wed, May 3, 2017, at 08:12 AM, Gunnar Wagenknecht wrote:
> Sorry, overlooked your two other questions:
> 
> > On 3. May 2017, at 13:53, Mickael Istria <mistria@xxxxxxxxxx> wrote:
> 
> > Have you evaluated contributing such bundles to Equinox or Platform instead?
> 
> Sort of ... I don't like being bound to the Platform/Equinox cycle.
> Adding a new SLF4J version to Orbit and (when necessary) changing the
> binding is a quick operation.
> 
> Having said that, I can see an issue here with how Orbit does "releases".
> It doesn't. We simply declare published bits from master as recommended
> builds.
> 
> > What are the current clients for the bundle you're proposing?
> 
> So far I see two: EGit and M2E. Potentially anyone in the IDE. However,
> M2E has an alternate solution with a Logback appender and some specific
> configuration. It's now widely known, though. 
> 
> -Gunnar
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/orbit-dev