@ Pradeep: I just have look in github[1] and featue poms [3], etc.. version are correct in there. Need to check svn up with external works fine in here. I will join you with this task to complete this branch build regard to jaggery
@Nuwan: I think we have to do that trunk ( 0.9.0-07262013) shift to branch regard jaggery. That changes need to be in new branch and that version regard to branch as below. will reduce those lot of build fails. It is better to have much better version numbers? (idea for version numbers) [image: Inline image 1] [2] will be the version that to be used in wso2 svn branch, @ Pulasthi: yap, here is thread/details regard the build fails in trunk. [Features-Jaggery]Build Failure in trunk [1] https://github.com/wso2/jaggery/tree/0.9.0-07262013 [3] https://github.com/wso2/jaggery/blob/0.9.0-07262013/features/pom.xml
<<aaa.png>>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
