| I would not expect non-test projects like eclipselink.dbws,
eclipselink.core and eclipselink.moxy to depend on JUnit
4.  I'd suggest separating test infrastructure from runtime
infrastructure into different projects so that we keep the runtime
dependencies minimal. 
 Shaun
 
 Mike Norman wrote:
 As part
of the work to merge DBWS code into EclipseLink, some IPzilla
CQ's (specificallyhttps://dev.eclipse.org/ipzilla/show_bug.cgi?id=1768
and 1755) were create to enable the use
 of the pb4 custom JUnit4 Runner
and Ant task.  Not only are there DBWS tests that require
 this capability, but also new core feature tests for supporting
non-JDBC arguments to StoredProcedures.
 
 This is the first time in EclipseLink that multiple components required
some utility or library. To deal
 with this, I propose a new 'common' project - the directory structure
would be as follows:
 
 ${eclipselink-svn-directory-root}
 +---branches
 \---trunk
 |   about.txt
 |   ...
 |
 (new)  +---common
 -    |   \---eclipselink.common
 -    |   |   |   .classpath
 -    |   |   |   .project
 -    |   |   |
 -    |   |   +---lib
 -    |   |   |       ant.jar                          (CQ 1768)
 -    |   |   |       junit4-ext-pb4.jar               (CQ 1755)
 -    |   |   |       ${other_commonly_used}.jar       (future CQ)
 -    |   |   \---pb4
 (new)  |   |       \--- ...
 (old)  +---dbws
 |   +---eclipselink.dbws
 |   |   |   .classpath
 |   |   |   .project
 |   |   |
 |   |   \---src
 |   |       \---org
 |   |           \---eclipse
 |   |               \---persistence
 |   |                   +---dbws
 |   |                   |       ...
 |    ...
 (old)  +---foundation
 |   +---eclipselink.core
 |   |   |   .classpath
 |   |   |   .project
 |   |   |
 |   |   \---src
 |   |       \--- ...
 
 
 From a developer's view inside of an Eclipse IDE environment, the main
projects (such as eclipselink.dbws,
  eclipselink.core and
 eclipselink.moxy) depend apriori
upon eclipselink.common. The
other change will be relying upon version 4 of the JUnit library - this
 should not affect any code as the old JUnit 3.8.x APIs are preserved in
JUnit4.
 
 
 
 --   Mike Norman | Principal Software Designer | 613.288.4638 Oracle Server Technologies | TopLink Product
 45 O'Connor Street, Suite 400 | Ottawa, ON K1P 1A4 | (fax) 613.238.2818
 
 
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
 
 --   Shaun Smith | Principal Product Manager | +1.905.502.3094 Oracle TopLink
 110 Matheson Boulevard West, Suite 100
 Mississauga, Ontario, Canada L5R 3P4
 
 |