From: Josh P. <jos...@gm...> - 2008-12-16 18:33:43
|
When building a framework, I keep getting the following on the console: [woframework] Installing ${framework.name} in . and wind up with a directory name (literally) "$ {framework.name}.framework" I've looked at my build.xml, and even replaced it with the latest build.xml. I've also looked at my build.properties and didn't see anything that would affect this. Any insights? |
From: Chuck H. <ch...@gl...> - 2008-12-16 18:41:36
|
On Dec 16, 2008, at 10:33 AM, Josh Paul wrote: > When building a framework, I keep getting the following on the > console: > > [woframework] Installing ${framework.name} in . > > and wind up with a directory name (literally) "$ > {framework.name}.framework" > > I've looked at my build.xml, and even replaced it with the latest > build.xml. I've also looked at my build.properties and didn't see > anything that would affect this. > > Any insights? This should be project.name if you are using the nightly wolips. Is framework.name in build.properties? Is build.properties getting loaded by build.xml? Chuck -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects |
From: Josh P. <jos...@gm...> - 2008-12-16 19:12:26
|
I deleted the build.properties file and copied one from another framework (and adjusted accordingly). All works as expected now. FWIW, I have in build.xml: <!-- property determination --> <target name="setProps"> <property file="${user.home}${file.separator}build.properties"/> <property file="build.properties"/> <property file="${user.home}${file.separator}Library$ {file.separator}wobuild.properties"/> <condition property="wo.properties.check.failed"> <not> <and> <isset property="wo.wosystemroot"/> <isset property="wo.wolocalroot"/> </and> </not> </condition> <fail message="Could not find ${user.home}${file.separator}Library ${file.separator}wobuild.properties." if="wo.properties.check.failed"/> <property name="install.dir" value="${wo.wolocalroot}/Library/ Frameworks"/> </target> On Dec 16, 2008, at 10:41 AM, Chuck Hill wrote: > > On Dec 16, 2008, at 10:33 AM, Josh Paul wrote: > >> When building a framework, I keep getting the following on the >> console: >> >> [woframework] Installing ${framework.name} in . >> >> and wind up with a directory name (literally) "$ >> {framework.name}.framework" >> >> I've looked at my build.xml, and even replaced it with the latest >> build.xml. I've also looked at my build.properties and didn't see >> anything that would affect this. >> >> Any insights? > > > This should be project.name if you are using the nightly wolips. Is > framework.name in build.properties? Is build.properties getting > loaded by build.xml? > > Chuck > > -- > Chuck Hill Senior Consultant / VP Development > > Practical WebObjects - for developers who want to increase their > overall knowledge of WebObjects or who are trying to solve specific > problems. > http://www.global-village.net/products/practical_webobjects > > > > > > |
From: Chuck H. <ch...@gl...> - 2008-12-16 19:17:05
|
On Dec 16, 2008, at 11:12 AM, Josh Paul wrote: > I deleted the build.properties file and copied one from another > framework (and adjusted accordingly). All works as expected now. > > FWIW, I have in build.xml: > > <!-- property determination --> > <target name="setProps"> > <property file="${user.home}${file.separator}build.properties"/> > <property file="build.properties"/> > <property file="${user.home}${file.separator}Library$ > {file.separator}wobuild.properties"/> You are using the old (stable) WOLips? I ask as this file is obsolete with New Hotness (nightly and soon to be stable). Chuck > > <condition property="wo.properties.check.failed"> > <not> > <and> > <isset property="wo.wosystemroot"/> > <isset property="wo.wolocalroot"/> > </and> > </not> > </condition> > <fail message="Could not find ${user.home}${file.separator}Library > ${file.separator}wobuild.properties." > if="wo.properties.check.failed"/> > <property name="install.dir" value="${wo.wolocalroot}/Library/ > Frameworks"/> > </target> > > On Dec 16, 2008, at 10:41 AM, Chuck Hill wrote: > >> >> On Dec 16, 2008, at 10:33 AM, Josh Paul wrote: >> >>> When building a framework, I keep getting the following on the >>> console: >>> >>> [woframework] Installing ${framework.name} in . >>> >>> and wind up with a directory name (literally) "$ >>> {framework.name}.framework" >>> >>> I've looked at my build.xml, and even replaced it with the latest >>> build.xml. I've also looked at my build.properties and didn't see >>> anything that would affect this. >>> >>> Any insights? >> >> >> This should be project.name if you are using the nightly wolips. >> Is framework.name in build.properties? Is build.properties getting >> loaded by build.xml? >> >> Chuck >> >> -- >> Chuck Hill Senior Consultant / VP Development >> >> Practical WebObjects - for developers who want to increase their >> overall knowledge of WebObjects or who are trying to solve specific >> problems. >> http://www.global-village.net/products/practical_webobjects >> >> >> >> >> >> > > -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects |
From: Josh P. <jos...@gm...> - 2008-12-16 19:27:20
|
Yes. Not on hotness right now. On Dec 16, 2008, at 11:16 AM, Chuck Hill wrote: > > On Dec 16, 2008, at 11:12 AM, Josh Paul wrote: > >> I deleted the build.properties file and copied one from another >> framework (and adjusted accordingly). All works as expected now. >> >> FWIW, I have in build.xml: >> >> <!-- property determination --> >> <target name="setProps"> >> <property file="${user.home}${file.separator}build.properties"/> >> <property file="build.properties"/> >> <property file="${user.home}${file.separator}Library$ >> {file.separator}wobuild.properties"/> > > You are using the old (stable) WOLips? I ask as this file is > obsolete with New Hotness (nightly and soon to be stable). > > Chuck > > >> >> <condition property="wo.properties.check.failed"> >> <not> >> <and> >> <isset property="wo.wosystemroot"/> >> <isset property="wo.wolocalroot"/> >> </and> >> </not> >> </condition> >> <fail message="Could not find ${user.home}${file.separator}Library >> ${file.separator}wobuild.properties." >> if="wo.properties.check.failed"/> >> <property name="install.dir" value="${wo.wolocalroot}/Library/ >> Frameworks"/> >> </target> >> >> On Dec 16, 2008, at 10:41 AM, Chuck Hill wrote: >> >>> >>> On Dec 16, 2008, at 10:33 AM, Josh Paul wrote: >>> >>>> When building a framework, I keep getting the following on the >>>> console: >>>> >>>> [woframework] Installing ${framework.name} in . >>>> >>>> and wind up with a directory name (literally) "$ >>>> {framework.name}.framework" >>>> >>>> I've looked at my build.xml, and even replaced it with the latest >>>> build.xml. I've also looked at my build.properties and didn't see >>>> anything that would affect this. >>>> >>>> Any insights? >>> >>> >>> This should be project.name if you are using the nightly wolips. >>> Is framework.name in build.properties? Is build.properties >>> getting loaded by build.xml? >>> >>> Chuck >>> >>> -- >>> Chuck Hill Senior Consultant / VP Development >>> >>> Practical WebObjects - for developers who want to increase their >>> overall knowledge of WebObjects or who are trying to solve >>> specific problems. >>> http://www.global-village.net/products/practical_webobjects >>> >>> >>> >>> >>> >>> >> >> > > -- > Chuck Hill Senior Consultant / VP Development > > Practical WebObjects - for developers who want to increase their > overall knowledge of WebObjects or who are trying to solve specific > problems. > http://www.global-village.net/products/practical_webobjects > > > > > > |