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 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 > usually something you’d encounter with a product like netatalk, or…? When you > copied them down from a server, there could have been metadata stored like > that. > > Tim > UCLA GSE&IS > > On Nov 20, 2013, at 6:31 AM, David Avendasora <webobje...@avendasora.com> > wrote: > >> 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 control what goes-into and >> excluded-from the Classes, Resources and WebServerResources directory at >> build time. >> >> This is an VERY IMPORTANT find! If you are using Jenkins on a Mavericks box, >> you are probably going to need to make these changes as well. >> >> Please post back when you’ve determined the exact settings that eliminate >> problem files. It should also get added to the Wiki so people googling >> WebObjects Mavericks will find it! >> >> Dave >> >> >> On Nov 20, 2013, at 5:52 AM, John Pollard <j...@pollardweb.com> wrote: >> >>> 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 Inrax.eomodeld Java ._Java >>> >>> When I deleted ._Inrax.eomodeld the problem went away. Interesting how that >>> foxed the WO frameworks somehow. >>> >>> So I will look into how to suppress these in the release build. >> >> >> ————————————————————————————— >> WebObjects - so easy that even Dave Avendasora can do it!™ >> ————————————————————————————— >> David Avendasora >> Senior Software Abuser >> Nekesto, Inc. >> >> >> >> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-deploy/lists%40thetimmy.com >> >> This email sent to li...@thetimmy.com > > > ————————————————————————————— WebObjects - so easy that even Dave Avendasora can do it!™ ————————————————————————————— David Avendasora Senior Software Abuser Nekesto, Inc. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com