+0
Same reason as Ralph, the versioning seems weird to me.
I don't understand the reasoning of version number. Our version number
doesn't have to be managed by some tweet or google links.
On Wed, 24 Mar 2021 at 09:17, Ralph Goers
wrote:
> If I were a user and expected the feature to be in
what "mvn" command are you running?
can you send me the full logs, please?
Regards,
Hervé
Le lundi 22 mars 2021, 22:00:31 CET Maarten Mulders a écrit :
> Tested on a MacBook, set up a HTTP (non-TLS) repository, and removed a
> part of my ~/.m2/repository. The missing artifacts are not
Alright, let's take a look back at your problem situation. I tried to
explain others, but figured out I didn't completely understand it.
Is this what you meant?
root:
... foo:
foo-a
foo-b
... images:
image-a
image-b
subparent:
. subimage-a
Le mar. 23 mars 2021 à 08:34, Martin Kanters a
écrit :
> Alright, let's take a look back at your problem situation. I tried to
> explain others, but figured out I didn't completely understand it.
> Is this what you meant?
>
> root:
> ... foo:
> foo-a
> foo-b
> ... images:
>
I agree that we should document changes between Maven 3 and 4 thoroughly, a
migration table is a good idea. I've added a comment in the maven-site
ticket: https://issues.apache.org/jira/browse/MNGSITE-444
Feel free to add your scenarios there.
I'm convinced your scenarios can be done using Maven
Hi Guillaume, hard to say whether this has something to do with the reactor
changes in my opinion. I see you have provided the JIRA issue [1].
Please let me know when you have a small sample project or IT. I would like
to check this out.
Thanks, Martin
[1]
The CVE is for documentation and the hardening of default behavior,
it's not your typical zero day.
On Mon, Mar 22, 2021 at 10:53 PM Gary Gregory wrote:
>
> You are acknowledging a CVE _before_ a release?
>
> Gary
>
>
> On Mon, Mar 22, 2021, 15:40 Robert Scholte wrote:
>
> > Hi,
> >
> > For the
after some review together, we identified that such basic error message happens
when blocked HTTP repository is defined in build pom.xml
Ideally, we would need an enhanced error message like it happens when HTTP
repository is defined in a dependency POM
Jira issue created for tracking that
If I were a user and expected the feature to be in 3.7.0 then I would certainly
also expect it in 3.8.0. The only ways to avoid this are a) stay on 3.6.x.x
until the feature is available, b) specifically say the promised features
aren’t available yet.
That said I’m +0 on the version numbering.
