I vote +1 for option 3. We should also compile the API jar (woden-api.jar ?) separately from the implementation classes to ensure the interface classes have no compile time dependencies on the implementation. At least that's a goal anyway.

Jeremy

On 9/16/05, Lawrence Mandel <[EMAIL PROTECTED]> wrote:

Kihup,

I think there are a few options here.

1. Package the Woden API and Woden implementation in two jars (as you suggested).
2. Package the Woden API and Woden implementation in one jar. This probably is not a good idea as the idea is that other implementations of the Woden API will be created.
3. Package the Woden API as one jar and the Woden API + implementation as a second jar. This allows those that require the Woden API to just download the API while those that want the implementation can download one jar with everything they need.

Comments?

Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920
[EMAIL PROTECTED]


Reply via email to