JmsSerializerBundle installation ends with error: Unrecognized option “xml” under...












0















When I install a Symfony 4 skeleton project and add the JmsSerializerBundle, I get an error.



To reproduce:



composer create-project symfony/website-skeleton myproject
cd myproject
composer require jms/serializer-bundle


The installation ends with an error:



Using version ^3.0 for jms/serializer-bundle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Restricting packages listed in "symfony/symfony" to "4.1.*"
Package operations: 16 installs, 0 updates, 0 removals
- Installing hoa/exception (1.17.01.16): Loading from cache
- Installing hoa/event (1.17.01.13): Loading from cache
- Installing hoa/consistency (1.17.05.02): Loading from cache
- Installing hoa/visitor (2.17.01.16): Loading from cache
- Installing hoa/ustring (4.17.01.16): Loading from cache
- Installing hoa/protocol (1.17.01.14): Loading from cache
- Installing hoa/zformat (1.17.01.10): Loading from cache
- Installing hoa/iterator (2.17.01.10): Loading from cache
- Installing hoa/compiler (3.17.08.08): Loading from cache
- Installing hoa/regex (1.17.01.13): Loading from cache
- Installing hoa/math (1.17.05.16): Loading from cache
- Installing hoa/stream (1.17.02.21): Loading from cache
- Installing hoa/file (1.17.07.11): Loading from cache
- Installing jms/metadata (2.0.0): Loading from cache
- Installing jms/serializer (2.0.0): Loading from cache
- Installing jms/serializer-bundle (3.0.0): Loading from cache
Writing lock file
Generating autoload files
ocramius/package-versions: Generating version class...
ocramius/package-versions: ...done generating version class
Symfony operations: 1 recipe (f702450e5b1b913f83ea887faacbdb83)
- WARNING jms/serializer-bundle (>=2.0): From github.com/symfony/recipes-contrib:master
The recipe for this package comes from the "contrib" repository, which is open to community contributions.
Review the recipe at https://github.com/symfony/recipes-contrib/tree/master/jms/serializer-bundle/2.0

Do you want to execute this recipe?
[y] Yes
[n] No
[a] Yes for all packages, only for the current installation session
[p] Yes permanently, never ask again for this project
(defaults to n): y
- Configuring jms/serializer-bundle (>=2.0): From github.com/symfony/recipes-contrib:master
Executing script cache:clear [KO]
[KO]
Script cache:clear returned with error code 1
!!
!! In ArrayNode.php line 304:
!!
!! Unrecognized option "xml" under "jms_serializer.visitors"


Running composer etc on Windows 10 Powershell. I'm guessing the skeleton is too bare and it needs a dependency, but shouldn't that be solved automatically?



What could be the cause? How can I fix it? Thanks in advance for your help.










share|improve this question

























  • Which version of JMSerializerBundle did Composer install (2.x or 3.x)?

    – xabbuh
    Nov 22 '18 at 11:42











  • "jms/serializer-bundle": "^3.0"

    – Jorr.it
    Nov 22 '18 at 12:10











  • The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.

    – xabbuh
    Nov 22 '18 at 12:13











  • Thanks. If you change your comment to an answer, I will accept it.

    – Jorr.it
    Nov 22 '18 at 12:16
















0















When I install a Symfony 4 skeleton project and add the JmsSerializerBundle, I get an error.



To reproduce:



composer create-project symfony/website-skeleton myproject
cd myproject
composer require jms/serializer-bundle


The installation ends with an error:



Using version ^3.0 for jms/serializer-bundle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Restricting packages listed in "symfony/symfony" to "4.1.*"
Package operations: 16 installs, 0 updates, 0 removals
- Installing hoa/exception (1.17.01.16): Loading from cache
- Installing hoa/event (1.17.01.13): Loading from cache
- Installing hoa/consistency (1.17.05.02): Loading from cache
- Installing hoa/visitor (2.17.01.16): Loading from cache
- Installing hoa/ustring (4.17.01.16): Loading from cache
- Installing hoa/protocol (1.17.01.14): Loading from cache
- Installing hoa/zformat (1.17.01.10): Loading from cache
- Installing hoa/iterator (2.17.01.10): Loading from cache
- Installing hoa/compiler (3.17.08.08): Loading from cache
- Installing hoa/regex (1.17.01.13): Loading from cache
- Installing hoa/math (1.17.05.16): Loading from cache
- Installing hoa/stream (1.17.02.21): Loading from cache
- Installing hoa/file (1.17.07.11): Loading from cache
- Installing jms/metadata (2.0.0): Loading from cache
- Installing jms/serializer (2.0.0): Loading from cache
- Installing jms/serializer-bundle (3.0.0): Loading from cache
Writing lock file
Generating autoload files
ocramius/package-versions: Generating version class...
ocramius/package-versions: ...done generating version class
Symfony operations: 1 recipe (f702450e5b1b913f83ea887faacbdb83)
- WARNING jms/serializer-bundle (>=2.0): From github.com/symfony/recipes-contrib:master
The recipe for this package comes from the "contrib" repository, which is open to community contributions.
Review the recipe at https://github.com/symfony/recipes-contrib/tree/master/jms/serializer-bundle/2.0

Do you want to execute this recipe?
[y] Yes
[n] No
[a] Yes for all packages, only for the current installation session
[p] Yes permanently, never ask again for this project
(defaults to n): y
- Configuring jms/serializer-bundle (>=2.0): From github.com/symfony/recipes-contrib:master
Executing script cache:clear [KO]
[KO]
Script cache:clear returned with error code 1
!!
!! In ArrayNode.php line 304:
!!
!! Unrecognized option "xml" under "jms_serializer.visitors"


Running composer etc on Windows 10 Powershell. I'm guessing the skeleton is too bare and it needs a dependency, but shouldn't that be solved automatically?



What could be the cause? How can I fix it? Thanks in advance for your help.










share|improve this question

























  • Which version of JMSerializerBundle did Composer install (2.x or 3.x)?

    – xabbuh
    Nov 22 '18 at 11:42











  • "jms/serializer-bundle": "^3.0"

    – Jorr.it
    Nov 22 '18 at 12:10











  • The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.

    – xabbuh
    Nov 22 '18 at 12:13











  • Thanks. If you change your comment to an answer, I will accept it.

    – Jorr.it
    Nov 22 '18 at 12:16














0












0








0








When I install a Symfony 4 skeleton project and add the JmsSerializerBundle, I get an error.



To reproduce:



composer create-project symfony/website-skeleton myproject
cd myproject
composer require jms/serializer-bundle


The installation ends with an error:



Using version ^3.0 for jms/serializer-bundle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Restricting packages listed in "symfony/symfony" to "4.1.*"
Package operations: 16 installs, 0 updates, 0 removals
- Installing hoa/exception (1.17.01.16): Loading from cache
- Installing hoa/event (1.17.01.13): Loading from cache
- Installing hoa/consistency (1.17.05.02): Loading from cache
- Installing hoa/visitor (2.17.01.16): Loading from cache
- Installing hoa/ustring (4.17.01.16): Loading from cache
- Installing hoa/protocol (1.17.01.14): Loading from cache
- Installing hoa/zformat (1.17.01.10): Loading from cache
- Installing hoa/iterator (2.17.01.10): Loading from cache
- Installing hoa/compiler (3.17.08.08): Loading from cache
- Installing hoa/regex (1.17.01.13): Loading from cache
- Installing hoa/math (1.17.05.16): Loading from cache
- Installing hoa/stream (1.17.02.21): Loading from cache
- Installing hoa/file (1.17.07.11): Loading from cache
- Installing jms/metadata (2.0.0): Loading from cache
- Installing jms/serializer (2.0.0): Loading from cache
- Installing jms/serializer-bundle (3.0.0): Loading from cache
Writing lock file
Generating autoload files
ocramius/package-versions: Generating version class...
ocramius/package-versions: ...done generating version class
Symfony operations: 1 recipe (f702450e5b1b913f83ea887faacbdb83)
- WARNING jms/serializer-bundle (>=2.0): From github.com/symfony/recipes-contrib:master
The recipe for this package comes from the "contrib" repository, which is open to community contributions.
Review the recipe at https://github.com/symfony/recipes-contrib/tree/master/jms/serializer-bundle/2.0

