I would like to update the docs about preparationGoals, adding
completionGoals and example about how to 'git add' files
Not blocker
Enrico
Il dom 1 dic 2019, 08:15 Hervé BOUTEMY ha scritto:
> merged, thank you for the PR
>
> I'll do the release next week-end: if anybody wants to update someth
merged, thank you for the PR
I'll do the release next week-end: if anybody wants to update something, you
have one week
here is the current state of the reference documentation:
https://maven.apache.org/maven-release-archives/maven-release-LATEST/
Regards,
Hervé
Le dimanche 24 novembre 2019,
Hi,
The vote has passed with the following result:
+1 : Robert Scholte, Karl Heinz Marbaise, Tibor Digana
PMC quorum: reached
I will promote the artifacts to the central repo.
On 26-11-2019 21:46:08, Robert Scholte wrote:
Hi,
To support the build/consumer process we need an improvement of Ma
+1
On Sat, Nov 30, 2019 at 5:39 PM Tibor Digana wrote:
> The URL of source dist archive is wrong.
> If you are going to test it, this is the right URL:
>
> https://repository.apache.org/content/repositories/maven-1543/org/apache/maven/shared/maven-artifact-transfer/0.12.0/maven-artifact-transfe
The URL of source dist archive is wrong.
If you are going to test it, this is the right URL:
https://repository.apache.org/content/repositories/maven-1543/org/apache/maven/shared/maven-artifact-transfer/0.12.0/maven-artifact-transfer-0.12.0-source-release.zip
On Sat, Nov 30, 2019 at 3:39 PM Karl H
Hi,
here is my +1
Kind regards
Karl Heinz Marbaise
On 26.11.19 21:46, Robert Scholte wrote:
Hi,
To support the build/consumer process we need an improvement of Maven Artifact
Transfer, hence this release.
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1
Good news
Il giorno sab 30 nov 2019 alle ore 14:27 Robert Scholte <
rfscho...@apache.org> ha scritto:
> Hi Enrico,
>
> current implementation says groupId+artifact are required, but you can
> either specify version or relativePath (or omit it, meaning ../pom.xml)
> I've decided to keep G+A so MAv
Hi Enrico,
current implementation says groupId+artifact are required, but you can either
specify version or relativePath (or omit it, meaning ../pom.xml)
I've decided to keep G+A so MAven can verify the pom is pointing to the right
parent.
MNG-6656 has a demo attached which shows you the new val
+1
On 26-11-2019 21:46:08, Robert Scholte wrote:
Hi,
To support the build/consumer process we need an improvement of Maven Artifact
Transfer, hence this release.
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12344974&styleName=Text
There
Hi,
when we move to the consumer pom we can leverage the disk layout of
projects inside the same repository while looking for the parent pom.
Currently you can use the element to refer to the location
of a parent pom, AFAIK this is only an hint for Maven and for tools: you
must always copy all of
10 matches
Mail list logo
