[jira] [Commented] (CB-3401) split BlackBerryOS from Playbook

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CB-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688277#comment-13688277 ] 

ASF subversion and git services commented on CB-3401:
-----------------------------------------------------

Commit b66b2ef13a61a5b6902fcfa8eb66886ac02711a3 in branch refs/heads/master from [~lorin]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;h=b66b2ef ]

[CB-3401] renamed blackberry root folder to bbos

[CB-3928] fixed link to cordova project home page, and sub project references

[CB-3401] removed playbook native implementation from bbos

[CB-3401] removed ext-air references from ant create script

[CB-3401] updated build and run project level scripts target blackberry build/deployment only

[CB-3401] added playbook implementation in new directory

[CB-3401] removed bbos references in build.xml

[CB-3401] updated build and run project level scripts to target playbook build/deployment only

[CB-3401] fixed bug in run tool, --help prints message appropriately

[CB-3401] playbook create, build and run tools updated to support independant directories

                
> split BlackBerryOS from Playbook
> --------------------------------
>
>                 Key: CB-3401
>                 URL: https://issues.apache.org/jira/browse/CB-3401
>             Project: Apache Cordova
>          Issue Type: New Feature
>          Components: BlackBerry
>    Affects Versions: 2.7.0
>            Reporter: Lorin Beer
>            Assignee: Lorin Beer
>             Fix For: 2.9.0
>
>
> new  directory structure will split the playbook/blackberry10/blackberry10 implementations into separate folders in the root of the repo.
> BB10 is already split off.
> This will cause minor duplication in tooling, but this preps for the deprecation of BBOS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira