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.

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

Plugin is not active #7

Closed
soufea opened this issue May 3, 2024 · 2 comments
Closed

Plugin is not active #7

soufea opened this issue May 3, 2024 · 2 comments

Comments

@soufea
Copy link

soufea commented May 3, 2024

Hello,

Thanks for the reply and great to hear you are planning to maintain this further !

I am moving the discussion here from this issue.

Here is a minimal example to reproduce. Basically, doing an export or build in folder B doesn't change anything, no errors.

Structure

── pyproject.toml
└── repo
    ├── A
    │   └── pyproject.toml
    └── B
        ├── poetry.lock
        ├── pyproject.toml
        └── reqs.txt

root pyproject.toml

[tool.poetry]
name = "repo"
version = "0.1.0"
description = ""
authors = [""]
readme = ""

[tool.poetry.dependencies]
python = "^3.8"

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

project A pyproject.toml

[tool.poetry]
name = "lib-a"
version = "0.1.0"
description = ""
readme = "README.md"
authors = ["Soufiane EL ALAMI <soufiane.elalami@outlook.fr>"]

[tool.poetry.dependencies]
python = "^3.8"

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

project B pyproject.toml

# repo/B/pyproject.toml
[tool.poetry]
name = "app-B"
version = "0.1.0"
description = ""
readme = "README.md"
authors = ["Soufiane EL ALAMI <soufiane.elalami@outlook.fr>"]

[tool.poetry.dependencies]
python = "^3.8"
lib-a = {path = "../A", develop=true}

[tool.poetry-monorepo.deps]
enabled = true

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

I hope this is useful :)

@gerbenoostra
Copy link
Owner

Hi. Firstly sorry for the late reply, apparently I'm not yet getting email notifications on new issues.

Running poetry build from repo/B is expected to invoke the plugin, so thanks for reporting.

To diagnose the issue, let's verify a few things first:

  1. Could you ensure that the plugin is installed for the poetry you're invoking:
poetry self show plugins
  1. get more debug output:
poetry build -vvv

The first few lines should be similar to:

Loading configuration file ...
Using virtualenv: ...
Replacing path dependencies with named dependencies.
Building project_name (1.2.3)
  - Building sdist

@gerbenoostra
Copy link
Owner

Can't reproduce without more diagnostics

@gerbenoostra gerbenoostra closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants