[
https://issues.apache.org/jira/browse/CB-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106063#comment-14106063
]
Steve Gill commented on CB-7363:
--------------------------------
Was merely giving you different workflow ideas by showing you mine. It isn't
going to be acceptable for everyone's use cases.
If I want to test official releases:
cd cordova-cli/node-modules
git checkout SOMETAG
npm unlink cordova-lib
npm install
or
cd cordova-cli/node-modules
npm install cordova-lib
or
cd cordova-lib
git checkout SOMETAG (if it is npm linked in cli, it will use the version i
just checked out now)
I'm sure pros and cons exist for many of these workflows. Just thought I'd
share in hopes that it would help you with your workflow woes.
> 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
> Fix For: 3.6.0
>
>
> 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)
