The new modules exist to wrapper svnClientAdapter as an Eclipse
plugin. There is zero code duplication and maintenance. The new
modules only contain the small number of files necessary to expose the
code as an Eclipse plugin, the code itself is pulled in via
svn:externals property so it only exists in one location within the
repository. If you browse the repository directly you can see there
is not much in those modules, it is only when you check them out that
the SVN client materializes the svn:externals into files on disk so
that it looks like duplication.
On Thu, Jan 20, 2011 at 7:28 AM, Dimitrios Athanasiou
> I am a student at TU Delft, Netherlands. I am currently working on my thesis
> project and I am performing an empirical study regarding software quality.
> I was looking into the source of subclipse and its evolution. At some point
> (I was checking the difference between release 1.2.1 and 1.4.0 ) , the
> they co-exist increasing the volume and the duplication of the system.
> Of course, I understand these are probably imported libraries. However, they
> are imported as source code.
> My question is whether these library source files were imported so that they
> can be modified? In other words, do you put maintenance effort on that
> source code or is it just imported libraries?
> I would appreciate it if you would answer me. Thank you in advance for your
> time and consideration.
> Kind regards,
> Dimitrios Athanasiou
> MSc Student @ TU Delft
> Intern Researcher @ SIG (Software Improvement Group)
> Software Improvement Group
> Did you miss our e-newsletter of January? Please subscribe via: www.sig.eu/nl/nieuwsbrief/
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2011-01-20 14:16:31 CET