You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Robert Scholte <rf...@apache.org> on 2021/08/31 20:50:34 UTC

Maven Extension Configuration

Hi,

I see quite some Maven extensions that rely on configuration.
There's no convention for this, so they all pick their own format and 
location.
Looking at the build-cache it seems there's again configuration 
required.

I think with Maven 4 we should make it possible to add a 
configuration-block to an extension, similar to plugins.
The difficult part is how to make Components (@Named/@Inject) get access 
to this configuration.
I don't think we can pass if with some method of an API.
For that reason probably the Configuration itself should be a Component 
too and Maven (with Sisu) is responsible for mapping and injecting it.
Important benefit is that we'll have type-safe configuration.

I hope others like this idea as well.
Is it worth investigating or do we already see blockers?

In case of enough positive responses I'll prepare a wiki page for the 
details.

thanks,
Robert

Re: Maven Extension Configuration

Posted by Romain Manni-Bucau <rm...@gmail.com>.
Sounds reasonable, probably like mojo, with properties override so maybe
@Param support too or so.

Le mar. 31 août 2021 à 23:21, Falko Modler <f....@gmx.net> a écrit :

> Hi Robert,
>
> this is basically https://issues.apache.org/jira/browse/MNG-5897, no?
>
> I left a few thouhts there a while ago.
>
> Cheers,
>
> Falko
>
> Am 31.08.2021 um 22:50 schrieb Robert Scholte:
> > Hi,
> >
> > I see quite some Maven extensions that rely on configuration.
> > There's no convention for this, so they all pick their own format and
> > location.
> > Looking at the build-cache it seems there's again configuration required.
> >
> > I think with Maven 4 we should make it possible to add a
> > configuration-block to an extension, similar to plugins.
> > The difficult part is how to make Components (@Named/@Inject) get
> > access to this configuration.
> > I don't think we can pass if with some method of an API.
> > For that reason probably the Configuration itself should be a
> > Component too and Maven (with Sisu) is responsible for mapping and
> > injecting it.
> > Important benefit is that we'll have type-safe configuration.
> >
> > I hope others like this idea as well.
> > Is it worth investigating or do we already see blockers?
> >
> > In case of enough positive responses I'll prepare a wiki page for the
> > details.
> >
> > thanks,
> > Robert
> >
> >
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: Maven Extension Configuration

Posted by Robert Scholte <rf...@apache.org>.
Yes it is, Karl Heinz beat me already in 2015!

------ Origineel bericht ------
Van: "Falko Modler" <f....@gmx.net>
Aan: dev@maven.apache.org
Verzonden: 31-8-2021 23:21:33
Onderwerp: Re: Maven Extension Configuration

>Hi Robert,
>
>this is basically https://issues.apache.org/jira/browse/MNG-5897, no?
>
>I left a few thouhts there a while ago.
>
>Cheers,
>
>Falko
>
>Am 31.08.2021 um 22:50 schrieb Robert Scholte:
>>Hi,
>>
>>I see quite some Maven extensions that rely on configuration.
>>There's no convention for this, so they all pick their own format and
>>location.
>>Looking at the build-cache it seems there's again configuration required.
>>
>>I think with Maven 4 we should make it possible to add a
>>configuration-block to an extension, similar to plugins.
>>The difficult part is how to make Components (@Named/@Inject) get
>>access to this configuration.
>>I don't think we can pass if with some method of an API.
>>For that reason probably the Configuration itself should be a
>>Component too and Maven (with Sisu) is responsible for mapping and
>>injecting it.
>>Important benefit is that we'll have type-safe configuration.
>>
>>I hope others like this idea as well.
>>Is it worth investigating or do we already see blockers?
>>
>>In case of enough positive responses I'll prepare a wiki page for the
>>details.
>>
>>thanks,
>>Robert
>>
>>
>>
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: Maven Extension Configuration

Posted by Falko Modler <f....@gmx.net>.
Hi Robert,

this is basically https://issues.apache.org/jira/browse/MNG-5897, no?

I left a few thouhts there a while ago.

Cheers,

Falko

Am 31.08.2021 um 22:50 schrieb Robert Scholte:
> Hi,
>
> I see quite some Maven extensions that rely on configuration.
> There's no convention for this, so they all pick their own format and
> location.
> Looking at the build-cache it seems there's again configuration required.
>
> I think with Maven 4 we should make it possible to add a
> configuration-block to an extension, similar to plugins.
> The difficult part is how to make Components (@Named/@Inject) get
> access to this configuration.
> I don't think we can pass if with some method of an API.
> For that reason probably the Configuration itself should be a
> Component too and Maven (with Sisu) is responsible for mapping and
> injecting it.
> Important benefit is that we'll have type-safe configuration.
>
> I hope others like this idea as well.
> Is it worth investigating or do we already see blockers?
>
> In case of enough positive responses I'll prepare a wiki page for the
> details.
>
> thanks,
> Robert
>
>
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org