[
https://issues.apache.org/jira/browse/CB-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106013#comment-14106013
]
Steve Gill commented on CB-7363:
--------------------------------
I'm not a fan of adding a dev version dependency in package.json for the
cli/plugman on master. IMO package.json should only include versions that are
released! If someone checks out the cli from master, and runs npm install, it
will fail now. This can't happen! It needs to be fixed asap!
CLI package.json has cordova-lib dependency set to ~0.21.8-dev, The released
version is 0.21.7. npm install will fail!
I am fine with adding ~ or >= though instead of exact matching.
The way I handle working with unreleased versions for all of the repos and I
think is the optimal way to do it:
cd cordova-js
npm install
npm link
cd cordova-lib/cordova-lib
npm install
npm link
cd node-modules
npm link cordova-js (this will use the linked version from above)
cd cordova-plugman
npm install
npm link
cd node-modules
npm link cordova-lib
npm link cordova-js
cd cordova-cli
npm install
npm link
cd node-modules
npm link cordova-lib
> Do not insist on precise version of cordova-lib
> -----------------------------------------------
>
> Key: CB-7363
> URL: https://issues.apache.org/jira/browse/CB-7363
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, Plugman
> Affects Versions: 3.5.0
> Reporter: Josh Soref
> Assignee: Josh Soref
>
> Currently plugman's {{package.json}} has:
> {quote}
> "cordova-lib" : "0.21.6",
> {quote}
> Unfortunately, my git repo (from coho) of {{cordova-lib}} has {{0.21.8-dev}},
> which means that if I do {{npm install}} in {{cordova-plugman}}, and I have a
> _symlink_ to {{cordova-lib}} in its {{node_modules}}, the _symlink_ is
> *obliterated*. This isn't desirable and makes a totally mess out of git
> repositories.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
