14. Close the vote
15. Commit the finalized release notes
16. Commit the updated doap
17. Add the release to the dist
$ cd ~/tmp
$ svn co https://dist.apache.org/repos/dist/dev/maven/maven-3 maven-dist
$ cd maven-dist
$ mkdir -p 3.5.0/{binaries,source}
$ for ext in tar.gz zip ; do ( cd
Hi,
The vote has passed with the following result:
+1: Mark Derricutt, Dejan Stojadinović, Grzegorz Grzybek, Petr Široký, Igor
Fedorenko (binding), Anders Hammar, Manfred Moser, Karl Heinz Marbaise
(binding), Tibor Digana (binding), Fred Cooke, Raphael Ackermann, Hervé
Boutemy (binding), Olivier
23. Mark the version in JIRA as released
On 7 April 2017 at 09:40, Stephen Connolly
wrote:
> 14. Close the vote
> 15. Commit the finalized release notes
> 16. Commit the updated doap
> 17. Add the release to the dist
>
> $ cd ~/tmp
> $ svn co
Hi Robert ,
*JDK 9 Developer Preview is now available on java.net [1]
*
Developer Preview milestone: - A reasonably stable build suitable for
broad testing by the developer community is available.
JDK 9 Builds 163 and higher include all planned features.
*Attention annotation
Hello,
thanks for the fast turnaround.
I am afraid I've hit another issue (or maybe misconfiguration?). I was
trying to use -Dmaven.surefire.debug in the following project:
https://github.com/psiroky/surefire-2.20-debug-reproducer
$ mvn clean install -s settings.xml -Dmaven.surefire.debug
The
One more difference (bug?) I found:
When I do:
final URL parentUrl = this.getClass().getResource("/");
System.out.println(parentUrl);
the output is
'file:/home/psiroky/tmp/surefire-2.20-debug/target/test-classes//' -- note
the duplicated slash at the end.
I've done the same with 2.19.1 and the
This is related to ForkConfiguration.
There is path created for the manifest.
On Fri, Apr 7, 2017 at 1:44 PM, Petr Široký wrote:
> One more difference (bug?) I found:
>
> When I do:
>
> final URL parentUrl = this.getClass().getResource("/");
>
Good point. The PING chcking should be disabled when JMX observes debug
mode.
See implementation in JUnit sources. The same is there.
Can you open pull request with a fix?
On Fri, Apr 7, 2017 at 11:06 AM, Petr Široký wrote:
> Hello,
>
> thanks for the fast turnaround.
>
>
GitHub user kevin-canadian opened a pull request:
https://github.com/apache/maven/pull/112
Fix snapshot regular expression
The snapshot regular expression should only match an explicit period.
You can merge this pull request into a Git repository by running:
$ git pull
I'try to take a look. However, I have no prior experience with jUnit or
surefire sources, so it might take a while until I have something.
Thanks,
Petr
On Fri, Apr 7, 2017 at 2:22 PM Tibor Digana
wrote:
> Good point. The PING chcking should be disabled when JMX
Thank you for the new release!
Gary
On Apr 7, 2017 2:07 PM, "Stephen Connolly" wrote:
> The Apache Maven team would like to announce the release of Apache Maven
> 3.5.0.
>
> You can download the appropriate sources etc. from the download page
>
>
The Apache Maven team would like to announce the release of Apache Maven
3.5.0.
You can download the appropriate sources etc. from the download page
http://maven.apache.org/download.cgi
Notable changes
===
- ANSI colors added to the console output
- Fix various bugs in mvn scripts
Congratulations on a successful release! Thanks to all of the maven core team
for your work, particularly for the willingness to abandon 3.4 and reset to a
more iterative approach.
Thanks,
Chas
> On Apr 7, 2017, at 2:07 PM, Stephen Connolly wrote:
>
> The Apache Maven
Github user Fuud commented on the issue:
https://github.com/apache/maven-surefire/pull/114
any updates?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Sorry, I realized this was pending issue after release Vote started. Do not
worry, we will trigger a new version 2.20.1 in two weeks. Something is
already in good progress like this, so no reason to wait too long for
2.20.1.
On Fri, Apr 7, 2017 at 8:52 AM, flungo [via Maven] <
I completely agree we need to prove each code change does not break
existing integration tests (and I did run the tests locally with my
changes, fwiw)
--
Regards,
Igor
On Fri, Apr 7, 2017, at 11:58 AM, Stephen Connolly wrote:
> I want every issue that changes code (not docs or javadocs) to have
Hi Igor,
Also, does anyone know how to get my JIRA account fixed so I can
assign/close/etc bugs?
You are not allowed to do? Write an INFRA ticket...in the meantime I or
others can help here with that...
JIRA says your account does not exist...tried to assign 6210 to you...
Looks really
I want every issue that changes code (not docs or javadocs) to have an
integration test run before merging.
We were trying to get consensus on a process but the debate died without a
conclusion
On Fri 7 Apr 2017 at 16:21, Igor Fedorenko wrote:
> I have two of small-ish
Github user khmarbaise commented on the issue:
https://github.com/apache/maven/pull/112
First thanks for your pull request but it is really needed that you open a
[JIRA ticket ](issues.apache.org/jira/browse/MNG) and furthermore it would be
great if you could offer some unit tests
Hi Igor,
On 07/04/17 17:21, Igor Fedorenko wrote:
I have two of small-ish fixes I'd like to submit, so I was wondering if
master is open for 3.5.1 changes already or we want to give it little
more time in case we need to release any emergency patches.
If that's really necessary we can simply
Thank you for quick response, Karl. I'll create feature branches and
push proposed fixes there.
Is there a preference between apache and github for code review
branches?
--
Regards,
Igor
On Fri, Apr 7, 2017, at 11:32 AM, Karl Heinz Marbaise wrote:
> Hi Igor,
> >>
> >> Also, does anyone know
I have two of small-ish fixes I'd like to submit, so I was wondering if
master is open for 3.5.1 changes already or we want to give it little
more time in case we need to release any emergency patches.
Also, what is the general bug fixing protocol now, push to directly to
master and be prepared
@Petr
Both issues are fixed now. Would you please verify this version from
master? I tested on my side.
On Fri, Apr 7, 2017 at 3:42 PM, Petr Široký wrote:
> I'try to take a look. However, I have no prior experience with jUnit or
> surefire sources, so it might take a
24. Publish the website with https://cms.apache.org/maven/publish
25. Send the announcement email
26. (PMC only) Record the release on
https://reporter.apache.org/addrelease.html?maven
27. Tweet the release
TODO:
28. Wait for the announcement email to show up on the
Yes, agreed, 30 is a lot, but if you have N artifacts in a dir running
sha1sum dir/* and pasting the result raw into the email is not difficult.
Less so than formatting the two, probably.
On 8 April 2017 at 09:13, Stephen Connolly
wrote:
> On 7 April 2017 at
The CI build will finish after 3 hours.
Then the SNAPSHOT version will be in Maven Central.
On Fri, Apr 7, 2017 at 11:40 PM, Dan Tran wrote:
> is 2.20-SNAPSHOT up to date? that is only quick way I can test
>
> Thanks
>
> -D
>
> On Fri, Apr 7, 2017 at 2:03 PM, Tibor Digana
On 7 April 2017 at 22:10, Fred Cooke wrote:
> Thanks for all of your hard work on this, much appreciated!
>
> A little feedback for 3.5.1 (not helping with 3.5.0): checksums for the
> binaries too, not just the source.
>
>
checksums are in the staging repo and on the
is 2.20-SNAPSHOT up to date? that is only quick way I can test
Thanks
-D
On Fri, Apr 7, 2017 at 2:03 PM, Tibor Digana
wrote:
> @Petr
> Both issues are fixed now. Would you please verify this version from
> master? I tested on my side.
>
> On Fri, Apr 7, 2017 at
Thanks for all of your hard work on this, much appreciated!
A little feedback for 3.5.1 (not helping with 3.5.0): checksums for the
binaries too, not just the source.
That's it. :-)
On 8 April 2017 at 09:05, Stephen Connolly
wrote:
> 24. Publish the website
29 matches
Mail list logo