+1, thanks
(small request: can the title "Drop plugin cruft" be rewritten to describe
the issue in the changelog on jira?)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordp
you ask but you know it is gradle right ([1])? ;)
It is the risk to drive the build descriptors by code, you can get
conflicts using conventions not validating themselves in the build script.
[1] https://github.com/openjdk/jfx/blob/master/build.gradle#L1674
Romain Manni-Bucau
@rmannibucau
nature of maven so think we are good like that
and it is saner to enable this kind of update than requiring them to create
a ton of version branches which will never be maintained so it is a good
trade off IMHO.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
sh the tag on a personal (pmc) github fork
and only after the vote push it upstream to be able to drop it without any
impact for rerolls.
+1 for this one (no regression on tested projects) but hope it is the last
"burn"
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rman
Hi Guillaume,
Why isnt it beta1 - I know but we shouldn't burn version even in
alpha/beta, every time it makes noise we can't justify technically :(?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Ol
+1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
+1
Le mar. 21 mai 2024 à 19:40, Manfred Moser a
écrit :
> Looks good!
>
> +1
>
> On 2024-05-21 8:17 a.m., Tamás Cservenák wrote:
> > Howdy,
> >
> > We solved 6 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12354608
> >
> > There are still a couple of
+1, tested on a few projects (mvn 4 + java 17)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.
1 or 2 (there are iso from an user perspective imho even if help plugins
looks natural)
Rather not 3 for me by design and to keep it light
Maybe 5: external self contained tool (always better to check a soft cause
if tool cant run your tool is useless: here if mvn doesnt run you cant
check
need of any maven thread since we don't change anything ;)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn &
try to use one of the existing
solutions maybe before moving to building a new maven - or discuss
rebuilding maven from scratch if that is the ultimate intent, if we break
the compat rule a lot of things can change and concepts can be
simplified+refined but AFAIK we are not in this mood, are we?
Romain M
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
n data)
So there is not yet any describe use case requiring a new concept in maven
AFAIK.
>
>
> Thanks
> T
>
>
>
> On Mon, May 6, 2024 at 5:56 PM Romain Manni-Bucau
> wrote:
>
> > Hi Tamas
> >
> > So it is just a spi consommable from a plugin usi
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
ying we cannot keep SPI along with Plugins, I am just
> > saying
> > > > > that
> > > > > > it's pointless: we will have many releases of the same thing.
> > > > > >
> > > > > > On Mon, May 6, 2024 at 2:31 PM Guillaume Nodet
covered for all cases
already.
If you want an auto-discovered case you don't cover the case you describe,
ie enable/disable deployAtEnd so I still don't see any issue for now.
>
> T
>
> T
>
> On Mon, May 6, 2024 at 3:52 PM Romain Manni-Bucau
> wrote:
>
> >
> >
.
I don't see a case in between since user is not able to consume it.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibuc
Tamas, the extension can inject the configuration which is instantiated
when the mojo will be executed.
At startup it does not need to be there, so there is no issue there while
you resolve the plugin dependency you inject from the extension in
afterModelRead normally.
Romain Manni-Bucau
end users - to redo an extension
concurrent for other needs than the previous one
So ultimately I think this is not an issue we need to address even if any
use case can get multiple solutions, a single one is often the best
compromise for everyone.
Romain Manni-Bucau
@rmannibucau <https://twitter.co
- exactly like shade plugin references its
transformers to be concrete.
So for me nothing to create nor modify to get an old feature.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpres
and make it maven 3 friendly automatically (can be a x-maven-plugin
downloading x-v3 or x-v4 subartifact for the runtime, not sexy internally
but very smooth in terms of usage).
Best,
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/>
+1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
gt; > Cheers,
> > > Andres
> > >
> > > ---
> > > Java Champion; Groovy Enthusiast
> > > https://andresalmiray.com
> > > https://www.linkedin.com/in/aalmiray
> > > --
> > > What goes
us making it obvious it will fail but
I think it will be fixed for the final GA release.
So from my small window there is no concern even if most of us using
central outside the asf will be impacted sometime next year probably.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibu
+1
Le lun. 22 avr. 2024 à 05:30, Olivier Lamy a écrit :
> +1
>
> On Sun, 21 Apr 2024 at 01:54, Hervé Boutemy wrote:
> >
> > Hi,
> >
> > We solved 3 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12354342=Text
> >
> > Staging repo:
> >
+1
Le mer. 17 avr. 2024 à 12:28, Tamás Cservenák a
écrit :
> +1
>
> [INFO] Reference build java.version: 21 (from MANIFEST.MF Build-Jdk-Spec)
> [INFO] Reference build os.name: Unix (from pom.properties newline)
> [INFO] Minimal buildinfo generated from downloaded artifacts:
>
>
+1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
and artifact
plugin is considered not a core plugin - not sure of the status today)?
I'm happy both ways but I'm way less happy with a broken setup if we
consider it is supported by maven.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.me
can be done I think.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibuca
Hi
For me it is:
* Tree: human work on transitivity
* List: pre-resolve for the runtime (dump jar list in a file)
* Resolve: CI init phase
Le jeu. 21 mars 2024 à 17:54, Christian Stein a écrit :
> I use the "resolve" goal like this:
>
> mvn --batch-mode --no-transfer-progress
properly the
command before it is executed (as of today).
+1 to not "preparePaths" and just let the compilation be native.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordp
Hi Hervé,
Think we can try to just move forward the v4 effort and if there are enough
requests on v3 we would maintain it as a best effort but as it had been
mentionned there is no more any real reason to do both as soon as maven v4
is officially out - ie final - IMHO.
Romain Manni-Bucau
+1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
Think site got slowly replaced by other alternatives - even to document
mojos! - so today it is mainly about us and I also dont think limiting
doxia 2 to maven 4 has much issues, there is no real request from outside
for it AFAIK.
>From a versioning standpoint I see really no reason to make a
+1 without any strong opinion on doxia 2 for maven 3 in the future (no
blocker IMHO but not the baseline too)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github &
.$pluginMajor.$minor.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in
+1
(side note for future releases: we can move to milestone versioning more
than alpha since we are not alpha at all it seems, are we?)
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibuca
Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.pac
Hi Tamas,
Not sure I really got the issue, is it to do a breaking change without a
maven-core bump?
I tend to agree with you, ie the versioning is
$mavenCoreMajor.$pluginMajor.$pluginMinor and no patch digit and guess it
works good enough even for users, no?
Best,
Romain Manni-Bucau
Le lun. 4 mars 2024 à 10:49, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Note: this logging issue is not very important. If there is such
> resistance against it, I will not insist.
>
>
> Le 2024-03-04 à 08 h 35, Romain Manni-Bucau a écrit :
>
>
nd there System.Logger fills another gap the JVM had and
was using System.out before as explained in the first responses.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> |
Le dim. 3 mars 2024 à 22:28, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-03-03 à 20 h 38, Romain Manni-Bucau a écrit :
>
> > the idea of maven-api was to abstract anything from the implementation
> > to be able to change
> A standar
Le dim. 3 mars 2024 à 19:18, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-03-03 à 18 h 48, Romain Manni-Bucau a écrit :
>
> >> (snip) Nothing force us to use System.getLogger() for getting an
> >> instance of that interface. (s
Le dim. 3 mars 2024 à 17:50, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Hello Romain
>
> Le 2024-03-03 à 17 h 02, Romain Manni-Bucau a écrit :
>
> > SystemLogger has the ServiceLoader "pick random first" implementation
>
ur mail right and didn't interpret the multiple points I
understood.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <
+1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
Hi Hervé
Im not sure why there is this belief toolchain improvement is needed, this
is NOT needed and CI already bypass it so for me this is not an enabler,
more a blocker IRL.
Let's improve plugins if they dont enable executable/env config but
toolchain is just a part of the execution of so
ntinuing such discussion in circles brings
> anything good - so be it.
>
>
>
> >
> >
> > Aleksandar Kurtakov 于2024年2月28日周三 01:15写道：
> >
> > > On Tue, Feb 27, 2024 at 6:13 PM Romain Manni-Bucau <
> > rmannibu...@gmail.com>
> > > wrote:
> > >
Not sure we'll converge guys but shouldnt we make a vote? Seems we all
understand the impacts technically so maybe time to decide else we'll still
be there in a year.
Le mar. 27 févr. 2024 à 16:41, John Neffenger a écrit :
> On 2/26/24 11:42 AM, Basil Crow wrote:
> > We had a similar
way to
converge anytime - nor the need to be honest.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://w
Le ven. 23 févr. 2024 à 13:44, Elliotte Rusty Harold a
écrit :
> On Fri, Feb 23, 2024 at 12:23 PM Romain Manni-Bucau
> wrote:
> >
> > @Elliotte while you are pretty right in terms of *compile* features but
> it
> > ignores the biggest criteria for any ASF pr
will start to
"pf" ;)).
So most of the challenge here is to stay an active community and not a
dying one and using recent enough JDK is a good way to encourage it IMHO.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.me
rs, period.
If not then we should refine the prerequisites to run maven.
Side note: this let us free to use java ea if we want on our CI and for
releases, we just have to ensure we run on the minimum supported versions
tests - without compilation to have some harnessing.
Romain Manni-Bucau
@rmannibu
esis is wrong please close this thread and
start a new about this minimalistic feature, if we want to drop that we go
in the distro erea, drop plugins support but decision is not taken on the
same points at all - we woud likely dont care of the java version we would
go that path.
Romain Manni-Bucau
version in
stone.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau>
Hmm, not sure im ready for a 200M vanilla build tool even if it would have
been ok legally...
Le mer. 21 févr. 2024 à 21:41, Hunter C Payne
a écrit :
> I might be wrong but I understood that shipping the JRE/JVM required a
> license and this is why most people don't ship with a JVM bundled.
n.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#executable
.
> ____
> From: Romain Manni-Bucau
> Sent: Wednesday, February 21, 2024 3:48:43 PM
> To: Maven Developers List
> Subject: Re: [DISCUSS] Java version for Maven
>
> Hi H
ssion)
>
Sure, my point was not to create a debate on that now, just that we should
probably not see toolchain as a solution cause it hurts more it helps.
>
> Le mercredi 21 février 2024, 08:48:43 CET Romain Manni-Bucau a écrit :
> > Hi Hervé,
> >
> > +1000 on the ph
well.
So overall I think we could drop toolchain which ultimately still misses a
few parts to be complete in terms of env setup and make a shared-executable
stronger - likely the future base of exec plugin even if not required.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibu
aEE just pushed back from 21 to 17
as a requirement due to the pressure from the communityand at ASF we
don't really care about code at the end ;).
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://r
S
- indeed with best effort on later versions but no guarantee upfront.
With such a policy calendar can be communicated and people can follow or
not without surprises.
So today, since we don't have yet a final I think 21 can make sense but not
cause it is the current latest, cause it will likely be t
Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.pac
+1, project ok, downstream projects ok, tested on mvn 3.9.2 & java 11
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmann
Rather -0 on my side by experience cause this kind of tool is often abused,
in particular using an IoC or a codebase with indirections like maven. One
prerequisite being all the stack uses it - plexus, sisu, commons etc - Im
not sure we can get the benefits without the downsides.
That said you
Le mar. 6 févr. 2024 à 16:12, Hunter C Payne
a écrit :
> There are also license differences between Java 8 and Java 9+. And the
> improvements beyond 8 are not things the market seems to want. Nobody
> wants Jigsaw and the API improvements aren't enough to get people to
> upgrade. Those that
and
broken by design but is the current state of the art.
However even google-http-java-client moved to java 21 so your example kind
of confirms the coming outcome of this thread IMHO rather than trying to
oppose to it so I'm not sure what's the point is.
Romain Manni-Bucau
@rmannibucau <https://twitter.
more than companies.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibu
Side note: dont think toolchain enhancements is a requirement at all, lot
of users keep rejecting this additional work (and to be honest I can agree
1nd it does not help more things than using properties to switch the
env/executable in plugins) so only question for me is the baseline and
minimum
+1
Le lun. 29 janv. 2024 à 23:41, Sylwester Lachiewicz
a écrit :
> +1
>
> pon., 29 sty 2024 o 20:37 Benjamin Marwell
> napisał(a):
>
> > Hi,
> >
> > We solved 6 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321432=12349496
> >
> > There are still two
+1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
;).
Best,
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Bo
Le lun. 22 janv. 2024 à 13:34, Benjamin Marwell a
écrit :
> To add some more information, I have seen some extreme reduction in
> build times after switching from Java 11 to 17 or even 21 (just for
> build, not the runtime).
> We can still verify it runs on 11/17 by using the integration tests,
Same there while surefire/invoker runs respect supported versions.
Le dim. 21 janv. 2024 à 22:04, Guillaume Nodet a écrit :
> At build time, I think it's fine to bump to whatever is needed to make
> our life manageable. If 17 is required, so be it.
>
> Guillaume
>
> Le sam. 20 janv. 2024 à
+1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> |
Afaik the ci is up to date so must pass so likely needs a fix.
Le sam. 13 janv. 2024 à 14:43, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Just saw that the CI build has been successful on Java 17 and 21, but
> failed on Java 11 because of the use of the |{@return ...}|
by some other ASF projects with success so can be
worth a try).
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn &
Hi Guillaume,
Is it possible to not burn versions, it is always misleading for end users
so would be great to get the alpha 11 out maybe?
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibuca
,
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<htt
(thought I sent my vote yesterday but somehow the thread does not list it
so resending, please ignore if a gmail issue) +1
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com&g
type names before making it live,
the legacy ones arelegacy but new ones can need an agreement but that's
a very small detail.
Best,
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordp
Le mar. 9 janv. 2024 à 08:03, Michael Osipov a écrit :
> Am 2024-01-08 um 09:14 schrieb Slawomir Jaranowski:
> > +1
> >
> > We should maintain GitHub releases notes, last is for 3.2.2
> > Now we have outdated info which can be confusing for users.
> > So we should be consistent - if we have one
+1
Le dim. 7 janv. 2024 à 18:30, Sylwester Lachiewicz
a écrit :
> +1
>
> niedz., 7 sty 2024, 18:07 użytkownik Tamás Cservenák
> napisał:
>
> > +1
> >
> > On Sat, Jan 6, 2024 at 9:05 PM Michael Osipov
> wrote:
> >
> > > Hi,
> > >
> > > we solved 7 issues:
> > >
> > >
> >
>
any message, if you feel motivated to send a pr it
would be welcomed I guess.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibuc
other way around
so from a theorical standpoint classpath has still a wider area - not
saying it is better to always start with classpath though, don't
overinterpret please.
But anyway we can move forward we don't have to agree on that
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannib
Le jeu. 4 janv. 2024 à 16:21, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-04 à 15 h 56, Romain Manni-Bucau a écrit :
>
> > Well it was written that the artifact names were not JPMS compatible,
> > you can review https://github.c
consider
that path as something relevant today.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.
Le jeu. 4 janv. 2024 à 13:05, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-04 à 12 h 49, Romain Manni-Bucau a écrit :
>
> > Just take the previous example you even explained yourself with an
> > invalid JPMS name, this is still a vali
line you will need an aggregator pom and I'm not sure how well it will
sit in a packaging=pom pom defining it for children.
>
>
>
>
> Am 04.01.24 um 11:32 schrieb Romain Manni-Bucau:
> > Le jeu. 4 janv. 2024 à 10:37, Christoph Läubrich a
> > écrit :
> >
> >
Le jeu. 4 janv. 2024 à 11:42, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-04 à 11 h 31, Romain Manni-Bucau a écrit :
>
> >> No, optional dependencies in JPMS are handled by "static requires".
> >>
> > As explained in
; Plugins can have a default phase that is chosen if not specified, still
> a lifecycle mapping would require that as well, so lifeycle mapping (as
> xml component xml) is just a little bit different syntax then?
>
You can get a phase if it exists, not sure if you make it empty - was my
point
&
Le jeu. 4 janv. 2024 à 10:54, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-04 à 10 h 27, Romain Manni-Bucau a écrit :
>
> > You also explained this is not true since you cannot compile part of
> > the code linked to optional d
still need to associate phase(s) to each plugin to be able to
run "mvn compile" "mvn test" or alike until we have an alias notion in
pom/extensions.xml (= say "mvn foo" means run these plugins but it is the
lifecycle somehow).
>
>
> Am 04.01.24 um 09:37 schrieb Rom
Le jeu. 4 janv. 2024 à 10:20, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-04 à 09 h 21, Romain Manni-Bucau a écrit :
>
> > Please just stip thinking jpms first, think classpath first with jpms
> > compat, changes the whole perspective. If
valuate the mappings but looks doable.
High level it is more or less "let the pom/.mvn inject maven components
without coding/by declaration".
Hope it makes sense, let me know if it is worth investigating more or if
the idea is too particular to my old needs.
Best,
Romain Manni-Bucau
@rm
Le jeu. 4 janv. 2024 à 01:23, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-03 à 21 h 31, Romain Manni-Bucau a écrit :
>
> >> Can you compile this test case with the dependency on the class-path,
> >> without omitting the
Le mer. 3 janv. 2024 à 19:25, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-03 à 17 h 15, Romain Manni-Bucau a écrit :
>
> > see it as "where classpath is in core comes from the time maven was
> > only for java libs" (i'd say
Le mer. 3 janv. 2024 à 17:03, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-03 à 16 h 45, Romain Manni-Bucau a écrit :
> > maven4 introduces the notion of "services" (...snip...) So guess all
> > is there to do it and core can s
Le mer. 3 janv. 2024 à 16:11, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-03 à 15 h 19, Romain Manni-Bucau a écrit :
>
> > I can agree with that so let's move it in a plugin related code maybe?
> >
> The call is on core Maven devel
Le mer. 3 janv. 2024 à 14:45, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-03 à 12 h 08, Romain Manni-Bucau a écrit :
> >> I would like to see a proof in the form of an "hello world"
> >> application (…snip…)
> >
>
Le mer. 3 janv. 2024 à 11:50, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2024-01-03 à 09 h 08, Romain Manni-Bucau a écrit :
>
> > (…snip…) just to answer trivially to "But if an artifact is included,
> > it should (at least by default)
1 - 100 of 977 matches
Mail list logo