Do you want to execute this recipe?
[y] Yes
[n] No
[a] Yes for all packages, only for the current installation session
[p] Yes permanently, never ask again for this project
(defaults to n): y
- Configuring jms/serializer-bundle (>=2.0): From github.com/symfony/recipes-contrib:master
Executing script cache:clear [KO]
[KO]
Script cache:clear returned with error code 1
!!
!! In ArrayNode.php line 304:
!!
!! Unrecognized option "xml" under "jms_serializer.visitors"


Running composer etc on Windows 10 Powershell. I'm guessing the skeleton is too bare and it needs a dependency, but shouldn't that be solved automatically?



What could be the cause? How can I fix it? Thanks in advance for your help.










share|improve this question
















When I install a Symfony 4 skeleton project and add the JmsSerializerBundle, I get an error.



To reproduce:



composer create-project symfony/website-skeleton myproject
cd myproject
composer require jms/serializer-bundle


The installation ends with an error:



Using version ^3.0 for jms/serializer-bundle
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Restricting packages listed in "symfony/symfony" to "4.1.*"
Package operations: 16 installs, 0 updates, 0 removals
- Installing hoa/exception (1.17.01.16): Loading from cache
- Installing hoa/event (1.17.01.13): Loading from cache
- Installing hoa/consistency (1.17.05.02): Loading from cache
- Installing hoa/visitor (2.17.01.16): Loading from cache
- Installing hoa/ustring (4.17.01.16): Loading from cache
- Installing hoa/protocol (1.17.01.14): Loading from cache
- Installing hoa/zformat (1.17.01.10): Loading from cache
- Installing hoa/iterator (2.17.01.10): Loading from cache
- Installing hoa/compiler (3.17.08.08): Loading from cache
- Installing hoa/regex (1.17.01.13): Loading from cache
- Installing hoa/math (1.17.05.16): Loading from cache
- Installing hoa/stream (1.17.02.21): Loading from cache
- Installing hoa/file (1.17.07.11): Loading from cache
- Installing jms/metadata (2.0.0): Loading from cache
- Installing jms/serializer (2.0.0): Loading from cache
- Installing jms/serializer-bundle (3.0.0): Loading from cache
Writing lock file
Generating autoload files
ocramius/package-versions: Generating version class...
ocramius/package-versions: ...done generating version class
Symfony operations: 1 recipe (f702450e5b1b913f83ea887faacbdb83)
- WARNING jms/serializer-bundle (>=2.0): From github.com/symfony/recipes-contrib:master
The recipe for this package comes from the "contrib" repository, which is open to community contributions.
Review the recipe at https://github.com/symfony/recipes-contrib/tree/master/jms/serializer-bundle/2.0

Do you want to execute this recipe?
[y] Yes
[n] No
[a] Yes for all packages, only for the current installation session
[p] Yes permanently, never ask again for this project
(defaults to n): y
- Configuring jms/serializer-bundle (>=2.0): From github.com/symfony/recipes-contrib:master
Executing script cache:clear [KO]
[KO]
Script cache:clear returned with error code 1
!!
!! In ArrayNode.php line 304:
!!
!! Unrecognized option "xml" under "jms_serializer.visitors"


Running composer etc on Windows 10 Powershell. I'm guessing the skeleton is too bare and it needs a dependency, but shouldn't that be solved automatically?



What could be the cause? How can I fix it? Thanks in advance for your help.







php composer-php symfony4 jmsserializerbundle






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 22 '18 at 12:14







Jorr.it

















asked Nov 22 '18 at 10:47









Jorr.itJorr.it

72211021




