Delany wrote:
> Oh hi Nils. Yeah well a compromise is reached. I would still support a ban
> on tag in project-specific settings - more for enforcer.
> Its just about maintaining good abstractions. "User settings" what should
> that mean? Its basically the settings that a user doesn't want to
Oh hi Nils. Yeah well a compromise is reached. I would still support a ban
on tag in project-specific settings - more for enforcer.
Its just about maintaining good abstractions. "User settings" what should
that mean? Its basically the settings that a user doesn't want to commit.
You wanted "This
Le dim. 30 juil. 2023, 21:36, Garret Wilson a
écrit :
> On 7/30/2023 3:45 PM, Thomas Broyer wrote:
> > The easiest way to opt-in is to configure the plugin in
>
> > of the parent POM, and then only "apply" to chosen projects by declaring
> > the plugin in the (only needs the groupId and
Delany wrote:
> In any case, what repository on the Internet is configured to allow
> anonymous uploads? The settings.xml must always be populated with
> credentials for a deployment to take place.
> If you fear someone accidentally uploading artefacts to random repos then
> "you're doing it
On 7/31/2023 1:27 PM, Delany wrote:
…
In any case, what repository on the Internet is configured to allow
anonymous uploads? The settings.xml must always be populated with
credentials for a deployment to take place.
If you fear someone accidentally uploading artefacts to random repos then
On 7/31/2023 1:02 PM, Garret Wilson wrote:
…
Let me confirm something: if I disable the Nexus Staging Maven Plugin
by using `none` in a child POM, what will happen when a
developer types `mvn deploy`? Nothing? I only ask because Tamás had
mentioned the Maven Deploy Plugin. But I'm looking at
Deploy is a phase in the default lifecycle
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
So whatever plugins are bound to that phase will be executed if you ask
Maven to run to that phase. To see what those executions would be, run
mvn
On 7/31/2023 3:07 AM, Delany wrote:
Perhaps you're getting confused because you conflate 2 issues:
… prevent general configuration like from being inherited.
… preventing plugin configuration from being inherited.
I do not conflate them—I do not think they are the same thing. I said
they are
Perhaps you're getting confused because you conflate 2 issues:
One is about a way to prevent general configuration like from
being inherited. Currently the only way to do this is through profiles -
which you reject off-hand.
Allowing a project model to be composited with MNG-5102 is another
