Topic
  • 5 replies
  • Latest Post - ‏2013-01-22T20:36:15Z by IdanAdar
SystemAdmin
SystemAdmin
2327 Posts

Pinned topic common build failed

‏2013-01-05T00:41:13Z |
When i try to build and deploy my app I see the following in my console:

2013-01-04 17:41:50 Activation done.
2013-01-04 17:41:50 Starting build process: application 'Inventory', all environments
2013-01-04 17:41:50 FWLST1040E: common build failed: File 'C:\Users\Carlos\AppData\Local\Temp\worklightBuildcommon8441950236864446783\preview\default\StockAppSOA.html' does not exist
2013-01-04 17:41:50 Application 'Inventory' with all environments build finished.
2013-01-04 17:41:50 FWLST1035I: No environments to build.
That StockAppSOA.html file is from a project that I have erased already but somehow when I try to build and deploy other projects the server is pointing to that file.
please help.
  • SystemAdmin
    SystemAdmin
    2327 Posts

    Re: common build failed

    ‏2013-01-05T00:44:20Z  
    Forgot to add these info:

    Operation System: Windows 64 bit
    Java: Oracle 64 bit
    Database: MySQL

    Installation type: Enterprise Edition
    Eclipse: JEE
    Worklight plug-in: 5.0.5
  • SystemAdmin
    SystemAdmin
    2327 Posts

    Re: common build failed

    ‏2013-01-05T00:49:13Z  
    Here are things you can try:

    • Starting eclipse with -clean (details/help: http://stackoverflow.com/q/2030064/186909) > build all and deploy
    • Remove everything in the 'bin' folder > refresh the project > build all and deploy
    • Remove the 'WorklightServerHome' folder from your workspace > refresh the project > build all and deploy
    • Switch to a clean workspace > import the project > [x] copy files > build all and deploy
    • Remove the environments > add them again > build all and deploy
    • If all else fails, create a new project on a new workspace and manually copy the contents in common/ and any .jar/etc files you need > build all and deploy

    Note: Always keep a backup of your data around in case you want to go back :)
  • SystemAdmin
    SystemAdmin
    2327 Posts

    Re: common build failed

    ‏2013-01-05T01:24:19Z  
    Here are things you can try:

    • Starting eclipse with -clean (details/help: http://stackoverflow.com/q/2030064/186909) > build all and deploy
    • Remove everything in the 'bin' folder > refresh the project > build all and deploy
    • Remove the 'WorklightServerHome' folder from your workspace > refresh the project > build all and deploy
    • Switch to a clean workspace > import the project > [x] copy files > build all and deploy
    • Remove the environments > add them again > build all and deploy
    • If all else fails, create a new project on a new workspace and manually copy the contents in common/ and any .jar/etc files you need > build all and deploy

    Note: Always keep a backup of your data around in case you want to go back :)
    Thank you cnandreu,

    I've tried all the options you gave me,but none of them seemed to work.

    But I finally found the problem, so I'm going to explain it here, in case there is someone out there with a similiar issue:

    When I copied most of the functionality on my script file, adapters, and html from one project to another, one of the information I also copied was the application-descriptor and what happened is that there is a tag <mainFile> and this had the old project main HTML instead of the new one I was using, once I corrected this I was again able to build and deploy my project.
  • SystemAdmin
    SystemAdmin
    2327 Posts

    Re: common build failed

    ‏2013-01-22T20:24:42Z  
    Thank you cnandreu,

    I've tried all the options you gave me,but none of them seemed to work.

    But I finally found the problem, so I'm going to explain it here, in case there is someone out there with a similiar issue:

    When I copied most of the functionality on my script file, adapters, and html from one project to another, one of the information I also copied was the application-descriptor and what happened is that there is a tag <mainFile> and this had the old project main HTML instead of the new one I was using, once I corrected this I was again able to build and deploy my project.
    I just built a working Android Application from scratch and tested it so I would know it's working then
    copy from another project my common (HTML,CSS,JS,etc) and now I continue to get this message too.

    2013-01-22 15:23:36 Activation done.
    2013-01-22 15:23:36 Starting build process: application 'anUSPSHYALLV00', all environments
    2013-01-22 15:23:37 FWLST1040E: android build failed: No match found
    2013-01-22 15:23:38 FWLST1040E: common build failed: No match found
    2013-01-22 15:23:38 Application 'anUSPSHYALLV00' with all environments build finished.
    2013-01-22 15:23:38 FWLST1035I: No environments to build.

    I checked in the Application Description as mentioned in this thread but it's the same as it was
    in the working example and I have put my replacement HTML into the same .html so I really don't
    know what to look for next to fix this.
  • IdanAdar
    IdanAdar
    741 Posts

    Re: common build failed

    ‏2013-01-22T20:36:15Z  
    I just built a working Android Application from scratch and tested it so I would know it's working then
    copy from another project my common (HTML,CSS,JS,etc) and now I continue to get this message too.

    2013-01-22 15:23:36 Activation done.
    2013-01-22 15:23:36 Starting build process: application 'anUSPSHYALLV00', all environments
    2013-01-22 15:23:37 FWLST1040E: android build failed: No match found
    2013-01-22 15:23:38 FWLST1040E: common build failed: No match found
    2013-01-22 15:23:38 Application 'anUSPSHYALLV00' with all environments build finished.
    2013-01-22 15:23:38 FWLST1035I: No environments to build.

    I checked in the Application Description as mentioned in this thread but it's the same as it was
    in the working example and I have put my replacement HTML into the same .html so I really don't
    know what to look for next to fix this.
    Why do you create a project and application, build and deploy it but then replace its web resources with those from another project?
    There is likely some manual changes you did not do and thus it fails; this a very not recommended way to work.

    Hard to pin-point where it fails. If you'd like you can post your changed Worklight project and we'll give it a look, but I strongly suggest to just not work this way.

    Idan Adar
    QA Engineer
    IBM Worklight Mobile Platform