[svn] 785: test to see if the build is still broken.

Revision: 785
Author: [email protected]
Date: 2008-03-12 06:07:12 -0700 (Wed, 12 Mar 2008)
Log Message:
test to see if the build is still broken.
Modified Paths:
flex/sdk/branches/3.0.x/kick-build.txt

Hm. Well, I promise that when I used to catch a fish on that Flick Fishing game, that there would be a vibration. I don't know how the device or the game made it happen, but I don't think I would mistake a sound for a movement of/in the device itself. I just played the game with the sound up, and there was still no wiggle. I suppose in the end, its really not that important. I know that there was a "wiggle" in that game before the latest Apple software update, that there isn't one now, so I'll just chalk it up to an "improvement."

Similar Messages

[svn] 759: 30x: The build has been broken for three days? Kicking before investigating.

Revision: 759
Author: [email protected]
Date: 2008-03-07 11:01:32 -0800 (Fri, 07 Mar 2008)
Log Message:
30x: The build has been broken for three days? Kicking before investigating.
Modified Paths:
flex/sdk/branches/3.0.x/kick-build.txt

You might need to stop the restore process and try restoring your backup again. To do this, go to Settings>iCloud>Storage & Backup and tap Stop Restoring... at the bottom. Then restore your backup again as explained here: https://support.apple.com/kb/ph12521. When you're not using it, be sure your phone is connected to wifi and your charger while it is restoring the backup.

How to test to see if the cursor is on the last row in a jTable?

I like to know how to test the cursor position in jTable.

From the many topics you post here, I can see that you are thinking in the wrong terms.
Although it's possible, you should not test if the current row is the last one in a JTable. Instead you should test whether or not the current row is the last one in a VO instance, to which any particular JTable's model is bound.
So, please read the API documentation for oracle.jbo.ViewObject and oracle.jbo.server.ViewObjectImpl.

[svn:fx-trunk] 11311: hook up the building of the playerglobal_rb fat swcs.

Revision: 11311
Author:   [email protected]
Date:     2009-10-30 10:00:39 -0700 (Fri, 30 Oct 2009)
Log Message:
hook up the building of the playerglobal_rb fat swcs. Currently this will only produce en_US based docs for all languages we are building for. Once we get translated dita files we will start using them.
QE notes: all langs will be in English
Doc notes:
Bugs: no
Reviewer: Pete
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/build.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/build.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/__Global__.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/air.net.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/air.update.events.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/air.update.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.accessibility.xm l
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.data.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.desktop.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.display.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.errors.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.events.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.external.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.filesystem.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.filters.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.geom.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.html.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.media.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.net.drm.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.net.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.printing.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.profiler.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.sampler.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.security.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.system.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.text.engine.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.text.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.ui.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.utils.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/flash.xml.xml
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/packages.dita
Added Paths:
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/en_US/docs/authoring.xml

Thats good news.

[svn:bz-3.x] 15200: Update the build.xml to include contents under / resources/clustering/2.9.0

Revision: 15200
Revision: 15200
Author:   [email protected]
Date:     2010-04-02 07:46:55 -0700 (Fri, 02 Apr 2010)
Log Message:
Update the build.xml to include contents under /resources/clustering/2.9.0
Modified Paths:
    blazeds/branches/3.x/build.xml

Revision: 15200
Revision: 15200
Author:   [email protected]
Date:     2010-04-02 07:46:55 -0700 (Fri, 02 Apr 2010)
Log Message:
Update the build.xml to include contents under /resources/clustering/2.9.0
Modified Paths:
    blazeds/branches/3.x/build.xml

Testing to see if a session has expired

Hello all,
I am trying to test to see if the user's session has expired by inserting the following code at the top of the page:
HttpSession sess = request.getSession();
if(sess.getAttribute("userId")=="null"){response.sendRedirect("logon.jsp");}The problem is that when the session expires and I refresh or go to the page with the above code, I get a null pointer exception and, of course , it wont redirect.
Am I doing the comparison improperly?
TIA!!

I have changed my code somewhat but I still cant get the page to redirect.This is the first 20 lines of code:
<%@page import="java.util.*,
          java.net.*,
          java.text.*,
          java.util.zip.*,
          java.io.*,
                javax.servlet.http.*,sensorPac.methodClass"
