Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-21 Thread John Pollard
All, Just deleting ._Inrax.eomodeld wasn't enough, all sorts of other mysterious problems cropped up, caused by the ._ flies in the model directory itself, so they all need to go. Mysteriously the problems didn't show on my test server for the very same deployment tree containing the same

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-20 Thread John Pollard
The problem turns out to be the inclusion of Mac OS X hidden files in the release tree that are related to how Mavericks stores meta information about files and directories. For example, here is the content of the model Resources directory: ._Info.plist Info.plist ._Inrax.eomodeld

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-20 Thread David Avendasora
Interesting! The place to suppress inclusion of these files is in each project’s *.patternset files in the woproject directory at the root of the project. Eclipse may be hiding this directory from you as normally you wouldn’t need to modify it. Inside are several .patternset files that

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-20 Thread Timothy Worman
I have been developing on Mavericks for some time and haven’t had this issue. There is no underscore convention file naming in any of my projects. Is it possible that these projects' files were initially stored on a file server/share that used the underscore naming for file metadata? That is

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-20 Thread David Avendasora
Hi Tim, That makes a lot of sense. Just to be clear, you are saying that you build your apps *for deployment* on your development machine using Ant. Right? Dave On Nov 20, 2013, at 12:35 PM, Timothy Worman li...@thetimmy.com wrote: I have been developing on Mavericks for some time and

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-20 Thread Timothy Worman
Hey David: Yeah, at this time I still build with ant and deploy manually - probably because I’m just a Tim and not a David. I haven’t had any problems at all and I definitely do not have the type of metadata files John is describing in any of my projects or elsewhere on my filesystem. Tim

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-20 Thread David LeBer
John, Hidden underscore files generally only show up when you are using a file system that doesn’t support resource forks. If you drive is HFS+ then you shouldn’t see them. But I think your problem may be with your workflow (specifically with tar), not the filesystem.

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-20 Thread Mark Ritchie
Hi Sorry to come late to the party. I believe those files which have the prefix ._ are Apple Double files and they contain the resource fork and possibly extended attributes of files which are not on HFS. You might have luck checking for any extended attributes before archiving the file as I

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-19 Thread John Pollard
Hi Chuck, You mean Info.plist and Inrax.eomodeld look bogus? Inrax is the name of the system being modelled. No changes in deployment, other than the deployed apps with their embedded frameworks. Those are the same file model directory names as I currently have running on the live server now.

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-19 Thread Chuck Hill
I meant the names/paths in the error message. On 2013-11-19 8:41 AM, John Pollard wrote: Hi Chuck, You mean Info.plist and Inrax.eomodeld look bogus? Inrax is the name of the system being modelled. No changes in deployment, other than the deployed apps with their embedded frameworks. Those

Re: Deploying from Mavericks, now wants index.eomodeld / eomodel.plist

2013-11-19 Thread John Pollard
Yes. Frameworks including WO / Wonder etc. are all embedded in the app, so something must be up in my Mavericks dev environment. On 19 Nov 2013, at 16:48, Chuck Hill ch...@global-village.net wrote: I meant the names/paths in the error message. On 2013-11-19 8:41 AM, John Pollard wrote: