Ya love it. =)
On Fri, Mar 22, 2013 at 1:02 PM, Filip Maj <[email protected]> wrote: > Agree with everything Braden said > > On 3/22/13 12:05 PM, "tommy-carlos Williams" <[email protected]> wrote: > >>+1 for ./platforms becoming a build artifact. >> >>That is already how we are attempting to roll in our project using the >>cli, though its not quite right yet. >> >>On 23/03/2013, at 5:26, Braden Shepherdson <[email protected]> wrote: >> >>> We want this to stick around. One of my goals for the CLI is to make the >>> platforms/foo subdirectories completely build artifacts. Native code, >>>web >>> assets, JS code, all get copied on every prepare. That's not currently >>>true >>> for native code, but it is for the rest. >>> >>> Since we're doing that, we need the full content of the plugins to stick >>> around. Is there a problem with keeping this around? >>> >>> Braden >>> >>> >>> On Fri, Mar 22, 2013 at 2:12 PM, Brian LeRoux <[email protected]> wrote: >>> >>>> Cool. So, is this interim or necessary to exist for all of time? >>>> (Would assume you need some sort of staging area but not sure you need >>>> to keep em around if we can cache the manifest info or something.) >>>> >>>> On Fri, Mar 22, 2013 at 11:01 AM, Braden Shepherdson >>>> <[email protected]> wrote: >>>>> I assume you mean the top-level plugins/ folder in the CLI? >>>>> >>>>> That is where plugins are cached when you cordova plugin add them. >>>> Whether >>>>> they're coming from local directories or git or wherever, they get >>>>>copied >>>>> here. Then on a prepare this is where the plugin's assets are copied >>>> from. >>>>> >>>>> Braden >>>>> >>>>> >>>>> On Fri, Mar 22, 2013 at 1:56 PM, Brian LeRoux <[email protected]> wrote: >>>>> >>>>>> ... >>>> >
