synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <>
Subject [jira] [Resolved] (SYNAPSE-396) Consider reducing requisite dependencies of Synapse Core
Date Mon, 26 Aug 2013 02:16:52 GMT


Hiranya Jayathilaka resolved SYNAPSE-396.

       Resolution: Fixed
    Fix Version/s: 2.1

I believe we can resolve this now. We refactored all the dependencies for the 2.1 release.
We now declare all dependencies in the root POM under the dependencyManagement section (so
they are not automatically inherited by the child modules). Individual modules use the bare
minimum of dependencies in each of them. Spring and log4j dependencies have been removed from
Core. The only transport that Core depends on is the nhttp/pass-through transport. 
> Consider reducing requisite dependencies of Synapse Core
> --------------------------------------------------------
>                 Key: SYNAPSE-396
>                 URL:
>             Project: Synapse
>          Issue Type: Wish
>          Components: Core
>    Affects Versions: 2.0
>            Reporter: Oleg Kalnichevski
>            Assignee: Andreas Veithen
>             Fix For: 2.1
> Folks
> I understand that the greatest majority of Synapse users use it as a standalone application
and are unlikely  to care much about external dependencies of individual modules. However,
as the Synapse user base grows it will become more diverse as well. There will be users who
may want to (or have to) use parts of Synapse embedded into a larger runtime either as OSGi
bundles, GBeans or a set of plain old jars. They are also likely to concerned about total
number of external dependencies in order to minimize possibility of versioning conflicts.

> The present situation with external dependencies can only be described as depressing.
Synapse Core is currently dependent either directly or transitively on several dozens of libraries,
which makes it very difficult to embed. 
> More details to follow

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message