Looks like it was due to some changes done at the platform pom. In order to
fix this, I had to modify the antrun plugin of the affected integration
tests.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.1</version>
<executions>
<execution>
<id>create-temp-dir</id>
<phase>process-test-resources</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<tasks>
<property name="tempdir"
value="target/carbontmp/wso2esb-${pom.version}"/>
<mkdir dir="${tempdir}"/>
</tasks>
Fixed.
On Tue, Apr 5, 2011 at 11:50 PM, Amila Maha Arachchi <[email protected]>wrote:
> Triggered a new build starting from product level (not necessary to build
> other sections coz they were built in the previous cycle). Commented out
> integration tests from ESB.
>
> On Tue, Apr 5, 2011 at 11:02 PM, Afkham Azeez <[email protected]> wrote:
>
>> Please comment out esb integration module and restart the build.
>> On Apr 5, 2011 10:43 PM, "Amila Maha Arachchi" <[email protected]> wrote:
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
--
Kasun Indrasiri
Senior Software Engineer
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 71 536 4128
Blog : http://kasunpanorama.blogspot.com/
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
