[jgit-dev] why are JGit unit tests in separate projects

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

[jgit-dev] why are JGit unit tests in separate projects

From: Matthias Sohn <matthias.sohn@xxxxxxxxx>
Date: Mon, 2 Sep 2013 16:00:32 +0200
Delivered-to: jgit-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jgit-dev>
List-help: <mailto:jgit-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jgit-dev>, <mailto:jgit-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jgit-dev>, <mailto:jgit-dev-request@eclipse.org?subject=unsubscribe>

I am wondering why JGit unit tests are living in their own separate Eclipse projects / Maven modules.

Signing would be easier if they would reside in tst folder of the project / module they test.

--

Matthias

Follow-Ups:
- Re: [jgit-dev] why are JGit unit tests in separate projects
  - From: Shawn Pearce

Prev by Date: Re: [jgit-dev] faster ref-updates where the update-type is known to be non-fast-forward
Next by Date: Re: [jgit-dev] why are JGit unit tests in separate projects
Previous by thread: [jgit-dev] Stray reference?
Next by thread: Re: [jgit-dev] why are JGit unit tests in separate projects
Index(es):
- Date
- Thread

Back to the top