+1 both for immediate vote and for the plan to release as is then releasing
ASAP 3.5.4
Regards,
Hervé
- Mail original -
De: "Mirko Friedenhagen"
À: "Maven Developers List"
Envoyé: Samedi 3 Mars 2018 13:42:43
Objet: Re: [VOTE] Release Apache Maven 3.5.3
I would suggest releasing as is
I would suggest releasing as is as well.
State in the announcement that there might be a problem with parallel
builds on Windows, workaround with batch mode is easy anyway.
And if 3.5.4 only contains the fixed jansi dependency, releasing should be
fast and simple.
Best regards
Mirko
--
Sent fro
Maybe disappointed a bit on how we run the build with Java 1.8 and another
J7 - J10 used in all Tests (unit + integration tests).
$ mvn install -P run-its -nsu -Dintegration-test-port=8000
-Dintegration-test-stop-port=8001 "-Djdk.home=d:\Program Files\Java\jdk10"
-Djacoco.skip=true
There were sever
Regarding the "dummy" artifact, we do not have to do anything in here and
not to report a bug because the next release together with new API 3.0
naturally removes this hack.
Thx
On Fri, Mar 2, 2018 at 3:09 PM, Alex O'Ree wrote:
> I was about to post the stack trace when i more carefully read the
Hello Olivier,
We can continue with the next work in parallel if you agree.
Basically two things to do. The Java 7 and API 3.0.
The branch 3.0-rc-1 already exists. So would rather take this because I
know the branch and it contains a lots of 3.0 commits which need to be
squashed in one and master
Let's see if I have to send a new email.
The release notes, deployment and SHA1 are related to right version. Only
the title is bad.
On Sat, Mar 3, 2018 at 12:46 PM, Enrico Olivelli
wrote:
> Thank you !
> I will test on my company projects as soon as possible (maybe monday).
>
> nit: is The sub
+1 from me.
I did not find any issue.
On Sat, Feb 24, 2018 at 11:00 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 22 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12341428&styleName=Text&projectId=12316922
>
> There are 381 issues
Typo, the version is 2.21.0 of course.
On Sat, Mar 3, 2018 at 12:42 PM, Tibor Digana
wrote:
> Hi,
>
> We solved 33 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317927&version=12341630
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.
Thank you !
I will test on my company projects as soon as possible (maybe monday).
nit: is The subject of the vote thread wrong ?
Enrico
2018-03-03 12:44 GMT+01:00 Tibor Digana :
> The e-mail went out. The vote has started.
> Should I mention how to run the build with other JDK and follow the
The e-mail went out. The vote has started.
Should I mention how to run the build with other JDK and follow the
README.md on GitHub?
On Fri, Mar 2, 2018 at 8:16 PM, Enrico Olivelli wrote:
> Il ven 2 mar 2018, 19:43 Tibor Digana ha scritto:
>
> > I will close the Jira Version and I will complete
Hi,
We solved 33 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12341630
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
Staging repo:
https://
On Sat 3 Mar 2018 at 09:02, Karl Heinz Marbaise wrote:
> Hi,
>
> I just realized that our download link from the download page[1] points to:
>
> http://artfiles.org/apache.org/maven/
>
> Is that intentional ?
Depends on geolocation... my link is
http://mirrors.whoishostingthis.com/apache/maven
Hi,
I just realized that our download link from the download page[1] points to:
http://artfiles.org/apache.org/maven/
Is that intentional ?
Good idea? on http instead of https ?
Why not using:
https://www.apache.org/dist/maven/
Maybe I missed somthing ?
Kind regards
Karl Heinz Marbaise
13 matches
Mail list logo