maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christoph Läubrich (Jira) <j...@apache.org>
Subject [jira] [Updated] (MNG-6740) Provide a way to override properties of a polyglot build
Date Tue, 20 Aug 2019 10:35:00 GMT

     [ https://issues.apache.org/jira/browse/MNG-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christoph Läubrich updated MNG-6740:
------------------------------------
    Description: 
polyglot allows to generate maven models out of other metadata that pom.xml via extensions.

This is great and offers high flexibility for advanced use-cases but comes with the cost that
it is not as easy to modify certain settings or properties if the data is derived from other
sources.

For example [Eclipse Tycho|https://www.eclipse.org/tycho/] generates models out of OSGi/PDE
metadata but can often only guess what is the right thing to use for example as artifactId,
and it can't know of any custom properties a user might wish to set.

While it is always possible to create custom crafted poms, this contradicts the approach which
goal is to reuse as many metadata as possible, and the user only wants do configure a really
small portion of it (e.g. the description or a single poperty).

[A proposal was made to integrate support for this inside the tycho extension|https://bugs.eclipse.org/bugs/show_bug.cgi?id=550239],
but because it might be of wider use I'd like to evaluate (as suggestes by Mickael Istria)
if it is possible to implement/add this as a more generic feature directly into the maven
project.

  was:
polyglot allows to generate maven models out of other metadata that pom.xml via extensions.

This is great and offers high flexibility for advanced use-cases but comes with the cost that
it is not as easy to modify certain settings or properties if the data is derived from other
sources.

For example [Eclipse Tycho|http://example.com] generates models out of OSGi/PDE metadata but
can often only guess what is the right thing to use for example as artifactId, and it can't
know of any custom properties a user might wish to set.

While it is always possible to create custom crafted poms, this contradicts the approach which
goal is to reuse as many metadata as possible, and the user only wants do configure a really
small portion of it (e.g. the description or a single poperty).

[A proposal was made to integrate support for this inside the tycho extension|https://bugs.eclipse.org/bugs/show_bug.cgi?id=550239],
but because it might be of wider use I'd like to evaluate (as suggestes by Mickael Istria)
if it is possible to implement/add this as a more generic feature directly into the maven
project.


> Provide a way to override properties of a polyglot build
> --------------------------------------------------------
>
>                 Key: MNG-6740
>                 URL: https://issues.apache.org/jira/browse/MNG-6740
>             Project: Maven
>          Issue Type: New Feature
>            Reporter: Christoph Läubrich
>            Priority: Major
>
> polyglot allows to generate maven models out of other metadata that pom.xml via extensions.
> This is great and offers high flexibility for advanced use-cases but comes with the cost
that it is not as easy to modify certain settings or properties if the data is derived from
other sources.
> For example [Eclipse Tycho|https://www.eclipse.org/tycho/] generates models out of OSGi/PDE
metadata but can often only guess what is the right thing to use for example as artifactId,
and it can't know of any custom properties a user might wish to set.
> While it is always possible to create custom crafted poms, this contradicts the approach
which goal is to reuse as many metadata as possible, and the user only wants do configure
a really small portion of it (e.g. the description or a single poperty).
> [A proposal was made to integrate support for this inside the tycho extension|https://bugs.eclipse.org/bugs/show_bug.cgi?id=550239],
but because it might be of wider use I'd like to evaluate (as suggestes by Mickael Istria)
if it is possible to implement/add this as a more generic feature directly into the maven
project.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message