Hi all,
I'm trying to start this year 2013 by fulfilling some tasks I should
have done a few months ago.
So you can now find on this wiki page some tips about code quality
analysis and Sonar for Eclipse projects: http://wiki.eclipse.org/Sonar
It's currently quite simple, so if you think it
Depending on what the developer intends to do with the source, I can see it
as a benefit if CVS Ecliipse-SourceReferences does not work. If the
developer creates and contributes a patch using CVS, it will be rather
difficult to merge it.
- Konstantin
From:
Hi Folks,
Until recently, (ECF) has been signing our plugins by 'pushing' our
plugins to eclipse.org (built on our own builder machine...which is
*not* running at eclipse.org). Apparently this is not the appropriate
way now...rather what Denis indicated was appropriate was to have an
The original discussions of the CVS shutdown did involve leaving a read
only service intact [1]. Not all code from past releases was migrated, so
anyone wanting to find the source for an old release, or do long term
maintenance on old releases, needs access to the CVS data. At the very
least
Denis Roy wrote on 01/03/2013 02:53:48 PM:
Actually, the bug doesn't involve leaving a read only service intact
at all. The repos are still in their locations, read-only, but
pserver has been shut down.
Yes it depends on your interpretation of read only. If you interpret
this to mean
