Thanks Bryan! I think that's enough to retract my +1. I'll try and fix it up and post another RC.
On Mon, Mar 3, 2014 at 9:42 AM, Bryan Higgins <br...@bryanhiggins.net>wrote: > I found another issue which may actually be a show stopper. > > Any plugins added prior to adding a platform are not included in that > platform. > > This is a regression from 3.4.0-0.1.0 > > https://issues.apache.org/jira/browse/CB-6151 > > > On Sun, Mar 2, 2014 at 3:30 PM, Carlos Santana <csantan...@gmail.com> > wrote: > > > How do we handle dependencies for cordova-cli and plugman once you put > them > > in /dist/ ? > > > > These tools don't work if user doesn't get/install the dependencies > > > > I have being looking for more information on these with no luck on what > > should be the best way to handle it for cordova. > > > > So far I have found two projects "struts" [1] and "maven" [2], > > Each one has a document/html explaining for end users what is the > > dependency graph and information about each dependency (Version, License, > > and Location to Get it) > > > > I know we use npm to install and resolved dependencies but I think we > could > > start by documenting for end users what are the dependencies that the > > cordova-cli and plugman need to be able to run. > > Maybe start with a simple table with the dependency graph, version, > license > > type (i.e. GPLv2, MIT, Apache 2.0, etc..) and the npm uri and repo uri > and > > hash. > > > > We could also looked into providing a a convenient "binary" > > cordova-cli-3.4.0.-1.0.1-npmbundle.tgz that includes all the dependencies > > bundled (i.e. npm pack) [3] > > > > 1: > > > http://maven.apache.org/wagon/wagon-providers/wagon-ftp/dependencies.html > > 2: http://struts.apache.org/release/2.3.x/struts2-core/dependencies.html > > 3: https://www.npmjs.org/doc/cli/npm-pack.html > > > > > > > > > > > > > > On Fri, Feb 28, 2014 at 12:13 PM, Andrew Grieve <agri...@chromium.org > > >wrote: > > > > > Yes, that's my goal. > > > > > > > > > On Fri, Feb 28, 2014 at 11:09 AM, Marcel Kinard <cmarc...@gmail.com> > > > wrote: > > > > > > > To ask the question a bit differently, why is released code not going > > to > > > > dist? Additional channels are fine, but the channels should always > > > include > > > > dist, right? > > > > > > > > My intention in asking this question is to not force a vote, but for > > > > consumers to find all Apache-released software on dist. Or do I > > > > misunderstand the role of dist? I'm looking at the sections "Where do > > > > releases go" and "Where can we host public (GA) releases" of > > > > http://www.apache.org/dev/release > > > > > > > > Or are the tools and plugins not considered "released code"? > > > > > > > > (I can hear the moans already, just trying to keep us honest.) > > > > > > > > Andrew, do I understand that you'll be posting tools and plugins to > > dist? > > > > > > > > On Feb 27, 2014, at 11:51 AM, Brian LeRoux <b...@brian.io> wrote: > > > > > > > > > We do not have to vote on code not on /dist. > > > > > On Feb 27, 2014 8:47 AM, "Andrew Grieve" <agri...@chromium.org> > > wrote: > > > > > > > > > > > > > > > > > > > -- > > Carlos Santana > > <csantan...@gmail.com> > > >
