Hi
Found it. It's lurking on the left of
http://eclipse.org/projects/tools/ip_contribution_review.php,
so if you ignore the rubbish from
http://eclipse.org/projects/tools/ip_contribution_review.php
you get the good old review.
Regards
Ed
I opened a ticket some time ago, proposing to have the link on the project
page: https://bugs.eclipse.org/bugs/show_bug.cgi?id=400551
I guess it will be then easy to find.
Krum
From: cross-project-issues-dev-boun...@eclipse.org
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf
Hi David,
From the b3 aggregator log, it appears that Code Recommenders is the one
pulling in version 1.6.4.
Is that on purpose? That is, do you purposely constrain/include that
older version? Any chance to move up to the latest?
Sure. Will look into this straight away.
Andreas
--
Hi
Our Scout RT Gerrit Job on the Hudson Sandbox fails with an OutOfMemoryError
(https://hudson.eclipse.org/sandbox/job/eclipse.scout.rt/160/console):
#
# A fatal error has been detected by the Java Runtime Environment:
#
# java.lang.OutOfMemoryError: requested 2147483656 bytes for Chunk::new.
Hi,
From the b3 aggregator log, it appears that Code Recommenders is the one
pulling in version 1.6.4.
Is that on purpose? That is, do you purposely constrain/include that
older version? Any chance to move up to the latest?
Sure. Will look into this straight away.
made the move to
Thanks for your quick cooperation ... I bet you will be happier with the
newest version anyway ... at least I hope!
Thanks again,
From: Andreas Sewe andreas.s...@codetrails.com
To: cross-project-issues-dev@eclipse.org,
Cc: Marcel Bruch marcel.br...@codetrails.com
Date:
Hi David,
Thanks for your quick cooperation ... I bet you will be happier with the
newest version anyway ... at least I hope!
I bet we won't notice the difference: log.error(..) is still the same as
always.
Anyway, can you just double-check [1] that the other, SLF4J related
plugins like
The contribution review tool is intended to assist a project in
identifying IP contributions that come through Bugzilla.
If your project is using Git and is pushing commits that are
correctly annotated with author information, then this tool will be
of no interest
Looks right to me ... but ... to be honest, I know a whole lot less about
it than just about anyone else :)
(e.g not sure you need all three fragments ... but, no idea how it is
normally shipped/configured).
So, I've passed on your question to the original bug, and added you to CC
in case
Hi
Thanks; that's clear but is hardly sensible. I have a handful of PB
CQs to raise and I suspect many other projects must do too.
Since we are strongly encouarged to track the latest Orbit version,
shouldn't there be an auto-PB CQ for any project that has a PB
Also using Import-Package allows for provider substitution. You don't
really know who the provider of the package dependency is by looking at a
bundle manifest in isolation.
Tom
From: Wayne Beaton wa...@eclipse.org
To: cross-project-issues-dev@eclipse.org,
Date: 05/17/2013 02:06 PM
11 matches
Mail list logo
