synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: [VOTE] Release Synapse 2.1.0
Date Mon, 26 Dec 2011 23:28:19 GMT

The Maven artifacts don't meet the requirements for publication to
Maven Central (see [1] and in particular the link to [2]). In
particular each artifact must be signed. Each artifact must also have
an MD5 checksum (that is not explicitly mentioned in [2] because the
maven-deploy-plugin normally takes care of this).

I'm not even sure if releasing artifacts using the old
m2-ibiblio-rsync-repository thing is still supported. What is sure is
that the only documented way is via Nexus.

There is also a regression with respect to the project branding
requirements. Apparently the change in r1051752 was never applied to
the trunk and is missing in 2.1.0. That seems to be a general problem
in the Synapse project, namely that there is no effective strategy to
manage the release branch and to ensure that all relevant changes are
in the trunk. In Axis2/Rampart/Sandesha2 we have eradicated that
problem by using a consistent (yet simple) strategy to manage the
release/maintenance branches.



On Mon, Dec 26, 2011 at 16:30, Kasun Indrasiri <> wrote:
> Hi Devs,
> This is the call for votes to release Apache Synapse-2.1.0.
> Please review the signed artifacts:
> The m2 repository is available at:
> Revamped site for this release is available at:
> SVN Info:
> revision is 1222784 on
> Here is my +1 to declaring the above dist as Synapse-2.1.0.
> Thanks,
> --
> Kasun Indrasiri
> Associate Technical Lead,
> WSO2 Inc. - "Lean . Enterprise . Middleware" -
> Blog :

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

View raw message