Ahh cool lemme know and I can take a look at it / merge it!

On 5/10/13 11:01 AM, "Jeffrey Heifetz" <jheif...@blackberry.com> wrote:

>There will be a pull request coming, its just running through testing atm
>https://github.com/blackberry/cordova-plugman/pull/2. I expect to
>re-target this to apache in the coming hours.
>
>On 13-05-10 1:52 PM, "Filip Maj" <f...@adobe.com> wrote:
>
>>Only issue I see is that <source-file> support was removed from the
>>blackberry platform handler. With <config-file> and <asset> elements
>>being
>>handled in prepare, this leaves the blackberry platform handler empty.
>>Would we not want some manner of native file / library handling in the
>>blackberry implementation of plugman?
>>
>>On 5/9/13 8:43 PM, "Lorin Beer" <lorin.beer....@gmail.com> wrote:
>>
>>>great, thanks Fil!
>>>
>>>
>>>On Thu, May 9, 2013 at 1:27 PM, Filip Maj <f...@adobe.com> wrote:
>>>
>>>> I will look into these when I'm back in action tomorrow Lorin.
>>>>
>>>> On 5/7/13 8:29 AM, "Lorin Beer" <lorin.beer....@gmail.com> wrote:
>>>>
>>>> >for those working on plugman/cli:
>>>> >
>>>> >the code migration for blackberry's implementation of bb-cordova has
>>>> >begun.
>>>> >The plan is to merge their new implementation into
>>>> >apache/blackberry-cordova and apache/cordova-js as soon as possible.
>>>> >The blackberry team also has contributions to plugman and the cli.
>>>> >Currently, those contribs have been pushed to the apache plugman
>>>>future
>>>> >branch, and apache cli future-bb10 branch.
>>>> >
>>>> >The changes to plugman seem to be orthogonal, but shout at me if they
>>>>are
>>>> >breaking future.
>>>> >
>>>> >- Lorin
>>>>
>>>>
>>
>
>
>---------------------------------------------------------------------
>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.

Reply via email to