The issue is that my package has dependencies listed in the require part of its composer.json file. Those dependencies are not present in the plugin's generated JSON.
The consequence is that I can't require my module in an other project without having to explicitly require all of its dependencies.
What feature or behavior is this required for?
Having private hosted packages.
How could we solve this issue? (Not knowing is okay!)
I think we just have to add the require part of the archive's composer.json file into the generated json.
composer archive --format=zipthencurl -v --user '...' --upload-file ...as documented here: https://github.com/sonatype-nexus-community/nexus-repository-composer/blob/master/docs/COMPOSER_USER_DOCUMENTATION.md#user-content-publishing-composer-packagesThe issue is that my package has dependencies listed in the
requirepart of itscomposer.jsonfile. Those dependencies are not present in the plugin's generated JSON. The consequence is that I can't require my module in an other project without having to explicitly require all of its dependencies.What feature or behavior is this required for? Having private hosted packages.
How could we solve this issue? (Not knowing is okay!) I think we just have to add the
requirepart of the archive'scomposer.jsonfile into the generated json.Anything else? Nope, thank you for your work !