[
https://issues.apache.org/jira/browse/IGNITE-25901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-25901:
------------------------------------
Description:
ignite-codegen2 module is compileOnly, but Maven doesn't support such scope.
The module currently is in compile scope, but it leads that all apps are
dependent on ignite-core now depends on ignite-codegen2. But we don't even
publish the module.
The reason for compile was to provide better UX for Ignite developers with
Intellij IDEA. Developers usually fetch git branch and just run tests. But IDEA
doesn't automatically compile "provided" dependencies. And developer should
build the project with maven first.
Unfortunately, there is no way to enforce IDEA automatically compile the module
and in the same time skip it in a pom file.
Let's make the dependency provided then.
> External modules should not depend on ignite-codegen2
> -----------------------------------------------------
>
> Key: IGNITE-25901
> URL: https://issues.apache.org/jira/browse/IGNITE-25901
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
>
> ignite-codegen2 module is compileOnly, but Maven doesn't support such scope.
> The module currently is in compile scope, but it leads that all apps are
> dependent on ignite-core now depends on ignite-codegen2. But we don't even
> publish the module.
> The reason for compile was to provide better UX for Ignite developers with
> Intellij IDEA. Developers usually fetch git branch and just run tests. But
> IDEA doesn't automatically compile "provided" dependencies. And developer
> should build the project with maven first.
> Unfortunately, there is no way to enforce IDEA automatically compile the
> module and in the same time skip it in a pom file.
> Let's make the dependency provided then.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