%>
<%
System.out.println("SESSION="+session.getAttribute("userId"));
if(session.getAttribute("userId") == null){response.sendRedirect("logon.jsp");}%>When I look at the tomcat console window I get the following:
When I first hit the page with a valid session I get:
SESSION = fortegr
When I refresh or revisit the page after a minute (session.setMaxInactiveInterval(1);)
I get:
SESSION=null
Once again it will not redirect.
Any ideas?
TIA!

How to test to see if inputted swf exists?

Hi
I have an input field that asks for a .swf name - you enter the name, hit SUBMIT, and Flash loads that .swf onto the screen.
I've coded for an error to appear if the user doesn't input anything, but how to I test to see if the swf exists, and if not, return an error?
I have a function called onSwfLoad that runs when the swf loader finishes, triggered by an Event.COMPLETE in the swf loader event listener - is there something I can put in an if statement there to test if the swf loader found a file?
Thnaks
Shaun

the loader class doesn't have any events. you use the contentloaderinfo property of your loader to get a loaderinfo reference and that has the events you need:
loadSwfBut.addEventListener("mouseDown", sendData)
function sendData(evt:Event) {
    if(loadSwf.text !=""){
var Xpos:Number = 0;
var Ypos:Number = 100;
var swf:MovieClip;
var loader:Loader = new Loader();
var defaultSWF:URLRequest = new URLRequest(loadSwf.text);
loader.load(defaultSWF);
loader.x = Xpos;
loader.y = Ypos;
addChild(loader);
        loader.contentLoaderInfo.addEventListener(Event.COMPLETE, dataOnLoad);
        loader.contentLoaderInfo.addEventListener(IOErrorEvent.IO_ERROR, errorLoading);
    } else status_txt.text = "All fields are mandatory"
function errorLoading(event:IOErrorEvent):void {
    status_txt.text = "nup"
function dataOnLoad(evt:Event){
    status_txt.text = "yep";
stop();

Program won't build if a broken vi is included in a diagram disable structure

I develop code that can run on both PXI and Compact RIO devices.
To allow for the different DAq methods I have a target specific child object that I tried putting in a conditional disable diagram.
I found that even if it was disable, the build would still fail.
When you build rio code on a pxi target, you et problems But I didn't expect them if the class was diagram disabled
In fact it won't build if it is in the project at all.
Posted as a bitter lesson for others to avoid.
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

I just made a test built with a diagram disable structure containing an odd subVI in the disabled case and cannot reproduce this error. Are you sure that the relevant case is set to disabled?
Can you attach a simple VI that shows the problem?
LabVIEW Champion . Do more with less code and in less time .

(261205913) Q SYNCH-14 Is the client behavior still synchronous for buffered methods?

Q<SYNCH-14> Is the client behavior still synchronous for buffered methods?
Q<SYNCH-14> For buffered methods the client invocation is essentially asynchronous
since the return type for the method is void. Quote from BEA Workshop documentation:
If you add a message buffer to a method of your web service, incoming messages
(invocations of the method) are buffered on the local machine. The method invocation
returns to the client immediately. This prevents the client from waiting until
your web service processes the request. Note that since the buffering occurs on
your end of the wire, the client still must wait for the network roundtrip even
though it will return a void result. But the client does not have to wait for
your service to process the message

Futher information about the possibility of callback:
It may be possible for a synchronous only web service (i.e. MS .net) to even paticipant
in the callback functionality of asynchronous web services. If the client implements
the appropriate methods for the callback but listens for them on a different port
or binding than the SOAP request, then web service may be able to build a response
if the client's "callback URL" is submitted as the beginning part of a conversation.
Watch the BEA developer forum (http://dev2dev.bea.com) for more information about
this approach and other tips and techniques for building web services.
"Adam FitzGerald" <[email protected]> wrote:
>
Q<SYNCH-03> I heard that MS .net only implements synchrnonus method? If
this is true.
Does it means my async methods will only work with J2EE clients?
A<SYNCH-03> I do not know the limitations of .net but let me point out that
is very
difficult to provide asynchronous web service method invocation (this is
different
from an asynchronous web service). HTTP as a general communication protocol
is based
on a request and response paradigm so your client libraries will mostly
likely be
expecting a response even if it is empty (check the asynchronous example
from today
to see that the start method still returns an empty response). You must
distinguish
this from the notion of an asynchronous web service which is a business
operation
that occurs on the server whose return value/result is not directly associated
with
building response to the client. An asynchronous web service can (and generally
will)
be started and stopped with web service operations that are invoked synchronously.
Thus MS .net clients can still be client to WLS hosted web services.

[svn] 2153: build.xml: Adding a description to the 'asc-tests' task to match the other *-tests tasks.

Revision: 2153
Author: [email protected]
Date: 2008-06-19 18:34:42 -0700 (Thu, 19 Jun 2008)
Log Message:
build.xml: Adding a description to the 'asc-tests' task to match the other *-tests tasks.
Modified Paths:
flex/sdk/trunk/build.xml

Thats good news.

[svn:osmf:] 11045: Increasing timer interval in attempt to fix unit test on the build server.

Revision: 11045
Author:   [email protected]
Date:     2009-10-21 02:32:45 -0700 (Wed, 21 Oct 2009)
Log Message:
Increasing timer interval in attempt to fix unit test on the build server.
Modified Paths:
    osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/composition/TestParallelViewableTrai t.as

In general theory, one now has the Edit button for their posts, until someone/anyone Replies to it. I've had Edit available for weeks, as opposed to the old forum's ~ 30 mins.
That, however, is in theory. I've posted, and immediately seen something that needed editing, only to find NO Replies, yet the Edit button is no longer available, only seconds later. Still, in that same thread, I'd have the Edit button from older posts, to which there had also been no Replies even after several days/weeks. Found one that had to be over a month old, and Edit was still there.
Do not know the why/how of this behavior. At first, I thought that maybe there WAS a Reply, that "ate" my Edit button, but had not Refreshed on my screen. Refresh still showed no Replies, just no Edit either. In those cases, I just Reply and mention the [Edit].
Also, it seems that the buttons get very scrambled at times, and Refresh does not always clear that up. I end up clicking where I "think" the right button should be and hope for the best. Seems that when the buttons do bunch up they can appear at random around the page, often three atop one another, and maybe one way the heck out in left-field.
While I'm on a role, it would be nice to be able to switch between Flattened and Threaded Views on the fly. Each has a use, and having to go to Options and then come back down to the thread is a very slow process. Jive is probably incapable of this, but I can dream.
Hunt

[svn:bz-4.x] 16256: Do some build cleanup on the BlazeDS/4.x branch.

Revision: 16256
Revision: 16256
Author:   [email protected]
Date:     2010-05-20 10:50:31 -0700 (Thu, 20 May 2010)
Log Message:
Do some build cleanup on the BlazeDS/4.x branch. I had just intended to update the build scripts to exclude xalan.jar from the WEB-INF/lib directory of a bunch of the webapps but while I was doing this I found a number of other problems that I attempted to fix. Here is a breakdown of what I changed.
Update build scripts to not add xalan.jar to the WEB-INF/lib directory of those webapps that were including it. As far as I can tell we don't need to/shouldn't be shipping xalan.jar in the WEB-INF/lib directory of any of the webapps. I also updated the build scripts to not add fxgutils.jar to the WEB-INF/lib directory of those webapps that were including it. I also can't see any reason for us to be shipping fxgutils.jar with any of the webapps. This jar file is part of the Flex SDK and we're no longer shipping BlazeDS with the Flex SDK.
The clean target in the main build.xml file was not calling clean on the ds-console webapp. It was also calling clean on the qa-regress webapp twice and never calling clean on qa-manual which was probably a typo. Fixed the build so clean now gets called for ds-console and qa-regress.
The samples webapp had hsqldb.jar checked into its WEB-INF/lib directory in svn. The build script for the samples webapp was also copying hsqldb.jar from the <blazesd-home>/lib/hsqldb directory. I cleaned this up by deleting hsqldb.jar from the samples/WEB-INF/lib directory in svn so now we will just get the jar from the <blazeds-home/lib/hsqldb directory.
After removing hsqldb.jar from the samples/WEB-INF/lib directory none of the webapps in BlazeDS have anything checked into their WEB-INF/lib directories in svn. Most of the BlazeDS webapps were using properties from the top level build.properties file to determine which jars to delete from the WEB-INF/lib directory. This is problematic because unless we do a good job of keeping these lists of jars up to date files wind up not being cleaned from the WEB-INF/lib directory and we could potentially ship files that are no longer part of the build. I fixed this issue by updating the build scripts for all of the webapps to delete everything from the WEB-INF/lib directory as part of the clean target.
Checkintests: passed
Modified Paths:
    blazeds/branches/4.x/apps/blazeds/build.xml
    blazeds/branches/4.x/apps/blazeds-spring/build.xml
    blazeds/branches/4.x/apps/ds-console/build.xml
    blazeds/branches/4.x/apps/samples/build.xml
    blazeds/branches/4.x/apps/samples-spring/build.xml
    blazeds/branches/4.x/apps/team/build.xml
    blazeds/branches/4.x/build.properties
    blazeds/branches/4.x/build.xml
    blazeds/branches/4.x/qa/apps/qa-manual/build.xml
Removed Paths:
    blazeds/branches/4.x/apps/samples/WEB-INF/lib/

Found solution after many hours of search and test:
I have Launch2Net Premium 2.6.2 obn my system to get USB 3G Modem stick to work. It install many files into /System/Library/Extensions. All files are SierraDIPService.kext SierraFSPService.kext SierraDevSupport.kext.
Remove SierraDIPService.kext from the above Extensions folder allow MobileDevice.pkg and othe installer that need to update system extension like soundflower.pkg to work properly.
So, Sierra driveris the culprit!! I have to uninstall Launch2Net off my system. But my USB Stick Modem will not work anymore
I have written to Nova System, the developer of Launch2Net to get fix to this problem
Will update if there is any progess

Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

Hi all,
I have TFS2012 and run several projects.
We encounterwed with such an error while using Build server.
Overall Build Process
Initial Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
00:00
Get the Build
00:00
Update Build Number
Initial Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Final Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Result = Ephone_DIT_Deploy_20150424.1
01:56
Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
Initial Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
00:00
Get the Build Directory
Initial Property Values
Result = d:\temp\217\CTI\Ephone_DIT_Deploy
01:53
If Not String.IsNullOrEmpty(ConfigurationFolderPath)
Initial Property Values
Condition = True
01:53
Run TfsBuild for Configuration Folder
Initial Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp"
00:08
Getting sources
00:02
Labeling sources
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
00:19
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:10
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
MSBuild Log File
00:08
Generating list of changesets
00:20
Built Skins\SkinEPhone.cs for default targets.
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
00:03
Creating work item
Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Final Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
Final Property Values
Condition = True
Final Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
Final Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
Please have a look and guide where to find a problem
Thanks ahead

Hi Hooi,
I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
Best regards,

[svn] 3229: Made some updates to the config test framework.

Revision: 3229
Author: [email protected]
Date: 2008-09-16 12:15:34 -0700 (Tue, 16 Sep 2008)
Log Message:
Made some updates to the config test framework. This should be able to run on all the regression boxes now assuming I got the names of all the log files correct for the different app servers. After this checkin, I will update the regression scripts to start running the config framework tests under automation. This will be another antcall from the run.tests target in automation.xml which will run the tests and then load the results to the test results db.
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/testsuites/config/build.xml
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/DestinationWith NoChannelTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/DestinationWith NoIDTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidAckn owledgeModeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidDeli veryModeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidDest inationTypeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidMess ageTypeTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/NoConnectio nFactoryTest/error.txt
blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/NoJNDINameT est/error.txt
blazeds/trunk/qa/resources/frameworks/qa-frameworks.zip

despite the workaround, it doesn't fix the real problem. It shouldn't be a huge deal for adobe to add support for multiple svn versions. Dreamweaver is the first tool i've used that works with svn that doesn't support several types of svn meta data. If they're going to claim that Dreamweaver supports svn is should actually support svn, the current version, not a version several years old. This should have been among the first patches released, or at least after snow leopard came out (and packaged with it the current version of svn).
does anyone know if the code that handles meta data formatting is something that is human readable, or where it might be, or is it in compiled code.
i signed up for the forums, for the sole purpose of being able to vent about this very frustrating and disappointing situation.

[svn:fx-trunk] 11314: add the empty properties file to svn to fix the build .properties

Revision: 11314
Author:   [email protected]
Date:     2009-10-30 10:38:34 -0700 (Fri, 30 Oct 2009)
Log Message:
add the empty properties file to svn to fix the build.properties
QE notes:
Doc notes:
Bugs: fix the build
Reviewer: Pete
Tests run: checkintests
Is noteworthy for integration: no
Added Paths:
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/de_DE/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/fr_FR/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/ja_JP/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/ru_RU/empty.properties
    flex/sdk/trunk/frameworks/projects/playerglobal/bundles/zh_CN/empty.properties

Thats good news.

[svn] 785: test to see if the build is still broken.

Similar Messages

Maybe you are looking for