wrong branding.token is causing autoupdate to install in wrong targetcluster, since the update.xml has different cluster compared to installed DS.
authorchrislovsund@netbeans.org
Tue, 21 Aug 2012 14:17:29 +0200
changeset 2823daf5bd64192
parent 281 9778e0b60695
child 283 a11eb74f1c23
wrong branding.token is causing autoupdate to install in wrong targetcluster, since the update.xml has different cluster compared to installed DS.
EADS-2928 - CoS updating DS on Xen Desktop
nbproject/platform.properties
     1.1 --- a/nbproject/platform.properties	Mon Aug 20 09:29:11 2012 +0530
     1.2 +++ b/nbproject/platform.properties	Tue Aug 21 14:17:29 2012 +0200
     1.3 @@ -1,4 +1,4 @@
     1.4 -branding.token=plsql_support
     1.5 +branding.token=plsql-support
     1.6  nbjdk.active=JDK_1.6
     1.7  nbplatform.default.netbeans.dest.dir=/hudson/workdir/jobs/plsql-support/workspace/ide/netbeans
     1.8  nbplatform.default.harness.dir=${nbplatform.default.netbeans.dest.dir}/harness