./coho prepare-release-branch --version 3.4.0-rc1 -r android ./cordova-android/ =========== Executing: git fetch --progress origin ./cordova-android/ =========== Executing: git fetch --progress --tags origin ./cordova-android/ =========== Confirmed already up-to-date: cordova-android ./cordova-android/ =========== Executing: git checkout -b 3.4.x Switched to a new branch '3.4.x' ./cordova-js/ ================ Executing: git checkout -q 3.4.0-rc1 ./cordova-js/ ================ Executing: grunt
why are our last lines different? On Wed, Jan 22, 2014 at 4:09 PM, Joe Bowser <bows...@gmail.com> wrote: > Hey > > It looks like something either changed with cordova-js or with coho, > because I can't get coho to build: > jbowser-MacBookPro:~ jbowser$ cordova-coho/coho prepare-release-branch > --version 3.4.0-rc1 -r cordova-android > ./cordova-android/ =========== Executing: git fetch --progress apache > ./cordova-android/ =========== Executing: git fetch --progress --tags > apache > ./cordova-android/ =========== Confirmed already up-to-date: > cordova-android > ./cordova-android/ =========== Executing: git checkout 3.4.x > Already on '3.4.x' > ./cordova-js/ ================ Executing: git checkout -q 3.4.0-rc1 > ./cordova-js/ ================ Executing: grunt cordovajs > Warning: Task "cordovajs" not found. Use --force to continue. > > I'm going to have to proceed manually with the tagging and vendoring. > The next time we change how we build the JS, can we make sure coho > works with it, otherwise there's no point having it. > > On Wed, Jan 22, 2014 at 2:04 PM, Josh Soref <jso...@blackberry.com> wrote: > > Fwiw, cordova-blackberry is currently broken due to the config.xml move. > > > > We need to land a fix for this. > > > > --------------------------------------------------------------------- > > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from > your system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. > > >
