On Mon 6 Jul 2020 at 17:48, Hervé BOUTEMY wrote:
> Le lundi 6 juillet 2020, 11:33:05 CEST Mark Derricutt a écrit :
> > Hervé,
> >
> > If you configure IntelliJ (projecting much Mark?) to use Maven
> > 3.7.0-SNAPSHOT as it’s maven version, does that work?
> keeping internal Maven version was givin
Le lundi 6 juillet 2020, 11:33:05 CEST Mark Derricutt a écrit :
> Hervé,
>
> If you configure IntelliJ (projecting much Mark?) to use Maven
> 3.7.0-SNAPSHOT as it’s maven version, does that work?
keeping internal Maven version was giving an impression of working, probably
due to cache given updat
Hervé,
If you configure IntelliJ (projecting much Mark?) to use Maven
3.7.0-SNAPSHOT as it’s maven version, does that work?
I tend to configure my IJ to use my built SNAPSHOT when testing out Maven
releases.
Mark
On 6 July 2020 at 8:21:57 PM, Hervé BOUTEMY (herve.bout...@free.fr) wrote:
What i
I just created a "buildconsumer" branch in Doxia [1] to have a live example of
the new simplified build POM that Maven 3.7.0 will allow [2]
As expected, this branch can't build with Maven 3.6.3, but can with Maven
3.7.0-SNAPSHOT.
And in my favorite IDE, as expected, dependency resolution does no
(I’m unable to currently use 3.0.0-M1 for the same reason either).
>
> Hrm.
> Mark
>
>
> From: Jaroslav Tulach
>
> Reply: Maven Developers List
> Date: 4 July 2020 at 5:35:37 PM
> To: dev
> Cc: dev@maven.apache.org ,
> us...@maven.apache.org ,
> m2e-...@eclipse.o
nteresting.
> > I am not aware of that issue. Is there already a JIRA ticket for it,
> > because this must be solved before the next release.
> >
> >
> > (I’m unable to currently use 3.0.0-M1 for the same reason either).
> >
> > Hrm.
> > Mark
&g
elease.
>
>
> (I’m unable to currently use 3.0.0-M1 for the same reason either).
>
> Hrm.
> Mark
>
>
> From: Jaroslav Tulach
>
> Reply: Maven Developers List
> Date: 4 July 2020 at 5:35:37 PM
> To: dev
> Cc: dev@maven.apache.org ,
> us...@maven.apa
Robert Scholte:
There is a feature toggle, see
https://github.com/apache/maven/blob/master/maven-model-builder/src/main/java/org/apache/maven/feature/Features.java#L34
Awesome - I’ll get that a play and report back.
Does this mean that the install:install did work?
That would be interesting.
I
ven Developers List
Date: 4 July 2020 at 5:35:37 PM
To: dev
Cc: dev@maven.apache.org ,
us...@maven.apache.org ,
m2e-...@eclipse.org ,
openc...@microsoft.com
Subject: Re: Maven moving to the next level: the build/consumer pom
Hello Robert,
I am not sure how to deal with your announcement and given no react
Hello Jaroslav,
I might have missed the message on the dev@netbeans mailinglist. Based on the
responses in ponymail[1] I think I've answered them all (I don't know which one
came from netbeans).
I haven't tried it with any IDE, my main goal is that Maven itself keeps
working as expected and I'v
m2e-...@eclipse.org ,
openc...@microsoft.com
Subject: Re: Maven moving to the next level: the build/consumer pom
Hello Robert,
I am not sure how to deal with your announcement and given no reaction on
the dev@netbeans mailing list, I am probably not alone. Can you formulate
Hello Robert,
I am not sure how to deal with your announcement and given no reaction on
the dev@netbeans mailing list, I am probably not alone. Can you formulate
your issue as a bug report? E.g. have you tried to use your new Maven with
NetBeans and did you face a problem? Having steps to reproduce
On 25-6-2020 02:03:42, Anton Vodonosov wrote:
Can this work also allow arbitrary property expression in a module ?
Robert Scholte:
Currently only the ci-friendly version placeholders are supported.
Currently, this practice is discouraged because the deployed pom with property
expression is mean
On 23-6-2020 23:20:31, Matthieu BROUILLARD wrote:
Hi Robert,
congrats this looks like a great achievement.
I presume that the consumer pom means the end of the flatten plugin or is
there still some benefit in using flatten plugin?
Robert Scholte:
The flatten-maven-plugin was introduced when the
Can this work also allow arbitrary property expression in a module ?
Currently, this practice is discouraged because the deployed pom with property
expression is meaningless.
The flatten-maven-plugin can produce correct poms for deployment,
with all properties resolved; despite maven prints the ha
Just confirmed that I won't need these specific implementations, getting the
XMLReader via XMLReaderFactory is good enough.
Will commit this as part of MNG-6946.
Robert
On 24-6-2020 16:23:16, Elliotte Rusty Harold wrote:
The XML handling code in this work is running into some common design
flaws
The XML handling code in this work is running into some common design
flaws in the JDK XML classes, in particular in the Factories class.
First, you probably shouldn't use SAXParserFactory or SAXParser at
all. They were added to the JDK to support SAX 1.0, and haven't been
needed for since SAX 2 w
Hi,
One of my long standing wishes has made it to the master branch of Maven: the
support for build/consumer pom.
With this we can finally start improving the pom without breaking the Maven eco
system.
Up until now the pom.xml has been distributed (installed/deployed) as is to
both local and r
18 matches
Mail list logo
