Hi,

Had to build following modules in that order:

1. Axiom - /asf/webservices/commons/trunk/modules/axiom
2. Axis2 Core - /asf/axis/axis2/java/core/trunk (with -Dmaven.test.skip=true
IIRC)
3. Axis2 Transports - /asf/axis/axis2/java/transports/trunk (with
-Dmaven.test.skip=true)
4. Rampart - /asf/axis/axis2/java/rampart/trunk (with
-Dmaven.test.skip=true)
5. Synapse - /asf/synapse/trunk/java (with -Dmaven.test.skip=true)

Thanks.

- Asiri

On Wed, Nov 24, 2010 at 7:02 PM, Andreas Veithen
<[email protected]>wrote:

> That is caused by the presence of outdated snapshots in the WSO2
> repository (and an issue with metadata maintenance in the Apache Nexus
> repository). I've already requested several times that these snapshots
> be removed, but it seems that they are still there. I think that
> Synapse should follow the same policy that Axis2 is now following,
> which is to rely exclusively on Maven central and the Apache snapshot
> repository. This avoids issues with repositories that are not managed
> properly.
>
> A workaround is to build the snapshots locally, as indicated by Heshan.
>
> Andreas
>
> On Wed, Nov 24, 2010 at 13:22, Asiri Rathnayake <[email protected]> wrote:
> > Hi All,
> >
> > I tried to build synapse with a clean repository following instructions
> > given at [1]. However I keep getting this error:
> >
> > http://pastebin.com/raw.php?i=1nMPidjj
> >
> > And my build configuration is as follows:
> >
> > Apache Maven 2.2.1 (r801777; 2009-08-07 00:46:01+0530)
> > Java version: 1.5.0_16
> > Java home: /home/asiri/software/jdk1.5.0_16/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux" version: "2.6.33.6-147.fc13.i686.pae" arch: "i386"
> Family:
> > "unix"
> >
> > Do I need to build axis2 and related projects before attempting to build
> > synapse? Please clarify.
> >
> > Thanks.
> >
> > - Asiri
> >
> > [1] http://synapse.apache.org/building.html
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to