Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

composer global require "fxp/composer-asset-plugin:dev-master" fails #341

Open
Babi-B opened this issue Apr 28, 2022 · 1 comment
Open

composer global require "fxp/composer-asset-plugin:dev-master" fails #341

Babi-B opened this issue Apr 28, 2022 · 1 comment
Labels
support

Comments

@Babi-B
Copy link

Babi-B commented Apr 28, 2022

Problem Statement

I just installed composer on my machine. When I run composer global require "fxp/composer-asset-plugin:dev-master" I get back

Changed current directory to C:/Users/USER/AppData/Roaming/Composer
./composer.json has been created
Running composer update fxp/composer-asset-plugin
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires fxp/composer-asset-plugin dev-master, found fxp/composer-asset-plugin[v1.0.0-beta1, ..., 1.4.x-dev] but it does not match the constraint.


Installation failed, deleting ./composer.json.

Environment

I'm on Windows 10, RAM 8Gig, and 300Gig SSD.
Composer version 2.3.5
@francoispluchino
Copy link
Member

Hello,

This plugin is only compatible with Composer 1. As indicated on the readme and the issue #334, the next major version of Composer Asset Plugin is so different, but also incompatible with the current version, that it became a new project named Foxy.

myii added a commit to myii/osw-devops that referenced this issue Jun 2, 2022
@myii
fix(composer): install v1 to keep using fxp/composer-asset-plugin
f3f7350 
fxpio/composer-asset-plugin#341 (comment)

> This plugin is only compatible with Composer 1. As indicated on the
> readme and the issue #334, the next major version of Composer Asset
> Plugin is so different, but also incompatible with the current version,
> that it became a new project named Foxy.

Installing from https://getcomposer.org/installer gets v2 (at the time
of this commit), which doesn't work with the `composer-asset-plugin`.
Installing from the available package still gets v1, at least on `bionic`.
Use this until Foxy can be evaluated.

Also update the test to check for `composer.json`, since the directory
is created, even with the plugin isn't installed properly (e.g. with v2).
@myii myii mentioned this issue Jun 2, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
support
Milestone
No milestone
Development

No branches or pull requests
2 participants
@francoispluchino @Babi-B