+1 to the principle. Can we see your proposed procedure (if you are
tweaking one of the other steps to mention this requirement)
On Sunday 30 October 2016, Robert Scholte wrote:
> Hi,
>
> I'd like to remove step 6 of our release procedure[1]:
> 6. Add the release to the next board report
Hi,
I'd like to remove step 6 of our release procedure[1]:
6. Add the release to the next board report, in the private subversion
area.
This is a PMC activity. If you are not a PMC member then email the
Developer's list with a request to update this file for your release.
When copying the
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.6.0
The Compiler Plugin is used to compile the sources of your project.
This version introduces support of several new features of Java 9, such as:
JEP 247: Compile for Older Platform Vers
Hi,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12317320&version=12338585&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND
%20status%20%3D%20Open%20ORDER%20BY%20key
+1
Regards,
Hervé
Le samedi 29 octobre 2016, 20:45:43 CET Robert Scholte a écrit :
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317222&ve
> rsion=12335850&styleName=Text
>
> There are still a couple of issues left in JIRA:
> https://issues.
+1
Regards,
Hervé
Le jeudi 27 octobre 2016, 21:58:32 CET Robert Scholte a écrit :
> Hi,
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&ve
> rsion=12334249&styleName=Text
>
> There are ZERO issues left in JIRA:
> https://issues.apache.org/jir
Hi,
Patch looks good to me, apply it if you want.
I don't know the details about the deprecation of ArtifactMetadata, I
could imagine that it should be a Maven internal thing and plugins
shouldn't matter about its details. But as long as we need something like
ProjectArtifactMetadata we ca
Hi
1.0.0-beta-1 sounds a good idea.
Anyway as you release it do whatever you want :-)
On 30 October 2016 at 03:48, Karl Heinz Marbaise wrote:
> Hi Robert,
>
> On 29/10/16 16:24, Robert Scholte wrote:
>
>> 1.0.0 suggest pretty final to me. I suggest 0.9.0 instead (even though
>> 0.10.0 is a valid
Github user vaimr commented on the issue:
https://github.com/apache/maven-surefire/pull/122
Thanks @Tibor17 !
---
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 s
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/122
@vaimr
I had to change more things. See this diff and close the issue. Thx for
contributing.
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commitdiff;h=fb9b699e27dae
+1
On Sunday, 30 October 2016, Robert Scholte wrote:
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12317222&version=12335850&styleName=Text
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=proj
+1
On Sat, Oct 29, 2016 at 8:46 PM, rfscholte [via Maven] <
ml-node+s40175n5884422...@n5.nabble.com> wrote:
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317222&version=12335850&styleName=Text
>
> There are still a couple of issues left in J
12 matches
Mail list logo
