Hi Gabriel,
Let me paraphrase what you said " ... into master ... before I made changes
using PatternExcludesArtifactFilter based on the reviews ".
This means we are missing some commit in master.
In this case it does not make sense to test this project because the work
is incomplete.
We have to c
Hi Tibor:
Please note I don't know if it's a plugin issue. Further tests shows that
it works OK when configuring the plugin in the reporting section:
org.apache.maven.plugins
maven-project-info-reports-plugin
3.0.1
org.eclips
Hello,
As I going to start the release procedure for Maven Core I have a bunch of
questions.
I see that the procedure is slightly different from the procedure for
plugins ([1]), but actually the main differences are about the way we stage
the release artifacts and the finalization phase, the core
Il sab 24 ago 2019, 12:16 Tibor Digana ha scritto:
> Enrico, I know that Michael mentioned some test failure but I could not
> find it in MNG-6695 because the executions 1 and 2 were deleted by 3.
> So only Michael has the resources which belong to that error.
> Michael have you investigated the
that's bad. We were too fast :-)
Although my build passed but in this case as I saw the commit I have to
give my -1, sorry!
On Sat, Aug 24, 2019 at 9:41 PM Gabriel Belingueres
wrote:
> Hi:
>
> Regarding MPIR-375, I noted that the merge of the PR into master branch
> was done *before* I made chan
+1
Regards,
Hervé
Le vendredi 23 août 2019, 15:17:23 CEST Robert Scholte a écrit :
> Hi,
>
> The Apache Maven project consist of about 90 (sub)projects. Due to the
> small number of volunteers and the huge amount of code to maintain we're
> missing enough space to make real progress on all thes
Hi:
Regarding MPIR-375, I noted that the merge of the PR into master branch was
done *before* I made changes using PatternExcludesArtifactFilter based on
the reviews.
See https://github.com/apache/maven-project-info-reports-plugin/pull/7.
The commit in master is:
https://github.com/apache/maven-p
Hi Robert ,
*JDK 13 is now in the Release Candidate Phase
*
Per the JDK 13 schedule [1], we are now in the Release Candidate phase.
The stabilization repository, jdk/jdk13, is open for P1 bug fixes per
the JDK Release Process (JEP 3) [2].
All changes require approval via the Fix-Request Proces
Enrico, I know that Michael mentioned some test failure but I could not
find it in MNG-6695 because the executions 1 and 2 were deleted by 3.
So only Michael has the resources which belong to that error.
Michael have you investigated the error, what is it, what cause?
T
On Sat, Aug 24, 2019 at 12:
Il ven 23 ago 2019, 11:55 Enrico Olivelli ha scritto:
>
> I see this test failing on current master, locally on my machine (MacOS),
> this is a show stopper...
> I will investigate as soon as possible, but today I can't
>
The test doesn't fail on my fedora box, only on Mac, consistently.
We are
10 matches
Mail list logo
