MMBase

Split up mmbase jar to enforce clearer dependencies, and better reuseability.

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.9.2
  • Fix Version/s: 2.0.0
  • Component/s: Build
  • Description:
    Hide
    The rmmci client jar is a good example. All kind of stuff is included there, because you can't have the entire jar. It would be nicer if you simply could have the needed stuff in a separate jar. We propose 3 jars:

    - bridge
    - utils
    - core

    bridge depends on utils
    core implements bridge and may depend on utils
    utils depends on nothing.

    Applications may depend on all three, but preferrably only on bridge (or bridge and utils).
    Applications that depend only on utils are nice, are encouraged of course, but they are not mmbase applications.
    Show
    The rmmci client jar is a good example. All kind of stuff is included there, because you can't have the entire jar. It would be nicer if you simply could have the needed stuff in a separate jar. We propose 3 jars: - bridge - utils - core bridge depends on utils core implements bridge and may depend on utils utils depends on nothing. Applications may depend on all three, but preferrably only on bridge (or bridge and utils). Applications that depend only on utils are nice, are encouraged of course, but they are not mmbase applications.

Sub-Tasks

No sub-tasks match this view.

Activity

People

Dates

  • Created:
    2010-01-21 22:19
    Updated:
    2010-01-21 22:19