[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [orbit-dev] What to do about a bug in an Orbit provided bundle?
- From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
- Date: Fri, 5 Mar 2010 16:39:13 +0100
- Delivered-to: firstname.lastname@example.org
- Thread-index: Acq8V4IqszFxbKBGTNOtGNgkGVIUlAAIfBuA
- Thread-topic: [orbit-dev] What to do about a bug in an Orbit provided bundle?
In the concrete case of Jcraft JSch, there's actually 2 possibilities
(a) Mailinglist https://lists.sourceforge.net/lists/listinfo/jsch-users
. Really responsive.
(b) The JSch maintainer typically also listens on Platform Core/Team
Bugzilla's related to CVS, in case your bug is very tied to Eclipse or
easily reproducable within Eclipse that would also be an option.
I'm also interested in JSch, so I'd appreciate if you could keep me in
[mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of Michal Ruzicka
Sent: Friday, March 05, 2010 12:32 PM
Subject: [orbit-dev] What to do about a bug in an Orbit provided bundle?
I'm reposting a question I previously asked on eclipse.tools.orbit
newsgroup but got no answer:
I seem to have found a bug in com.jcraft.jsch bundle included in Obrit.
The bug is not in the packaging, but in the original code.
I'm able to provide a patch for the bug, but the question is:
Where should I report the bug?
Should I report it to Eclipse Bugzilla as a bug in Orbit, or should I
report it to Jcraft, and then request Orbit to include the fixed
version, once available?
orbit-dev mailing list