James

Waiting for investigation to see if it is possible to build a fallback cppstd compatible configuration instead of failing if the current profile is not a valid one.

Closing as deprecated/superseded by https://github.com/conan-io/conan/pull/16871

Hi @hlewin Thanks for your question. This would be mostly intended behavior. The ``VirtualBuildEnv`` and ``tool-requires`` are a "build-time" thing, while the ``deploy`` is a pure runtime thing, independent of...

> The possible workaround is a "forwarder" package with no content Sounds it could be possible. It would be good to understand a bit more the full picture: - Are...

That makes sense thanks for the clarification. I am going to check a little bit and experiment to see if there is some possible solution in Conan 2. Just to...

I have made this test pass in Conan 2. ```python def test_deploy_method_tool_requires(): c = TestClient() tool = textwrap.dedent(r""" import os from conan import ConanFile from conan.tools.files import save, chdir class...

> That having said I would still welcome a remark in the documentation that VirtualBuildEnv might not contain settings from tool-requirements that were skipped because they weren't needed for the...

This command seems to work (from @czoido from extensions repo) ``` docker run --name artifactory -d -e JF_SHARED_DATABASE_TYPE=derby -e JF_SHARED_DATABASE_ALLOWNONPOSTGRESQL=true -p 8081:8081 -p 8082:8082 releases-docker.jfrog.io/jfrog/artifactory-pro:latest ```

Closed by https://github.com/conan-io/docs/pull/3993 and , also in web

Hi @mikirothman Sorry this was not responded back then. > we will still get the defaults for the cpp_info.bindirs / cpp_info.libdirs / cpp_info.includedirs, I think when a component is being...