掲示板
Build namespace <namespace> has build number 73 which is newer than 4
8年前 に kiran kumar によって更新されました。
Build namespace <namespace> has build number 73 which is newer than 4
Regular Member 投稿: 175 参加年月日: 14/10/15 最新の投稿
how to resolve this issue.
Pls help me.
Pls help me.
8年前 に Jan Geißler によって更新されました。
RE: Build namespace <namespace> has build number 73 which is newer than 4
Liferay Master 投稿: 735 参加年月日: 11/07/05 最新の投稿
Take a look at your service.properties in docroot/WEB-INF/src.
change this entry
build.number=4
to
build.number=74
change this entry
build.number=4
to
build.number=74
8年前 に kiran kumar によって更新されました。
RE: Build namespace <namespace> has build number 73 which is newer than 4
Regular Member 投稿: 175 参加年月日: 14/10/15 最新の投稿
Thank you jan , now it's working
8年前 に David H Nebinger によって更新されました。
RE: Build namespace <namespace> has build number 73 which is newer than 4
Liferay Legend 投稿: 14919 参加年月日: 06/09/02 最新の投稿
When you build services, Liferay increments a counter in the service.properties file. This number is in both the service jar and in the service implementation.
It is a check between code with a service jar to ensure it is the same version as the one implemented in the service implementation.
When you get this message it means you are now out of sync - you have a newer service implementation than what the service jar you're using is or you have a newer service jar than the deployed implementation.
When working in a team setting, you have to manage the communication of the build number to all participants so the numbers remain equal. Often it is best practice to have one dev build services to keep this kind of thing from happening.
It is a check between code with a service jar to ensure it is the same version as the one implemented in the service implementation.
When you get this message it means you are now out of sync - you have a newer service implementation than what the service jar you're using is or you have a newer service jar than the deployed implementation.
When working in a team setting, you have to manage the communication of the build number to all participants so the numbers remain equal. Often it is best practice to have one dev build services to keep this kind of thing from happening.
8年前 に Devang Patel によって更新されました。
RE: Build namespace <namespace> has build number 73 which is newer than 4
Regular Member 投稿: 247 参加年月日: 15/01/19 最新の投稿Jan Geißler:
Take a look at your service.properties in docroot/WEB-INF/src.
change this entry
build.number=4
to
build.number=74
Thanks Jan Geißler
Regards,
Devang patel