I thought I’d responded - this has been a long time coming, and has been
discussed numerous times over the past few years, and I’m quite excited to
give it a bash, and see how well it works, and see if/what any implications
this has for our tiles-maven-plugin.
I still need to find time to dig into
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
first: thanks for sharing
from a high level point of view, the risk I see is to loose our conventions.
But let's try and see before judging
I think there are 2 topics currently mixed:
- default lifecycle phases:
do you want to add or remove phases? [1]
- default plugin bindings:
clearly, you
That good news. Call me Dr Deprecator of Maven Git Repos, I can call a vote
soon.
Robert
On 3-7-2020 21:56:40, Elliotte Rusty Harold wrote:
Indeed it does seem possible to remove maven-assembly-plugin's
dependency on maven-shared-io by copying a few classes from one into
the other and making the
Indeed it does seem possible to remove maven-assembly-plugin's
dependency on maven-shared-io by copying a few classes from one into
the other and making them non-public.
Removing file-management from the maven-dependency-plugin was even easier.
We should probably formally deprecate maven-shared-i
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
Looks like we can also remove the dependency from file-management to
maven-shared-io, again by copying a few classes into file-management.
I don't know if we can remove file-management completely.
On Thu, Jul 2, 2020 at 5:05 PM Robert Scholte wrote:
>
> The migration guide is about plugins, not a
I think we can remove it from the maven-assembly-pluign by copying two
or three classes into that plugin and making them non-public.
On Thu, Jul 2, 2020 at 5:05 PM Robert Scholte wrote:
>
> The migration guide is about plugins, not about libraries.
> For libraries it can be tricky.
>
> However, b
Hi everyone,
Wonder if we already discussed defining the lifecycle in the project (maybe
in $root/.mvn).
High level the need is to be able to change the default lifecycle in the
root pom without having to define a custom extension - in other words it is
about having a built-in extension.
The typic
10 matches
Mail list logo
