[
https://issues.apache.org/jira/browse/MNG-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6748:
--------------------------------
Description:
It would be nice to be able to pass properties from an aggregate pom to module
poms during a build.
Example: A project with 2 modules with different parent poms from the aggregate
and want to share a version of a common dependency. The dependency is not
available from the parent perspective. Each module would have to have a full
GAV for a dependency, but could share the version so they will match.
Proposed Solution: Any property given in the aggregate pom would be available
(and overwrite matching child module properties) to the child modules during
build process.
Another
[example|https://stackoverflow.com/questions/52379013/how-to-set-environment-variable-in-maven-aggregator-without-inheritance-to-be-re]
with similar expectations.
was:
It would be nice to be able to pass properties from an aggregate pom to module
poms during a build.
Example: A project with 2 modules with different parent poms from the aggregate
and want to share a version of a common dependency. The dependency is not
available from the parent perspective. Each module would have to have a full
GAV for a dependency, but could share the version so they will match.
Proposed Solution: Any property given in the aggregate pom would be available
(and overwrite matching child module properties) to the child modules during
build process.
Another
[example|[https://stackoverflow.com/questions/52379013/how-to-set-environment-variable-in-maven-aggregator-without-inheritance-to-be-re]]
with similar expectations.
> Aggregate pom to set properties for all modules
> -----------------------------------------------
>
> Key: MNG-6748
> URL: https://issues.apache.org/jira/browse/MNG-6748
> Project: Maven
> Issue Type: New Feature
> Reporter: Allyn Tobey
> Priority: Major
>
> It would be nice to be able to pass properties from an aggregate pom to
> module poms during a build.
> Example: A project with 2 modules with different parent poms from the
> aggregate and want to share a version of a common dependency. The dependency
> is not available from the parent perspective. Each module would have to have
> a full GAV for a dependency, but could share the version so they will match.
>
> Proposed Solution: Any property given in the aggregate pom would be available
> (and overwrite matching child module properties) to the child modules during
> build process.
>
> Another
> [example|https://stackoverflow.com/questions/52379013/how-to-set-environment-variable-in-maven-aggregator-without-inheritance-to-be-re]
> with similar expectations.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
