• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Framework Does Not Exist
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Framework Does Not Exist


  • Subject: Re: Framework Does Not Exist
  • From: David Avendasora <email@hidden>
  • Date: Mon, 23 Aug 2010 15:36:28 -0400

Hi Pascal,

My apologies, "hudson.build.properties" is what I used to be calling it. I have changed the name to simply "build.properties" to make sure there wasn't something going weird with the name.

Here's the build script that setsup the Hudson workspace and dynamically creates the build.properties file for the job (look at the very end):
http://services.wocommunity.org:8080/job/ERModernMoviesDemo/ws/HudsonBuildFiles/setupWOProjectWorkspace.sh/*view*/

Then you can compare that to the file it creates:
http://services.wocommunity.org:8080/job/ERModernMoviesDemo/ws/Root/build.properties/*view*/

Looking at the build.xml file:
http://services.wocommunity.org:8080/job/ERModernMoviesDemo/ws/Projects/Application/build.xml/*view*/

I can't see why what I'm doing isn't working on Linux.

Dave




On Aug 23, 2010, at 3:23 PM, Pascal Robert wrote:

>
>> I have a custom hudson.build.properties file that I'm passing into Ant using the -propertyfile argument. It defines the wo.local.root and wo.local.frameworks variables and I've verified that the frameworks do exist in the locations defined.
>
> Shouldn't we see a hudson.build.properties line in the output? Right now, we see :
>
> jar:file:/usr/local/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml from a zip file
> [property] Loading /var/lib/hudson/jobs/ERModernMoviesDemo/workspace/Projects/Application/build.properties
> [property] Loading /var/lib/hudson/Library/Application Support/WOLips/wolips.properties
>
> But no mention of "hudson.build.properties". I don't know if it's normal or not :-) Does hudson.build.properties should be call on the "call ant" section of the configure page, eg :
>
> 	build -verbose -propertyfile ${WORKSPACE}/Root/build.properties -lib ${WORKSPACE}/Root/lib/woproject.jar
>
> ?
>
>> What is very odd is that if I don't pass this file in, the build fails at the same point, but complaining about ERExtensions as opposed to Ajax, so it seems to me that the properties are correctly defined, but there is something wrong with the Ajax framework, but I can't see any difference (including case-sensitivity issues).
>>
>> So again, this is the same config.xml file for hudson on both Mac and Linux, they both checkout the same revision of Wonder and the same revision of ERModernMovies.
>>
>> Any ideas as to why the build is failing on Linux?
>>
>> Dave
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
>

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Framework Does Not Exist
      • From: David Avendasora <email@hidden>
References: 
 >Framework Does Not Exist (From: David Avendasora <email@hidden>)

  • Prev by Date: Wonder D2W Application build.xml
  • Next by Date: EO Models won't open
  • Previous by thread: Framework Does Not Exist
  • Next by thread: Re: Framework Does Not Exist
  • Index(es):
    • Date
    • Thread