[MacRuby] #1329: The deployment target for MacRuby Xcode projects does not set a dependency on the app being built first
MacRuby
ruby-noreply at macosforge.org
Tue Jun 14 11:11:45 PDT 2011
#1329: The deployment target for MacRuby Xcode projects does not set a dependency
on the app being built first
------------------------------------+---------------------------------------
Reporter: mrada@… | Owner: lsansonetti@…
Type: defect | Status: new
Priority: blocker | Milestone:
Component: MacRuby | Keywords:
------------------------------------+---------------------------------------
By not setting the dependency, it is possible for people who are new to
run the deployment before building their app. This is bad for at least two
reasons:
1. If you have made changes since the last build (e.g. a bug fix) and you
deploy before building an updated version of the app, you will build a
deployed app with a bug.
2. If the app has never been built (or you cleaned out the old build), you
will get a confusing error about the app not existing.
For problem 2 I added an extra message to macruby_deploy to message users
if the app does not exist
(https://github.com/MacRuby/MacRuby/commit/ced3d91ec99e0e82f180a7abbf4a536d69a66dab),
but that is really just a band-aid solution.
--
Ticket URL: <http://www.macruby.org/trac/ticket/1329>
MacRuby <http://macruby.org/>
More information about the macruby-tickets
mailing list