How to mention the magento version compatibility in composer.json Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Magento2: different kind of composer.json filesError in using composer to install a module in Magento 2.0Validating composer.json in magento giving me the following errorMagento 2.2 : requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.1.11) does not satisfy that requirementMagento extension install - Dependancy errorInstallation issues on packaging a module: Magento 2Can't install module using composer on Magento 2.1Issues using the Code Migration to migrate to Magento CE v2.2.3 w/ PHP 7.1What is the Composer.Json file and what is it used for?Module version in composer.json
Should I use a zero-interest credit card for a large one-time purchase?
Can an alien society believe that their star system is the universe?
Fundamental Solution of the Pell Equation
Do wooden building fires get hotter than 600°C?
What is the longest distance a player character can jump in one leap?
How can I use the Python library networkx from Mathematica?
Is safe to use va_start macro with this as parameter?
Extracting terms with certain heads in a function
When coming out of haste, do attackers have advantage on you?
What is the probability distribution of linear formula?
Do square wave exist?
bold in theorem
Is there any way for the UK Prime Minister to make a motion directly dependent on Government confidence?
How to convince students of the implication truth values?
Using et al. for a last / senior author rather than for a first author
Can you shove before Attacking with Shield Master using a Readied action?
How to answer "Have you ever been terminated?"
Crossing US/Canada Border for less than 24 hours
Most bit efficient text communication method?
How do pianists reach extremely loud dynamics?
Why do we bend a book to keep it straight?
Why do the resolve message appear first?
Has negative voting ever been officially implemented in elections, or seriously proposed, or even studied?
Closed form of recurrent arithmetic series summation
How to mention the magento version compatibility in composer.json
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Magento2: different kind of composer.json filesError in using composer to install a module in Magento 2.0Validating composer.json in magento giving me the following errorMagento 2.2 : requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.1.11) does not satisfy that requirementMagento extension install - Dependancy errorInstallation issues on packaging a module: Magento 2Can't install module using composer on Magento 2.1Issues using the Code Migration to migrate to Magento CE v2.2.3 w/ PHP 7.1What is the Composer.Json file and what is it used for?Module version in composer.json
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am creating a module in Magento 2. Now I am writing composer.json. Here I write supporting PHP version
"require": ^7.0.0",
,
How do I write my module will be supported by Magento version greater than 2.1, not support by 2.0
I found
"magento/framework": "^102.0.0",
"magento/module-backend": "^101.0.0"
What is the meaning of above lines . is it the version of Magento?
what are 102.0.0 means?
module magento2.2 composer
edited Jan 11 at 11:41
Evince Development
1,092319
asked Jan 11 at 10:49
Sammu SundarSammu Sundar
10510
add a comment |
I am creating a module in Magento 2. Now I am writing composer.json. Here I write supporting PHP version
"require": ^7.0.0",
,
How do I write my module will be supported by Magento version greater than 2.1, not support by 2.0
I found
"magento/framework": "^102.0.0",
"magento/module-backend": "^101.0.0"
What is the meaning of above lines . is it the version of Magento?
what are 102.0.0 means?
module magento2.2 composer
edited Jan 11 at 11:41
Evince Development
1,092319
asked Jan 11 at 10:49
Sammu SundarSammu Sundar
10510
add a comment |
I am creating a module in Magento 2. Now I am writing composer.json. Here I write supporting PHP version
"require": ^7.0.0",
,
How do I write my module will be supported by Magento version greater than 2.1, not support by 2.0
I found
"magento/framework": "^102.0.0",
"magento/module-backend": "^101.0.0"
What is the meaning of above lines . is it the version of Magento?
what are 102.0.0 means?
module magento2.2 composer
edited Jan 11 at 11:41
Evince Development
1,092319
asked Jan 11 at 10:49
Sammu SundarSammu Sundar
10510
I am creating a module in Magento 2. Now I am writing composer.json. Here I write supporting PHP version
"require": ^7.0.0",
,
How do I write my module will be supported by Magento version greater than 2.1, not support by 2.0
I found
"magento/framework": "^102.0.0",
"magento/module-backend": "^101.0.0"
What is the meaning of above lines . is it the version of Magento?
what are 102.0.0 means?
module magento2.2 composer
module magento2.2 composer
edited Jan 11 at 11:41
Evince Development
1,092319
asked Jan 11 at 10:49
Sammu SundarSammu Sundar
10510
edited Jan 11 at 11:41
Evince Development
1,092319
asked Jan 11 at 10:49
Sammu SundarSammu Sundar
10510
edited Jan 11 at 11:41
Evince Development
1,092319
edited Jan 11 at 11:41
Evince Development
1,092319
edited Jan 11 at 11:41
Evince Development
1,092319
1,092319
asked Jan 11 at 10:49
Sammu SundarSammu Sundar
10510
asked Jan 11 at 10:49
Sammu SundarSammu Sundar
10510
asked Jan 11 at 10:49
Sammu SundarSammu Sundar
10510
10510
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
As far as I know, you cannot specify a version for the 'parent' project in general with composer. The version of a composer package (here the Magento shop) is even optional, so you could not reliably depend on it:
The version of the package. In most cases this is not required and should be omitted
And a Magento installation is consisting of Magento modules. And these modules have their own versions. Though it would desirable to tell composer "Hey, this module can only be used with version X of Magento", you actually have to make the extension dependent on the other Magento extensions, which seems to have their own versioning scheme (with versions > 100). And probably this is what you actually want, since (I guess) your module code really depends on those Magento core modules.
In the composer.json file of my installation (2.3.1) I found a required package "magento/product-community-edition":"2.3.1". It would be tempting to make the module dependent on this, however, this is discouraged:
Do not specify a dependency on meta packages (e.g. product-community-edition).
So it seems you should make your module open for different versions or specify the requirements in a readme file.
answered 8 mins ago
robschrobsch
1619
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f257510%2fhow-to-mention-the-magento-version-compatibility-in-composer-json%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As far as I know, you cannot specify a version for the 'parent' project in general with composer. The version of a composer package (here the Magento shop) is even optional, so you could not reliably depend on it:
The version of the package. In most cases this is not required and should be omitted
And a Magento installation is consisting of Magento modules. And these modules have their own versions. Though it would desirable to tell composer "Hey, this module can only be used with version X of Magento", you actually have to make the extension dependent on the other Magento extensions, which seems to have their own versioning scheme (with versions > 100). And probably this is what you actually want, since (I guess) your module code really depends on those Magento core modules.
In the composer.json file of my installation (2.3.1) I found a required package "magento/product-community-edition":"2.3.1". It would be tempting to make the module dependent on this, however, this is discouraged:
Do not specify a dependency on meta packages (e.g. product-community-edition).
So it seems you should make your module open for different versions or specify the requirements in a readme file.
answered 8 mins ago
robschrobsch
1619
add a comment |
As far as I know, you cannot specify a version for the 'parent' project in general with composer. The version of a composer package (here the Magento shop) is even optional, so you could not reliably depend on it:
The version of the package. In most cases this is not required and should be omitted
And a Magento installation is consisting of Magento modules. And these modules have their own versions. Though it would desirable to tell composer "Hey, this module can only be used with version X of Magento", you actually have to make the extension dependent on the other Magento extensions, which seems to have their own versioning scheme (with versions > 100). And probably this is what you actually want, since (I guess) your module code really depends on those Magento core modules.
In the composer.json file of my installation (2.3.1) I found a required package "magento/product-community-edition":"2.3.1". It would be tempting to make the module dependent on this, however, this is discouraged:
Do not specify a dependency on meta packages (e.g. product-community-edition).
So it seems you should make your module open for different versions or specify the requirements in a readme file.
answered 8 mins ago
robschrobsch
1619
add a comment |
As far as I know, you cannot specify a version for the 'parent' project in general with composer. The version of a composer package (here the Magento shop) is even optional, so you could not reliably depend on it:
The version of the package. In most cases this is not required and should be omitted
And a Magento installation is consisting of Magento modules. And these modules have their own versions. Though it would desirable to tell composer "Hey, this module can only be used with version X of Magento", you actually have to make the extension dependent on the other Magento extensions, which seems to have their own versioning scheme (with versions > 100). And probably this is what you actually want, since (I guess) your module code really depends on those Magento core modules.
In the composer.json file of my installation (2.3.1) I found a required package "magento/product-community-edition":"2.3.1". It would be tempting to make the module dependent on this, however, this is discouraged:
Do not specify a dependency on meta packages (e.g. product-community-edition).
So it seems you should make your module open for different versions or specify the requirements in a readme file.
answered 8 mins ago
robschrobsch
1619
As far as I know, you cannot specify a version for the 'parent' project in general with composer. The version of a composer package (here the Magento shop) is even optional, so you could not reliably depend on it:
The version of the package. In most cases this is not required and should be omitted
And a Magento installation is consisting of Magento modules. And these modules have their own versions. Though it would desirable to tell composer "Hey, this module can only be used with version X of Magento", you actually have to make the extension dependent on the other Magento extensions, which seems to have their own versioning scheme (with versions > 100). And probably this is what you actually want, since (I guess) your module code really depends on those Magento core modules.
In the composer.json file of my installation (2.3.1) I found a required package "magento/product-community-edition":"2.3.1". It would be tempting to make the module dependent on this, however, this is discouraged:
Do not specify a dependency on meta packages (e.g. product-community-edition).
So it seems you should make your module open for different versions or specify the requirements in a readme file.
answered 8 mins ago
robschrobsch
1619
answered 8 mins ago
robschrobsch
1619
answered 8 mins ago
robschrobsch
1619
answered 8 mins ago
robschrobsch
1619
1619
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f257510%2fhow-to-mention-the-magento-version-compatibility-in-composer-json%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
