[orbit-dev] Modifying source of a 3rd party library

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[orbit-dev] Modifying source of a 3rd party library

From: Simon Kaegi <Simon_Kaegi@xxxxxxxxxx>
Date: Mon, 9 Feb 2009 12:07:35 -0500
Delivered-to: orbit-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/orbit-dev>
List-help: <mailto:orbit-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/orbit-dev>, <mailto:orbit-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/orbit-dev>, <mailto:orbit-dev-request@eclipse.org?subject=unsubscribe>

I've run into a situation with -- https://bugs.eclipse.org/bugs/show_bug.cgi?id=262641

One of the 3rd party libraries we use (and is no longer the active stream) has a bug in it that is likely not to be fixed.
It is fixed in a future release however due to JRE requirements we're unlikely to adopt it until the whole platform requires Java 5.

The fix is easy enough to make and I'm wondering if we have or perhaps should have any process around this sort of thing.
Any thoughts?

-Simon

Follow-Ups:
- RE: [orbit-dev] Modifying source of a 3rd party library
  - From: Oberhuber, Martin

References:
- [orbit-dev] Wrapped or not wrapped?
  - From: Oliver Wolf
- Re: [orbit-dev] Wrapped or not wrapped?
  - From: Oisin Hurley

Prev by Date: Re: [orbit-dev] David Williams vote summary
Next by Date: Re: [orbit-dev] Project Leadership
Previous by thread: Re: [orbit-dev] Wrapped or not wrapped?
Next by thread: RE: [orbit-dev] Modifying source of a 3rd party library
Index(es):
- Date
- Thread

Breadcrumbs