Build namespace has build number which is newer than

Liferay Portlet deployment error with build number

When multiple developers working on portlet that uses servicebuilder will give below exception “Build namespace has build number which is newer than “. When developer commits file and that deployed on other developer machine then it will throw below exception. Error registering plugins for leave-portlet at at at Caused by: com.liferay.portal.OldServiceComponentException: Build namespace js has build number 38 which is newer than 21 at com.liferay.portal.service.impl.ServiceComponentLocalServiceImpl.initServiceComponent( at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed( at com.liferay.portal.spring.transaction.DefaultTransactionExecutor.execute(


  1. create file at the same locaiton of
  2. add build.number={higher-value or same value in exception)
  3. Deploy portlet again

Best Practice: To avoid these kind of errors, follow these

  1. Create file with below properies and commit that file to SVN  and do the database tables creation manually. Restrict file in SVN folder so that no body changes it only SVN admin can do
  2.  Please look into below tutorial about how to manage build number of liferay portlet in real time using Jenkins and SVN