+1
On Sun, Oct 7, 2018 at 12:01 AM Michael Osipov wrote:
> Hi,
>
> We solved 14 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12342803
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/projects/MRESOLVER/issues
In IntelliJ IDEA it is "Remote", see Select Run/Debug Configurations >
Remote, change the port to 8000.
Run command *mvnDebug test* and then start "Remote" in IDEA.
On Tue, Oct 9, 2018 at 6:16 AM Romain Manni-Bucau
wrote:
> Hello
>
> Not sure the question was about test classes - you got answers
+1
Thx all for participating.
On Mon, Oct 8, 2018 at 10:22 AM Tibor Digana wrote:
> Hi,
>
> We solved 17 issues:
> https://issues.apache.org/jira/projects/SUREFIRE/versions/12343425
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/i
+1
On Thu, Oct 11, 2018 at 11:06 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 1 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12344286
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%
Hi,
The vote has passed with the following result:
+1: Karl Heinz Marbaise, Akira Ajisaka, Dejan Stojadinović, Enrico
Olivelli, Hervé BOUTEMY, Olivier Lamy, Tibor Digana
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file and add this release the
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 2.22.1
The release contains 17 bug fixes.
Again we received contributions from the community in form of bug reports
and bug fixes.
Thank you and keep them coming!
http://maven.apache.org/plugins/
Let's schedule the release day, no objections, but there are still two
open issues https://issues.apache.org/jira/projects/MNG/versions/12338966
which have not been discussed yet.
On Sun, Oct 21, 2018 at 8:11 PM Karl Heinz Marbaise
wrote:
> Hi to all Devs,
>
> * https://issues.apache.org/jira/b
I have computed SHA512 of the source release zip matching given hash
7aa3eef7a6c91793c2f7697b41a6edd6ed0dd002eb746c0fa86503a4c6391c85558878c7c7f2945a10a26caed5230d0088392f2bacb370995a3c7342aa43a2a4
+1
Cheers
Tibor
On Wed, Oct 24, 2018 at 8:48 PM Robert Scholte wrote:
> Let's do this with the
+1
On Fri, Oct 26, 2018 at 3:23 PM Robert Scholte wrote:
> Hi,
>
> We solved 12 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12335540&styleName=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jq
+1
On Wed, Oct 24, 2018 at 9:50 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We have solved 26 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12338966
>
> There are issues left in JIRA for Maven core:
>
> https://issues.apache.org/jira/issues/?jql=projec
+1
We plan also version 3.0?
On Sun, Oct 28, 2018 at 5:35 PM Hervé BOUTEMY wrote:
> Hi,
>
> We solved 30 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317825&version=12331230&styleName=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.a
+1
On Mon, Oct 29, 2018 at 5:34 AM Olivier Lamy wrote:
>
> Hi
> I'd like to release Maven plugin Tools 3.6.0
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343309&styleName=Text&projectId=12317820
>
> There are still a couple of issues left in JIRA:
> http
The job [1] hangs after previous shutdown and it is blocking Jenkins CI.
The job is trying to recover over half day and has no progress
according to the logs.
I will kill it and start it manually again.
[1] https://builds.apache.org/job/maven-box/job/maven-pmd-plugin/job/master/67/
--
Cheers
T
Can we add sub-version JDK 1.8.0_192 or JDK 1.8.0_192 to
maven-jenkins-env [1]? Is this JDK already installed on Jenkins by
Infra team?
Latest version should be independent of subversion, but I mean a new
label named "JDK 1.8 (181)" with concrete subversion.
We can introduce an integration test f
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342871
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://r
> On Fri, Nov 2, 2018 at 5:00 PM Tibor Digana
> wrote:
>
> > Hi,
> >
> > We solved 4 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342871
> >
> > There are still a couple of issues l
I am cancelling the first vote due to failed build and we can continue with
second vote. Sorry for that.
I am cancelling the first vote due to failed build and we can continue
with second vote. Sorry for that.
On Fri, Nov 2, 2018 at 5:00 PM Tibor Digana wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=123
+1
On Sat, Nov 3, 2018 at 11:32 AM Robert Scholte wrote:
> Hi,
>
> We solved 8 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317528&version=12330856&styleName=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql
t;
> - Eric L
>
> On 2018-11-03 13:58, Sylwester Lachiewicz wrote:
> > +1
> >
> > sob., 3.11.2018, 13:45: Tibor Digana
> napisał(a):
> >
> >> +1
> >>
> >> On Sat, Nov 3, 2018 at 11:32 AM Robert Scholte
> >> wrot
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342871
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://r
POM).
Due to we do not have this possibility now, we are able to test only with
such Java Specification Version which is 3 characters long at least, i.e.
9.0.1.
On Sun, Nov 4, 2018 at 11:48 AM Tibor Digana wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jir
y order. I noticed the process took a lot longer than usual
> after adding the staging repo, but I solved that by adding the default
> plugin repo as well.
>
> By the way, there were five issues closed, not four, which is not a bad
> thing, just a tiny error in the vote email text :)
>
+1, we need to have more participants in the Vote.
On Sun, Nov 4, 2018 at 11:48 AM Tibor Digana wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342871
>
> There are still a couple of issue
The vote has passed with the following result:
+1 : Eric Lilja, Enrico Olivelli, Christian Stein, Tamás Cservenák, Olivier
Lamy, Tibor Digana, Sylwester Lachiewicz, Karl Heinz Marbaise
0 : none
-1 : none.
PMC quorum: accomplished.
On Sun, Nov 4, 2018 at 11:48 AM Tibor Digana wrote:
>
The vote has passed with the following result:
+1 : Eric Lilja, Enrico Olivelli, Christian Stein, Tamás Cservenák, Olivier
Lamy, Tibor Digana, Sylwester Lachiewicz, Karl Heinz Marbaise
0 : none
-1 : none.
PMC quorum: accomplished.
I will promote the artifacts to the central repo.
--
Cheers
+1
On Thu, Nov 8, 2018 at 6:25 AM Olivier Lamy wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344059&styleName=Text&projectId=12317921
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/projects/MSHAD
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 3.0.0-M1
The release contains 5 bug fixes.
Again we received contributions from the community in form of bug reports
and bug fixes.
Thank you and keep them coming!
http://maven.apache.org/plugins
+1
I do not see the previous history in this vote.
On Sat, Nov 10, 2018 at 2:34 PM Robert Scholte wrote:
> +1
>
> On Thu, 08 Nov 2018 06:25:21 +0100, Olivier Lamy wrote:
>
> > Hi,
> >
> > We solved 4 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344059&styleName
Hi Romain,
Which class could not be loaded?
JAXB or CDI class?
Some class from Maven dist or another one?
BR,
Tibor
On Tue, Nov 13, 2018 at 5:35 PM Romain Manni-Bucau
wrote:
> Hi guys,
>
> did you plan to fix and upgrade classworlds to support java11?
>
> The trick is in org.codehaus.plexus.cl
Hi Robert,
Sorry I have not seen your email before.
" useModulePath " sounds good. I will rename the property if no objections.
BR
Tibor
On Sat, Nov 17, 2018 at 1:00 PM Robert Scholte wrote:
> On Sat, 17 Nov 2018 11:34:43 +0100, wrote:
>
> > This is an automated email from the ASF dual-hosted
Here is a command launched by our user
mvn test --file ./integration-tests/pom.xml
We have the following issue in Surefire but I think the root cause is in
Maven core.
https://github.com/apache/maven-surefire/pull/204
We can make a workaround in Surefire but is that right to do?
I am convinced
, 2018 at 1:31 PM Sylwester Lachiewicz
wrote:
> Hi Tribor, I think it can be MNG-6071
> <https://jira.apache.org/jira/browse/MNG-6071> i made fix some time ago.
> BR
> Sylwester
>
>
> niedz., 2 gru 2018 o 11:11 Tibor Digana
> napisał(a):
>
> > Here is a comman
Hi,
We solved 15 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12344396
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://
In my projects, the most plugins use single execution.
External projects also have this kind of principle.
Thus we should have a look in those possibilities where the most plugins
can gain the performance.
Usually the compiler and tests take long.
I know that maven-compiler-plugin:3.8.1 will be inc
I do not think it can be such JVM issue with string concatenations, otherwise
all the world has the same problem.
This type of issue is usually caused by multiple writes from multiple
threads.
Try to log every method with Thread id and we should see multiple ids.
The java.io is supposed to be synch
e/maven/tools/plugin/generator/PluginDescriptorGenerator.java
On Sat, Dec 8, 2018 at 11:46 AM Tibor Digana wrote:
> I do not think it can be such JVM issue with string concatenations,
> otherwise
> all the world has the same problem.
> This type of issue is usually caused by multipl
sts particularly, as no version of Surefire higher than
> that works well with it)
>
> - Eric L
>
> On 2018-12-05 23:26, Tibor Digana wrote:
> > Hi,
> >
> > We solved 15 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&am
ut this topic. I was just excited about M2
> since it brings us a lot closer to M3, which I am even more excited
> about for the reason described above, and I wanted to share that
> excitement.
>
> Great work!
>
> - Eric L
>
> On 2018-12-08 19:40, Tibor Digana wrote:
&g
+1
On Wed, Dec 5, 2018 at 11:26 PM Tibor Digana wrote:
> Hi,
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12344396
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org
Thank You!
PMC quorum reached: Krystian Nowak,Romain Manni-Bucau, Enrico Olivelli,
Olivier Lamy, Karl Heinz Marbaise, Francois Papon, Eric Lilja, Christian
Stein, Tibor Digana.
On Sun, Dec 9, 2018 at 10:28 AM Tibor Digana wrote:
> +1
>
> On Wed, Dec 5, 2018 at 11:26 PM Tibor Digana
Hi,
The vote has passed with the following result:
+1 : Krystian Nowak,Romain Manni-Bucau, Enrico Olivelli, Olivier Lamy,
Karl Heinz Marbaise, Francois Papon, Eric Lilja, Christian Stein, Tibor
Digana.
PMC quorum reached.
I will promote the artifacts to the central repo.
Cheers
Tibor Digana
+1
both checksums match, build success from src-zip.
On Sat, Dec 8, 2018 at 1:02 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 7 issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317526%20AND%20fixVersion%20%3D%2012343046%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>
+1
both checksums match, build success from src-zip.
On Sat, Dec 8, 2018 at 1:24 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522&version=12343422&styleName=text
>
> There are still a couple of issues left
+1
both checksums match, build success from src-zip.
On Sat, Dec 8, 2018 at 1:40 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/projects/MSHARED/versions/12344434
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jir
t; On Sat, 08 Dec 2018 12:44:40 +0100, Enrico Olivelli
>
> wrote:
>
> > +1 for Tibor's explanation.
> > Enrico
> >
> > Il sab 8 dic 2018, 12:29 Tibor Digana ha
> > scritto:
> >
> >> PluginDescriptorGenerator.writeDescriptor does not
-jdk7-m3.2.x_build, with the
> j.u.NoSuchElementException
> A rerun without any changes,now it luckily succeeds.
>
> Robert
>
> On Sun, 09 Dec 2018 17:35:45 +0100, Tibor Digana
>
> wrote:
>
> > Is the issue found on Oracle Jira or bug report?
> > This might to do
One more hint. What if the start element was added as NULL by an accident?
What if the impl of LinkedList ignores such element and then there are N -
1 elements to remove.
Adding an asset may help to find it.
On Sun, Dec 9, 2018 at 8:00 PM Tibor Digana wrote:
> I have checked everyth
Hi Herve
I have executed the build (mvn verify -P run-its) from the src zip but the
build failed:
Archetype IT 'it-basic' failed: Some content are not equals
Can you check it in the logs attached?
Thx
On Sun, Dec 9, 2018 at 4:48 PM Hervé BOUTEMY wrote:
> Hi,
>
> We solved 3 issues:
>
> https:
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 3.0.0-M2.
The release contains 15 bug fixes.
Again we received contributions from the community in form of bug reports
and bug fixes.
Thank you and keep them coming!
http://maven.apache.org/plugi
+1: here is mine
On Sun, Dec 9, 2018 at 4:48 PM Hervé BOUTEMY wrote:
> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317123&version=12343035&styleName=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira
+1
On Wed, Dec 12, 2018 at 5:49 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> here is my +1
>
> Kind regards
> Karl Heinz Marbaise
> On 09/12/18 16:41, Hervé BOUTEMY wrote:
> > Hi,
> >
> > We solved 3 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317123&version=12343
+1
On Sun, Dec 16, 2018 at 1:13 PM Robert Scholte wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12343568&styleName=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql
+1
On Sat, Dec 15, 2018 at 12:44 PM Robert Scholte
wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12338638&styleName=Text
>
> There are NO MORE issues left in JIRA (the only one left is doing this
> release):
>
> https:/
Try and you will see what happens.
I do not use it because I am the old school using IDEA and command line. I
need to see the code in IDE because this Diff in GitHub does not show me
the changes as good as IDEA does.
On Wed, Dec 19, 2018 at 6:01 PM Enrico Olivelli wrote:
> self anwsered:
> just
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342872
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://r
3.0.0-M3:
> >
> https://github.com/junit-team/junit5-samples/commit/a8660d636058a52fc68f7a9d6a5a11b42ee44303
> > Result: https://travis-ci.org/junit-team/junit5-samples/jobs/470432909
> >
> > On Thu, Dec 20, 2018 at 10:48 AM Tibor Digana
> > wrote:
> >
> > > Hi,
> > >
>
+1
On Thu, Dec 20, 2018 at 10:47 AM Tibor Digana
wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12342872
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org
Hi,
The vote has passed with the following result:
+1 : Christian Stein, Enrico Olivelli, Eric Lilja, Olivier Lamy, Karl Heinz
Marbaise, Tibor Digana
PMC quorum: reached
I will promote the artifacts to the central repo.
I will add the release to the next board report.
Cheers
Tibor
On Thu
Hi,
The vote has passed with the following result:
+1 : Christian Stein, Enrico Olivelli, Eric Lilja, Olivier Lamy, Karl Heinz
Marbaise, Tibor Digana
PMC quorum: reached
I will promote the artifacts to the central repo.
I will add the release to the next board report.
Cheers
Tibor
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 3.0.0-M3.
The release contains 6 bug fixes.
Again we received contributions from the community in form of bug reports
and bug fixes.
Thank you and keep them coming!
http://maven.apache.org/plugin
+1
On Tue, Dec 25, 2018 at 11:28 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 1 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12344667
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%
Does it mean that combinations of Maven and JDK reached the disk limit?
I am using JDK 7, 8, 11, 12 and Maven 3.2, 3.3 and 3.5.
So 12 combinations altogether.
Each makes cleanup, and the archiver stores totally 240 Mega Bytes per
build.
We have 10 surefire builds which makes 2.4 GB per Linux. Windo
+1
On Thu, Dec 27, 2018 at 11:21 PM Michael Osipov wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12344436
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D
These errors with JavaDoc in source code can be effectively avoided with
adding a JDK8 Profile in pom.xml and a config of compiler.
You do not need to wait for making a release when the Site is generated.
Even the contributor will fails his build when compiling and testing
project in his own:
o
..and so
> on)
> We already have tests over every supported platform, so Tibor's idea of
> adding doclint option whill enable us to have good coverage at every build
>
> Enrico
>
> Il mar 1 gen 2019, 13:03 Tibor Digana ha scritto:
>
> > These errors with JavaDoc in so
ady have tests over every supported platform, so Tibor's idea of
> adding doclint option whill enable us to have good coverage at every build
>
> Enrico
>
> Il mar 1 gen 2019, 13:03 Tibor Digana ha scritto:
>
> > These errors with JavaDoc in source code can be effe
I already lost the point of this thread.
Still the disk space problem on Windows executors in ASF Jenkins?
If it's this issue, then why the workspace is not investigated directly on
the system with remote access?
Jenkins is very good tool and I do not want to use Travis but Travis is one
step after
n Git
branches and should be fine for PRs as well.
On Thu, Jan 3, 2019 at 10:19 PM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On Thu 3 Jan 2019 at 20:52, Tibor Digana wrote:
>
> > I already lost the point of this thread.
> > Still the disk space problem on Win
019 at 21:37, Tibor Digana wrote:
>
> > Why the build cannot be triggered on GitHub or PR?
> > It's only a URL.
> > If you see the frequency of PRs in Surefire, 1 or 2 PRs/month, this
> should
> > not be a problem since the Windows build takes 1.5 hour and Linux 1
@Stephen Connolly
After such a big investment, especially made on your side, in Jenkins
plugin you developed you do not want to support the GitHub PRs and you just
let be to go with TravisCI just like that? I do not think so!
T
On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly <
stephen.alan.conn
Jan 5, 2019 at 12:11 AM Manfred Moser
wrote:
> I agree with Tibor. I would rather not have to deal with two different CI
> systems...
>
> Manfred
>
> Tibor Digana wrote on 2019-01-04 14:00:
>
> > @Stephen Connolly
> > After such a big investment, especially made o
+1
On Thu, Jan 3, 2019 at 2:28 PM Michael Osipov wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12344772
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2
Regarding "pull/1234/head" refs and the security, I think allowing only the
permission to Maven Central IP address is needed and nowhere else.
This can be accomplished by the java policy in JRE.
WDYT?
On Sun, Jan 6, 2019 at 11:09 AM Hervé BOUTEMY wrote:
> I didn't know about these special "pull/
s not the problem you think it is. Bitcoin mining is the current
> issue. And through Jenkinsfile or Process.exec you can bypass JVM
> permissions
>
> On Sun 6 Jan 2019 at 16:44, Tibor Digana wrote:
>
> > Regarding "pull/1234/head" refs and the security, I think all
disabled logs, workspace and artifacts for anonymous Jenkins users, but
available for PMC and Maven committers.
On Sun, Jan 6, 2019 at 8:41 PM Mickael Istria wrote:
> On Sun, Jan 6, 2019 at 8:32 PM Tibor Digana
> wrote:
>
> > I meant Bitcoins. Without network access bitcoins ca
Why we use old versions in default-bindings.xml?
Can we update all versions in 3.6.1 release?
Here is MNG-6557 which is related to Surefire but I guess this Jira issue
can be freely related to all plugins.
WDYT?
Any objections to update all plugins and assign this issue in 3.6.1?
Cheers
Tibor
continue to ignore the WARN on plugins versions and still get
> newest and latest plugins"
>
> this leads IMHO to one (bad) reason for people to require Maven Wrapper
>
>
> I know, this is counter intuitive, that's why it is required to really
> take a
> mom
19-01-11 um 12:55 schrieb Tibor Digana:
> > ok, Herve, the fact is that these plugins have been updated from time to
> > time.
> > How can we be on safe side with these updates? What is mandatory to do
> for
> > such upgrade?
>
> Testing...just like I do. See comment
I think we should downgrade maven-shared-utils to 3.1.0 in the m-invoker-p
because we found the same problem in surefire:3.0.0-M1.
We did not have time to fix it and I have realized the connection to the
Invoker just now.
Faster than a release is to deploy SNAPSHOT version of the Invoker and use
it
Such a drastic change?
First we should get the confidence using Jenkins CI for a long time run.
On Sat, Jan 12, 2019 at 11:20 AM Enrico Olivelli
wrote:
> Can't we rollback to the previous version instead of a snapshot?
>
> Enrico
>
> Il sab 12 gen 2019, 09:23 Tibor Digana h
t;
> >
> > Il sab 12 gen 2019, 11:39 Tibor Digana ha
> scritto:
> >>
> >> Such a drastic change?
> >
> >
> > If that version is buggy we should fix it or drop it.
> >
> > Do we have already released that buggy version to users?
>
;
> > Regards,
> >
> > Hervé
> >
> > Le samedi 12 janvier 2019, 15:42:57 CET Robert Scholte a écrit :
> >> Just wondering, can this be solved by an extension?
> >>
> >> So instead of changing this in Maven Core itself, people can add an
>
!!
> >
> > Should we try to go this route?
> >
> > Regards,
> >
> > Hervé
> >
> > Le dimanche 13 janvier 2019, 00:15:38 CET Stephen Connolly a écrit :
> >> The original plan was to make plugin version mandatory. Perhaps 3.7.0 is
> >> the
; >
> > >> > > I do understand Hervé concerns. We should motivate people to lock
> > >>
> > >> their
> > >>
> > >> > > plugins in their pom.
> > >> > > Most of all the packaging-p
fix these problems because
> they
> > > > > threaten the stability of your build.
> > > > > [WARNING]
> > > > > [WARNING] For this reason, future Maven versions might no longer
> > support
> > > > > building such malformed projects.
> > > > &g
To lookup easy or fast fixes, and +1 to perform a release then.
T
On Wed, Jan 16, 2019 at 1:56 PM Enrico Olivelli wrote:
> An user is asking for a release of the enforcer plugin
>
> https://github.com/apache/maven-enforcer/pull/36#issuecomment-447238729
>
> I can prepare the release
>
> Thoughts
+1
On Fri, Jan 18, 2019 at 4:01 PM Robert Scholte wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525&version=12343368&styleName=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql
+1
On Tue, Feb 5, 2019 at 12:15 AM Michael Osipov wrote:
> Hi,
>
> We solved 12 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12344885
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D
Is it so a big problem to keep both versions? This is our internal Nexus
server anyway.
On Wed, Feb 13, 2019 at 1:27 PM Benedikt Ritter wrote:
> Hello,
>
> Am Di., 12. Feb. 2019 um 08:39 Uhr schrieb Benedikt Ritter <
> brit...@apache.org>:
>
> > Hello,
> >
> > Am Mo., 11. Feb. 2019 um 18:39 Uhr
>
> > Am Mi., 13. Feb. 2019 um 17:48 Uhr schrieb Tibor Digana <
> > tibordig...@apache.org>:
> >
> > > Is it so a big problem to keep both versions? This is our internal
> Nexus
> > > server anyway.
> > >
> >
> > From my PoV the me
Benedikt, it does not mean that something with public IP is for public use.
We made only a compromise for some users to verify some functionality.
On Thu, Feb 14, 2019 at 11:42 AM Benedikt Ritter wrote:
> Am Mi., 13. Feb. 2019 um 17:48 Uhr schrieb Tibor Digana <
> tibordig...@a
Stephane, the problem is with Spring upgrade policy as I have understood.
What about releasing RC4 for you?
Do you really need to have SUREFIRE-1546 done? We do not want to enable it
implicitly as it is done in master right now, and therefore M4 needs to
take more time to enable this feature via c
welcome compromises on our side in ASF and now your steps in
Spring should be to make compromise in your internal policies.
Cheers
Tibor
On Mon, Feb 25, 2019 at 11:44 AM Stephane Nicoll
wrote:
> Thanks for the reply. See my feedback below
>
> On Mon, Feb 25, 2019 at 11:20 AM Tibor Digana
Stephane,
I have been quite busy with other JUnit5 work - SUREFIRE-1585.
Can you join us in the chat on Slack "the-asf.slack.com"?
You will find the Channel named "surefire".
Ping us as soon as you are ready and we will find some way.
I am glad!
Cheers
Tibor
On Mon, Feb 25, 2019 at 8:54 AM Stepha
Hi Stephane,
We are talking only about these two commits [1]?
Notice that 001e807 modifies file names to the verbose one which breaks
backwards compatibility and this should not forcibly (by default) happen in
your version/branch.
Try to fork the project, make a local branch and then reset HEAD t
+1
On Sun, Feb 24, 2019 at 9:34 PM Karl Heinz Marbaise
wrote:
> Hi to all,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12344643
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=pr
+1
On Fri, Mar 1, 2019 at 2:57 PM Robert Scholte wrote:
> Hi,
>
> We solved 46(!) issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12343313&styleName=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?
Hi Karl,
How you want to continue with this? The release plugin made commits to the
Git history. Do you want to complete it with deployment?
On Sun, Feb 24, 2019 at 9:34 PM Karl Heinz Marbaise
wrote:
> Hi to all,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
Hi,
All the issues for maven-compiler-plugin:3.8.1 is fixed.
https://issues.apache.org/jira/projects/MCOMPILER/versions/12343484
Can we agree on cutting the release version?
Do you see any reason to wait?
I am very happy to see a new incremental compiler, see
https://issues.apache.org/jira/brows
1 - 100 of 1363 matches
Mail list logo
