Le dim. 16 mars 2025 à 22:40, Slawomir Jaranowski
a écrit :
> Generally ok ...
> - we need first stabilize an API now I see that 4.x plugins should be
> changed again ...
>
That's really the reason why I'd like to branch: so that, if any new
feature requires a change in the API, it can be done i
I didn't summarise why it doesn't belong in maven, I summarised existing
uses across dozens of companies past and present. This is the current
reality for sophisticated users of the tiles plugin with M3. Not some pie
in the sky dream. I'm here because it sounded to me like that wasn't a
guaranteed
Le 2025-03-17 à 13 h 42, Romain Manni-Bucau a écrit :
(about being closely related to which plugin us it):
This is a quite dangerous target cause you will end up with scope =
plugin to keep it useable.
Not necessarily. This is only a convenience for a common pattern.
Plugins can filter the de
Le 2025-03-17 à 17 h 03, Matthias Bünger a écrit :
I'm not an IDE developer, but Maven user and mixing those two, for me
independend things, will make it more confusing than simpler.
The usage of introduced in Maven 4 is already implicitly mixing
the scope. The proposal to replace:
modula
On Mon, Mar 17, 2025 at 12:02 PM Guillaume Nodet wrote:
>
> We also need to disallowing version 4.0 poms without a proper namespace,
> >
>
> We just can't. Nor can we fix everything that's on Maven central. And
> that's the reason why we can't.
Yes, we absolutely can do that. We use a new mode
+1
On Sat, 15 Mar 2025 at 21:56, Slawomir Jaranowski
wrote:
>
> Hi,
>
> We solved 39 issues:
> https://github.com/apache/maven-apache-parent/milestone/5?closed=1
>
> There are no issues in GitHub
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=pro
+1
On Sun, 16 Mar 2025 at 05:38, Slawomir Jaranowski
wrote:
>
> Hi,
>
> NOTICE:
> ASF Maven parent 34 from staging is required for testing.
>
> We solved 40 issues:
> https://github.com/apache/maven-parent/milestone/5?closed=1
>
> There are still a couple of issues left in GitHUb
> https://github
I tried to clarify the 4.0 Milestones series in the version history, that were
upgraded to
3.20.0 (yes, wrong from a mathematical perspective, but right from the intent)
as they
were targetting Doxia 2 (before we have the "plugin 4.x = Maven 4 prerequisite"
convention)
https://maven.apache.o
My gut says the last occurrence should set the value, not the first.
At least that's how dependency versions are managed in the POM inheritance.
Other configuration systems like ini files override with subsequent values.
Is it too late to change?
Delany
On Mon, 17 Mar 2025 at 21:43, Karl Heinz Mar
On 18 Mar 2025 at 2:48:58 AM, Guillaume Nodet wrote:
> I'd be happy with a quick look from people experienced with tiles to check
> that it makes sense.
>
Took a quick look just now and aim to give it a closer/larger look soon.
Left one comment on the PR but also just noticed I get an NPE on a
Le lun. 17 mars 2025 à 12:29, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2025-03-17 à 12 h 02, Romain Manni-Bucau a écrit :
>
> > Concretely the issue there is that you now require the plugins to
> > configure a list of (type, scope) instead of a list of types to be
> >
Le 2025-03-16 à 17 h 37, Guillaume Nodet a écrit :
I think it's time to create a branch to release Maven 4.0.0 GA in the
coming weeks and switch master to 4.1.0-SNAPSHOT. Thoughts ?
One element that may be adjusted before GA. Maven 4 introduced a new way
to control where to put a JAR file, us
Ultimately this 100% depends on plugins.
A good example are annotation processors, you can have multiple passes in
the same module so type and scope are inaccurate (not blaming, just it
requires more effort to cover the case we cover with processor plugin
today).
Concretely the issue there is that
Le 2025-03-17 à 12 h 02, Romain Manni-Bucau a écrit :
Concretely the issue there is that you now require the plugins to
configure a list of (type, scope) instead of a list of types to be
functional.
I'd personally prefer we assume that types and scopes as two things do
not make sense anymore
I don't think tiles can be implemented just using a parser.
The ModelParser SPI provides a way to read a file into an existing *file*
model, but it does not handle parent hierarchy merging, profiles injection,
property substitution, etc... All those things are done by the ModelBuilder
which delega
Le 2025-03-17 à 08 h 23, Guillaume Nodet a écrit :
Yeah, I proposed a while ago to move the maven plugin and testing
harness inside Maven Core to keep them more easily aligned... So maybe
we think about it again ? I do think we want them to be roughly
available at the same time...
I would ap
>> And it just breaks all editors and IDE out there except the almost no
>> more used netbeans ;)
>
> Does it?
At least m2e should work with tiles extension (basically with any
extension).
> One option/alternative I had been contemplating was making the tiles
> plugin take the list of “tiles p
Le dim. 16 mars 2025 à 22:44, Mark Derricutt a écrit :
> On 17 Mar 2025 at 3:04:31 AM, Romain Manni-Bucau
> wrote:
>
> > And it just breaks all editors and IDE out there except the almost no
> more
> > used netbeans ;)
> >
>
> Does it? I guess that depends on how you use your IDE. IntelliJ stil
Le dim. 16 mars 2025 à 21:56, Elliotte Rusty Harold a
écrit :
> -1
>
> I don't think we're anywhere near ready to finalize 4.0. The more I
> look at it, the more issues I see.
>
> https://issues.apache.org/jira/browse/MNG-8537 is perhaps the most
> critical
>
This issue mentions several changes.
I've pushed an update POC at
https://github.com/apache/maven/pull/1209
There are clearly some things to adjust.
I'd be happy with a quick look from people experienced with tiles to check
that it makes sense.
Le lun. 17 mars 2025 à 09:17, Fred Cooke a écrit :
> I didn't summarise why it doesn
Le lun. 17 mars 2025 à 14:27, Martin Desruisseaux <
martin.desruisse...@geomatys.com> a écrit :
> Le 2025-03-17 à 13 h 42, Romain Manni-Bucau a écrit :
>
> (about being closely related to which plugin us it):
>
> > This is a quite dangerous target cause you will end up with scope =
> > plugin to
Hi,
I can't find any documentation about this plugin, everything is still
on version 3.x.
Should I stay on the 3.x versions ?
Using the last version of the fluido skin requires some update aroud
doxia which is not presetn of the version 4.x of the site plugin.
I am a bit lost about this.
Coul
Am 17.03.2025 um 11:47 schrieb Martin Desruisseaux:
In a discussion with some IDE developers, it has been suggested that
this list could be simplified with a combination of and .
I'm not an IDE developer, but Maven user and mixing those two, for me
independend things, will make it more c
4.x is reserved for Maven 4.x. Stick with 3.x+
On 2025/03/17 13:50:39 Tony Chemit wrote:
> Hi,
>
> I can't find any documentation about this plugin, everything is still
> on version 3.x.
>
> Should I stay on the 3.x versions ?
>
> Using the last version of the fluido skin requires some update a
Hi,
I'm trying to build a project with a number of subprojects..
I'm binding a plugin (just echoing) like this to new life cylce phases:
like this:
com.soebes.maven.plugins
echo-maven-plugin
before-ready
before:ready
Sure, that’s clearly not what I understood when you specifically mentioned
« 4.0 poms ». Since we have no correlation between the Maven version and
the model version , I assumed the later when talking about poms.
Guillaume Nodet
Le lun. 17 mars 2025 à 18:03, Elliotte R
Hi to all,
currently I'm trying to build a simple spring boot application which
uses a BOM for spring-boot-dependencies..
org.springframework.boot
spring-boot-dependencies
3.3.3
import
pom
So based on the releases of JUnit Jupiter, Mockito e
27 matches
Mail list logo
