Open FlxPeters opened 7 years ago
Are you using tags or branch names with Toran? There are a few issues with external sources being preferred when the local Studio-ised copy and the remote are sitting on the same commit, branch or tag.
See what happens when you
develop
on your local copy of the package and require
dev-develop
in your composer.json
I ran into the same issue, Composer favors our Satis tagged release over the local Studio loaded one.
I had similar problem. Turns out studio only picks my loaded local package only if it doesn't have local git changes (stuff I left unstaged). That said try stashing the package changes before doing composer update
and simply pop them after successful symlink.
Nope, scratch that. I just had some bizarre dependency incompatibility.
Please try out the newly released 0.14.0-beta1 version. I am hoping this issue will be gone.
(Note that you will have to run composer update
and composer dump-autoload
for the installation of any package.)
Hi,
i have a Toran proxy for my custom bundles included via repositories which also inclues a package i want to load with studio:
When i run composer update for my package, i always get the package from toran instead of studio. Studio is loaded properly.
It seams to load the package with studio, but then toran also gives me the package. Is this right or how could i force composer to use my studio linked package?
Thanks, Felix