Howdy,
Did anyone look at or maybe even tried MDK?
Thanks
T
On Mon, May 6, 2024 at 4:36 PM Tamás Cservenák wrote:
> Howdy,
>
> Please take a peek at (and maybe try out) latest Maveniverse project, MDK:
>
> https://github.com/maveniverse/mdk
>
> This is like "proof of concept" or "demo" of what
Well not sure what you didn't get from my mails but
1. I agree current solution does not need anything new if it was ambiguous
2. the mail you reference was for jreleaser outside maven so out of topic
there IMHO
If MDK does not need an external SPI I agree with you there is no new
concept nor nee
>
>
> Well, for *existing* core component I don't see an issue to add a toggle to
> say "deploy at end".
> What can be an issue there is only to make it global for the session and
> not per artifact + how to define "end" - agree onSessionClose can be too
> late but sure we can find a good "phase" (
Well, for *existing* core component I don't see an issue to add a toggle to
say "deploy at end".
What can be an issue there is only to make it global for the session and
not per artifact + how to define "end" - agree onSessionClose can be too
late but sure we can find a good "phase" (plain english
And few more things:
- my intent is to target BOTH, Maven3 and Maven4, as when Sonatype
deprecates OSS/S01 in favor of Central Portal, Maven3 (and currently also
Maven4) users are doomed to "roll their own" solutions for Central
publishing. While Sonatype Nx2 (running on Sonatype OSS/S01 and ASF re
>
>
> If you don't need to create a new module nor any new interface in maven
> core or a shared module I'm all for the change, otherwise it is a new
> shared thing whatever you present it.
>
So, if we don't change anything, you accept the "change"? :)
In short: MDK is just a "tech demo", but the
Le lun. 6 mai 2024 à 19:40, Tamás Cservenák a écrit :
> Howdy,
>
> inline.
>
>
> Exactly...this is what will always happen with plugins and extensions.
> > Indeed you can add a phase after plugins then you moved the issue to one
> > more step but the issue is still *exactly* the same but in a new
Howdy,
inline.
Exactly...this is what will always happen with plugins and extensions.
> Indeed you can add a phase after plugins then you moved the issue to one
> more step but the issue is still *exactly* the same but in a new concept
> and layer, so literally no gain there.
>
This is not a ne
Le lun. 6 mai 2024 à 18:55, Tamás Cservenák a écrit :
> Romain,
>
> I have more and more the feeling that you are not reading what has been
> written down, at least not carefully enough.
>
> Otherwise, you';d know that is it NOT "already doable", as explained in MDK
> doco (but also in previous t
Romain,
I have more and more the feeling that you are not reading what has been
written down, at least not carefully enough.
Otherwise, you';d know that is it NOT "already doable", as explained in MDK
doco (but also in previous thread):
Just one example: the current "deploy at end" feature of m-d
Hi Tamas
So it is just a spi consommable from a plugin using an extension to share a
state accross mojo execution...so nothing we already do.
My understanding of your request is to bring to maven 4 api this concept
for common needs (delayed tasks I'd say more than anything specific to
deployment)
Howdy,
Please take a peek at (and maybe try out) latest Maveniverse project, MDK:
https://github.com/maveniverse/mdk
This is like "proof of concept" or "demo" of what the Plugin SPI pattern
would be able to do.
The idea is to broaden the support, and provide services even like
"overlaid staging
12 matches
Mail list logo
