Foren
Build namespace UNIVERSITY has build number 15 which is newer than 10
mukesh kumar, geändert vor 11 Jahren.
Build namespace UNIVERSITY has build number 15 which is newer than 10
Junior Member Beiträge: 57 Beitrittsdatum: 13.03.12 Neueste Beiträge
Hi All
How to resolve the given issue.
Build namespace UNIVERSITY has build number 15 which is newer than 10.
Regards
Mukesh Kumar
How to resolve the given issue.
Build namespace UNIVERSITY has build number 15 which is newer than 10.
Regards
Mukesh Kumar
Priyanka Dhingra, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Liferay Master Beiträge: 501 Beitrittsdatum: 20.12.11 Neueste Beiträge
go to your service.properties file
change Build number to 15
change Build number to 15
Parth Kadia, geändert vor 4 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
New Member Beiträge: 2 Beitrittsdatum: 30.12.19 Neueste BeiträgeIt's works. Thank you.
Jignesh Vachhani, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Liferay Master Beiträge: 803 Beitrittsdatum: 10.03.08 Neueste Beiträge
You can update build number from release_ table for that portlet of liferay which has buildNumber column.
Hope this will resolve your query.
Hope this will resolve your query.
mukesh kumar, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Junior Member Beiträge: 57 Beitrittsdatum: 13.03.12 Neueste Beiträge
thanks jignesh and Priyanka .
David H Nebinger, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Liferay Legend Beiträge: 14914 Beitrittsdatum: 02.09.06 Neueste Beiträge
Both of these answers are most likely wrong.
When you build services, the build number is incremented. This is to prevent users of the service jar to use a 'stale' or out of date service jar when calling your service.
How are you sharing your service jar w/ other plugins?
When you build services, the build number is incremented. This is to prevent users of the service jar to use a 'stale' or out of date service jar when calling your service.
How are you sharing your service jar w/ other plugins?
Jignesh Vachhani, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Liferay Master Beiträge: 803 Beitrittsdatum: 10.03.08 Neueste Beiträge
Yes David
You are right but this is not the answer of the query which he asked for.
Many times literally or literally we are facing this problem and we solved this way only.
If you have any other solution please share it here.
You are right but this is not the answer of the query which he asked for.
Many times literally or literally we are facing this problem and we solved this way only.
If you have any other solution please share it here.
David H Nebinger, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Liferay Legend Beiträge: 14914 Beitrittsdatum: 02.09.06 Neueste Beiträge
Sure, I typically use the service-ext.properties to change my build number to 1. That way the management of the deployment of the service jar is all my responsibility, and I'm fine with that. I'm usually only adding new entities/methods, so existing entities/methods don't change and the build version for me is a roadblock, not a tool.
To do this for yourself, in the same directory as your service.properties file, create a service-ext.properties file and just add a line "build.number=1". This overrides whatever value is in service.properties, so you're effectively disabling the build.number handling.
Again, this means you're taking over responsibility for managing the service jar deployment. If not done correctly, you'll get weird errors at runtime that are harder to diagnose than the simple "build number is newer" error check that Liferay normally does (things like class not found or method missing exceptions).
To do this for yourself, in the same directory as your service.properties file, create a service-ext.properties file and just add a line "build.number=1". This overrides whatever value is in service.properties, so you're effectively disabling the build.number handling.
Again, this means you're taking over responsibility for managing the service jar deployment. If not done correctly, you'll get weird errors at runtime that are harder to diagnose than the simple "build number is newer" error check that Liferay normally does (things like class not found or method missing exceptions).
Priyanka Dhingra, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Liferay Master Beiträge: 501 Beitrittsdatum: 20.12.11 Neueste Beiträge
Thanks David....
I have 2 doubts...
what could be the possibilities of errors??What can go incorrect?
and build.number=1...Here "1" is some magic number??? or it can be any random number i want to pick up and use??
I have 2 doubts...
If not done correctly, you'll get weird errors at runtime that are harder to diagnose than the simple "build number is newer" error check that Liferay normally does (things like class not found or method missing exceptions).
what could be the possibilities of errors??What can go incorrect?
and build.number=1...Here "1" is some magic number??? or it can be any random number i want to pick up and use??
GERALD ROMERO, geändert vor 10 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
New Member Beiträge: 7 Beitrittsdatum: 12.10.12 Neueste Beiträge
Took me a while to figure this out myself. This is tracked in the servicecomponent table. Not the release_ table.
Hope that helps someone else.
Hope that helps someone else.
clint barbosa, geändert vor 10 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
New Member Beiträge: 7 Beitrittsdatum: 23.08.12 Neueste BeiträgeGerald Romero:
Took me a while to figure this out myself. This is tracked in the servicecomponent table. Not the release_ table.
Hope that helps someone else.
Thanks for this !
Robin Nagpal, geändert vor 9 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Junior Member Beiträge: 44 Beitrittsdatum: 18.11.14 Neueste Beiträge
You should first see what exactly changed and accordingly change your build number. If you are adding,deleting new methods then you can use the previous build number if you are not distributing your service jars to client.
But if you are adding/modifying column/field of an entity you might want to increment the build number as Liferay will execute the sql statements only if there is a increase in the build number
But if you are adding/modifying column/field of an entity you might want to increment the build number as Liferay will execute the sql statements only if there is a increase in the build number
Priyanka Dhingra, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Liferay Master Beiträge: 501 Beitrittsdatum: 20.12.11 Neueste Beiträge
@Mukesh Kumar....Please check the thread you are posting in
mukesh kumar, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Junior Member Beiträge: 57 Beitrittsdatum: 13.03.12 Neueste Beiträge
My thread is correct . While deploying the portlet i was getting this error.
Priyanka Dhingra, geändert vor 11 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
Liferay Master Beiträge: 501 Beitrittsdatum: 20.12.11 Neueste Beiträge
Hi Mukesh
I think this should be the correct thread
http://www.liferay.com/community/forums/-/message_boards/category/239390
and as you want in, for deploying the portlet only
http://www.liferay.com/community/forums/-/message_boards/category/239393
I think this should be the correct thread
http://www.liferay.com/community/forums/-/message_boards/category/239390
and as you want in, for deploying the portlet only
http://www.liferay.com/community/forums/-/message_boards/category/239393
Enrico Polanski, geändert vor 5 Jahren.
RE: Build namespace UNIVERSITY has build number 15 which is newer than 10
New Member Beiträge: 2 Beitrittsdatum: 20.11.18 Neueste Beiträge
The problem might be also the auto deploy.
Shutting down and restarting the server can fix this issue.
Shutting down and restarting the server can fix this issue.