72211021













  • Which version of JMSerializerBundle did Composer install (2.x or 3.x)?

    – xabbuh
    Nov 22 '18 at 11:42











  • "jms/serializer-bundle": "^3.0"

    – Jorr.it
    Nov 22 '18 at 12:10











  • The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.

    – xabbuh
    Nov 22 '18 at 12:13











  • Thanks. If you change your comment to an answer, I will accept it.

    – Jorr.it
    Nov 22 '18 at 12:16



















  • Which version of JMSerializerBundle did Composer install (2.x or 3.x)?

    – xabbuh
    Nov 22 '18 at 11:42











  • "jms/serializer-bundle": "^3.0"

    – Jorr.it
    Nov 22 '18 at 12:10











  • The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.

    – xabbuh
    Nov 22 '18 at 12:13











  • Thanks. If you change your comment to an answer, I will accept it.

    – Jorr.it
    Nov 22 '18 at 12:16

















Which version of JMSerializerBundle did Composer install (2.x or 3.x)?

– xabbuh
Nov 22 '18 at 11:42





Which version of JMSerializerBundle did Composer install (2.x or 3.x)?

– xabbuh
Nov 22 '18 at 11:42













"jms/serializer-bundle": "^3.0"

– Jorr.it
Nov 22 '18 at 12:10





"jms/serializer-bundle": "^3.0"

– Jorr.it
Nov 22 '18 at 12:10













The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.

– xabbuh
Nov 22 '18 at 12:13





The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.

– xabbuh
Nov 22 '18 at 12:13













Thanks. If you change your comment to an answer, I will accept it.

– Jorr.it
Nov 22 '18 at 12:16





Thanks. If you change your comment to an answer, I will accept it.

– Jorr.it
Nov 22 '18 at 12:16












1 Answer
1






active

oldest

votes


















1














The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see https://github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.






share|improve this answer



















  • 1





    As an update: The recipe for JMSSerializerBundle 3 has been merged in the meantime (see github.com/symfony/recipes-contrib/pull/559).

    – xabbuh
    Nov 26 '18 at 12:15











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53429212%2fjmsserializerbundle-installation-ends-with-error-unrecognized-option-xml-unde%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









1














The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see https://github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.






share|improve this answer



















  • 1





    As an update: The recipe for JMSSerializerBundle 3 has been merged in the meantime (see github.com/symfony/recipes-contrib/pull/559).

    – xabbuh
    Nov 26 '18 at 12:15
















1














The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see https://github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.






share|improve this answer



















  • 1





    As an update: The recipe for JMSSerializerBundle 3 has been merged in the meantime (see github.com/symfony/recipes-contrib/pull/559).

    – xabbuh
    Nov 26 '18 at 12:15














1












1








1







The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see https://github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.






share|improve this answer













The current recipe is not compatible with JMSSerializerBundle 3 (there is a pending pull request, see https://github.com/symfony/recipes-contrib/pull/559). So for now, you need to adapt the configuration manually.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 22 '18 at 13:23









xabbuhxabbuh

4,501615




4,501615








  • 1





    As an update: The recipe for JMSSerializerBundle 3 has been merged in the meantime (see github.com/symfony/recipes-contrib/pull/559).

    – xabbuh
    Nov 26 '18 at 12:15














  • 1





    As an update: The recipe for JMSSerializerBundle 3 has been merged in the meantime (see github.com/symfony/recipes-contrib/pull/559).

    – xabbuh
    Nov 26 '18 at 12:15








1




1





As an update: The recipe for JMSSerializerBundle 3 has been merged in the meantime (see github.com/symfony/recipes-contrib/pull/559).

– xabbuh
Nov 26 '18 at 12:15





As an update: The recipe for JMSSerializerBundle 3 has been merged in the meantime (see github.com/symfony/recipes-contrib/pull/559).

– xabbuh
Nov 26 '18 at 12:15




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53429212%2fjmsserializerbundle-installation-ends-with-error-unrecognized-option-xml-unde%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

SQL update select statement

'app-layout' is not a known element: how to share Component with different Modules