Il Dom 31 Mag 2020, 00:57 Olivier Lamy ha scritto:
> Hi
> First I'm not against PR and people asking review.
> But for obvious changes, we can probably avoid PR (ie some spam especially
> when people tag you in the description of a PR).
> We have a long history about commit-then-review so let's k
+1
On Sun, 24 May 2020 at 01:38, Hervé BOUTEMY wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12348077&styleName=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1578/
>
> https://reposit
Hi
First I'm not against PR and people asking review.
But for obvious changes, we can probably avoid PR (ie some spam especially
when people tag you in the description of a PR).
We have a long history about commit-then-review so let's keep this.
Such change don't really need a PR
https://github.co
makes sense to me.
Robert
On 30-5-2020 22:56:19, Hervé BOUTEMY wrote:
any objection that I create a new maven-artifact-plugin Git repository
initialized with current maven-buildinfo-plugin Git history?
Regards,
Hervé
Le mercredi 27 mai 2020, 19:26:55 CEST Robert Scholte a écrit :
> maven-studi
Le mardi 26 mai 2020, 00:05:39 CEST Robert Scholte a écrit :
> I missed the proposal for the version. I saw 3.2.5 and that can't be
> correct, hence I tried to explain what the correct version should be. So
> correct minimum version will be one of: 3.0, 3.1.0, 3.2.1, 3.3.1, 3.5.0
> This is the vers
any objection that I create a new maven-artifact-plugin Git repository
initialized with current maven-buildinfo-plugin Git history?
Regards,
Hervé
Le mercredi 27 mai 2020, 19:26:55 CEST Robert Scholte a écrit :
> maven-studies are just a sandbox, experimental code. Once it has a good
> shape, i
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12348151
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20component%20%3D%20%22ant%20tasks%22%20AND%20resolution%
apache-release profile is configured in Apache parent [1], then inherited in
every Maven parent POM
the only question I can see currently is if overriding the inherited config
makes sense, or even eventually cause some sort of conflict (because IIUC the
style of profile activation configuration
+1
On 23-5-2020 17:38:38, Hervé BOUTEMY wrote:
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12348077&styleName=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-1578/
https://repository.apache.org/content/re
here is my +1
more votes needed, please
Regards,
Hervé
Le samedi 23 mai 2020, 17:38:26 CEST Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&ve
> rsion=12348077&styleName=Text
>
> Staging repo:
> https://reposito
asfgit closed pull request #168:
URL: https://github.com/apache/maven-site/pull/168
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
dzikoysk commented on pull request #168:
URL: https://github.com/apache/maven-site/pull/168#issuecomment-636315538
Any thoughts on that? :)
This is an automated message from the Apache Git Service.
To respond to the message,
Hi,
I'd like to do a bootstrap release of the maven-wrapper-plugin, in order to
configure it in the next maven-core.
We solved 1 issue:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721&version=12348346&styleName=Text
There are no issues in JIRA:
https://issues.apache.o
Plugin is using an old parent, so the code in not reproducible
Cancelling the vote.
Robert
On 29-5-2020 14:09:38, Robert Scholte wrote:
Hi,
I'd like to do a bootstrap release of the maven-wrapper-plugin, in order to
configure it in the next maven-core.
There are no issues in JIRA:
https://is
14 matches
Mail list logo
