Carrot2

Add package version to all plugins that wrap third-party libraries

Details

  • Description:

    As a result of CARROT2-358: I suggest to add package versions to all plugins that wrap third-party libraries, to avoid this kind of problems in the future.

Issue Links

Activity

Hide
Dawid Weiss added a comment - 20/Sep/08 12:47 PM

Consolidated plugin/ project classpaths. Notes:

1) All the projects that are Eclipse plugins:

  • MUST NOT have Java project dependencies,
  • MUST declare dependencies via the plugin descriptor,
  • MUST NOT re-export dependencies via "Order and Export" tab,
    use the plugin descriptor instead.
  • SHOULD NOT depend on any extra plugins other than:
  • org.carrot2.core
  • org.carrot2.util.common
    These plugins re-export many standard libraries and there
    is usually no need to bother with importing anything else.
  • SHOULD declare plugin version number consistent with the
    Carrot2 release (3.0.0, for example).

2) All the projects that are regular Java projects (Webapp, DCS, examples):

  • MUST NOT declare dependencies on multiple Carrot2 plugins. Instead,
    add a dependency on:
  • carrot2-component-suites
    This project depends on nearly all algorithms and sources, so no extra
    classpath should be required.

3) All the library plugin wrappers:

  • MUST declare their corresponding version number consistent with their
    library release number.

Exception:
Apache commons and FEST libraries are bundled together in larger packages
for the use in the Carrot2 project. Their version number follows Carrot2
platform versioning.

Show
Dawid Weiss added a comment - 20/Sep/08 12:47 PM Consolidated plugin/ project classpaths. Notes: 1) All the projects that are Eclipse plugins:
  • MUST NOT have Java project dependencies,
  • MUST declare dependencies via the plugin descriptor,
  • MUST NOT re-export dependencies via "Order and Export" tab, use the plugin descriptor instead.
  • SHOULD NOT depend on any extra plugins other than:
  • org.carrot2.core
  • org.carrot2.util.common These plugins re-export many standard libraries and there is usually no need to bother with importing anything else.
  • SHOULD declare plugin version number consistent with the Carrot2 release (3.0.0, for example).
2) All the projects that are regular Java projects (Webapp, DCS, examples):
  • MUST NOT declare dependencies on multiple Carrot2 plugins. Instead, add a dependency on:
  • carrot2-component-suites This project depends on nearly all algorithms and sources, so no extra classpath should be required.
3) All the library plugin wrappers:
  • MUST declare their corresponding version number consistent with their library release number.
Exception: Apache commons and FEST libraries are bundled together in larger packages for the use in the Carrot2 project. Their version number follows Carrot2 platform versioning.
Hide
Dawid Weiss added a comment - 20/Sep/08 12:51 PM

Fixed in trunk.

Show
Dawid Weiss added a comment - 20/Sep/08 12:51 PM Fixed in trunk.

People

Dates

  • Created:
    09/Aug/08 10:29 AM
    Updated:
    20/Sep/08 12:51 PM
    Resolved:
    20/Sep/08 12:51 PM