Regarding the history, one of our contributor created a project, release
Jar atrifact which contains native libraries.
This artifact is not part of Surefire/Failsafe plugin.
It is used only in our ITs.
Naturally ARM is not supported because that time ARM was not much popular,
maybe only on the
+1, all fine
T
On Wed, Jul 6, 2022 at 10:08 PM Michael Osipov wrote:
> Hi,
>
> We solved 7 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12352045
>
> There are no issues left in JIRA:
>
>
David,
Sending from my mobile, so will be short. I wrote the roadmap with purpose
you was talking about. We can discuss it in a voice conf which would be
much faster and you can help us too but it would not be done by the way to
fire a random PRs. I neededed a break because of my job and illness
+1
Dňa ut 31. 5. 2022, 19:57 Andreas Dangel napísal(a):
> Hi,
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351350=Text=12317621
>
> There are still a couple of issues left in JIRA:
>
>
It works on JDK1.8 but it does not work on JDK18.
Do you have experiences with such issues?
T
On Mon, Apr 18, 2022 at 9:21 PM Michael Osipov wrote:
> Am 2022-04-18 um 21:19 schrieb Tibor Digana:
> > Did everybody run a local build?
> > I did and the IT failed MJAVADOC-538 w
+1
sha .. ok
build .. ok
T
On Sat, Apr 16, 2022 at 11:20 PM Michael Osipov wrote:
> Hi,
>
> We solved 11 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12351337
>
> There are still a couple of issues left in JIRA:
>
>
Did everybody run a local build?
I did and the IT failed MJAVADOC-538 with Maven 3.8.5 and JDK18.
It should be reproducible because the logs say:
MyClass.java:24: warning: use of default constructor, which does not
provide a comment
[WARNING] public class MyClass
[WARNING] ^
...
[ERROR] Failed to
+1
sha .. ok
build with jdk18 .. ok
T
On Sun, Apr 17, 2022 at 6:23 PM Michael Osipov wrote:
> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12351595
>
> There are still a couple of issues left in JIRA:
>
>
+1
sha .. ok
build with jdk18 .. ok
On Thu, Apr 14, 2022 at 10:37 PM Michael Osipov wrote:
> Hi,
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12351121
>
> There are still a couple of issues left in JIRA:
>
>
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 3.0.0-M6.
The release contains 111 bug fixes.
Again we received contributions from the community in the form of bug
reports and bug fixes.
Thank you and keep them coming!
It is a nice report in Jenkins but still this cannot be compared with Sonar.
Anyway, guys, feel free to continue in this discussion.
T
On Mon, Apr 4, 2022 at 2:26 AM Olivier Lamy wrote:
> On Mon, 4 Apr 2022 at 08:51, Tibor Digana wrote:
>
> > Regarding the next 4 reports out of 5:
+1
sha512 ok
build ok
T
On Sun, Apr 3, 2022 at 5:36 PM Hervé BOUTEMY wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322=12350902=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1734/
>
>
+1
The issues mentioned by Slawomir should be fixed after the release is
complete. Those issues are not a typical blocker.
On Fri, Apr 1, 2022 at 11:31 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 10 issues:
>
>
Regarding the next 4 reports out of 5:
Test report
Checkstyle report
PMD report and
Taglist report
we should use the Sonar Cube as a substitution and the development +
release process should take the Sonar into account on the fly.
Then I would understand the purpose of removal.
But now I don't!
hm, I do not understand his change regarding PR #49.
The CI result is used to fail due to the Socket timeout. The same has
happened in the latest surefire result vote. The build was red, we tried to
restart the build for 3 days, and finally the build got green at the end of
the Vote.
Instead of
Thank You guys.
The vote has passed with the following result:
+1 : Tibor Digana, Tamás Cservenák, Slawomir Jaranowski, Romain
Manni-Bucau, Christian Stein, Karl Heinz Marbaise, Delany, Sylwester
Lachiewicz, Dan Tran, Olivier Lamy, Arnaud Héritier, Hervé BOUTEMY
PMC quorum: accomplished.
I
Thank You guys.
The vote has passed with the following result:
+1 : Tibor Digana, Tamás Cservenák, Slawomir Jaranowski, Romain
Manni-Bucau, Christian Stein, Karl Heinz Marbaise, Delany, Sylwester
Lachiewicz, Dan Tran, Olivier Lamy, Arnaud Héritier, Hervé BOUTEMY
PMC quorum: accomplished.
I
ordering use flag
> -Dsurefire.runOrder.random.seed=55174043965113"
> Can you make it always do that? When I provide the flag, I don't get the
> message, so there's no record of the seed.
>
> +1
> Tested on Linux & Windows, JDK8 & 11
> Delany
>
> On Sat, 2 Apr 2022 at 15:4
+1
T
On Thu, Mar 31, 2022 at 2:35 PM Tibor Digana wrote:
> Hi,
>
> We solved 111 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344613
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jir
ll, or do I have to build it myself?
> > >
> > > Thanks,
> > > Delany
> > >
> > > On Thu, 31 Mar 2022 at 14:35, Tibor Digana
> > wrote:
> > >
> > > > Hi,
> > > >
> > > > We s
AFAIK, maven 4 is just a prototype.
T
On Sat, Apr 2, 2022 at 3:00 PM John Patrick wrote:
> Hi,
> If I want to start testing maven v4.x is it the master branch or the mvn4
> branch I need to build?
> Or is there a guide I can look at with current/known issues or work
> arounds?
>
> I've a few
Hi Guillaume,
I think it was in 2013 when I had IIRC chat with Jason and Kristian
Rosenvold that the model and Project is risky from the concurrency point of
view.
I found the setters implemented with ArrayList as thread unsafe, and I
proposed introducing Service classes with accessing the data
ve to build it myself?
> > >
> > > Thanks,
> > > Delany
> > >
> > > On Thu, 31 Mar 2022 at 14:35, Tibor Digana
> > wrote:
> > >
> > > > Hi,
> > > >
> > > > We solved 111 issues:
> > > &g
Hi,
We solved 111 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12344613
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
Staging
[INFO] BUILD FAILURE
[INFO]
On Tue, Mar 22, 2022 at 11:44 AM Olivier Lamy wrote:
> On Tue, 22 Mar 2022 at 14:40, Tibor Digana wrote:
>
> > Sorry for late reply.
> >
> >
gt; > >> if (severity == "WARN") {
> > >> log.warn("There is something wrong");
> > >> } else if (severity == "ERROR") {
> > >> throw new MojoFailureException("...") {
> > >> } else {
> > &g
e to hard to guess another property like
>
> maven.test.jvmcrash=FATAL
> maven.test.failure=WARN
> maven.test.error=ERROR
>
> :-)
>
> Am 16.03.22 um 12:25 schrieb Tibor Digana:
> > Hi Christoph,
> >
> > Such a granularity with error/failure might be also an addi
On Mon, Mar 14, 2022 at 6:18 PM Slawomir Jaranowski
wrote:
> pon., 14 mar 2022 o 10:52 Tibor Digana
> napisał(a):
>
> > Romain, it is not a bug.
> > Don't consider this as a bug. It was a feature request for change by
> > Olivier, and not a bug.
> > I clos
ust wondering but maybe it would be better to configure the severity
> instead of a true/false, something like:
>
> maven.test.failure=WARN
> maven.test.error=ERROR
>
> would only warn about failing tests but thrw exception if starting the
> test fails?
>
> Am 14.03.22
Läubrich a
> > écrit :
> >
> > > I also agree that the test at least should run, we use this property to
> > > run the test and produce result and later on have a buildstep that
> > > analyze the results (and probably fail the build job).
> > >
In case of the user property *maven.test.failure.ignore* the MOJO must not
throw any exception which is interpreted by the Maven Core as BUILD SUCCESS.
We have received an internal requirement to change the behavior of the user
property *maven.test.failure.ignore* so that the behavior will have
Hello Maven developers,
I want to inform you about some compliance issues between the Javadoc of
Maven Plugin API and the Maven Core 3.x behavior. I am only a messenger
providing the facts and I would like the community to post the opinions and
finally a concrete fix(es).
The Maven 3 reports
+1
T
On Sat, Mar 5, 2022 at 5:47 PM Michael Osipov wrote:
> Hi,
>
> We solved 27 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12351105
>
> There are still hundreds of issues left in JIRA:
>
>
+1
T
Dňa ne 27. 2. 2022, 19:12 Hervé BOUTEMY napísal(a):
> Hi,
>
> We solved 18 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12346694=Text
>
> Changes since the last release:
>
>
We have tried that on GitHub Actions and it was not terribly slow.
It was only useless to force every build configuration to run the
maven site.
Notice that the GH Actions are quite fast and if you employ only one
special run for "mvn site" with a deployment to a web container or gh_pages
then it
There is such a situation where the contributor changes the site, we vote
for his PR on GH but we lately find out that the site is broken in some
way. If I could see the site deployed to gh_pages which is a Git branch and
visualized on GH then the contributor would fix it much better.
Of course
+1
build .. ok
checksum .. ok
T
On Thu, Feb 17, 2022 at 3:03 PM Michael Osipov wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12351319
>
> There are still a couple of issues left in JIRA:
>
>
+1
On Thu, Feb 17, 2022 at 11:17 PM Hervé BOUTEMY
wrote:
> Hi,
>
> We solved 10 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12350295=Text
>
> https://github.com/apache/maven-apache-parent/compare/apache-24...apache-25
>
> Staging repo:
>
+1
On Mon, Feb 14, 2022 at 11:48 AM Tamás Cservenák
wrote:
> Howdy,
>
> We solved many issues (6.1.0 canceled release + 6.1.1 are both assigned to
> 6.1.1 version):
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523=12351333
>
> There are still some issues left in
+1
Build .. ok
Dňa pi 11. 2. 2022, 10:37 Olivier Lamy napísal(a):
> Hi,
> I'd like to release Apache Maven Compiler Plugin 3.10.0
>
> 7 issues fixed
> https://issues.apache.org/jira/projects/MCOMPILER/versions/12351256
>
> draft github release notes (sadly only for people with write access as
+1
build .. ok
sha .. ok
On Thu, Feb 10, 2022 at 9:25 AM Michael Osipov wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12348417
>
> There are still a couple of issues left in JIRA:
>
>
+1
build .. ok
sha .. ok
On Fri, Feb 11, 2022 at 11:28 AM Tamás Cservenák
wrote:
> Howdy,
>
> We solved many issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523=12342225
>
> There are still a handful of issues left in JIRA:
>
>
Tamas, do you also have empty pages?
https://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/maven-indexer-examples/indexer-examples-basic/index.html
https://maven.apache.org/maven-indexer-archives/maven-indexer-LATEST/maven-indexer-examples/indexer-examples-spring/index.html
On
Hi Falco, do not keep it in your mind, file a Jira ticket. If you post a PR
in progress, it would be worth to give a feedback in advance. Somebody may
guide you in the right direction rather sooner than later. T
Dňa št 10. 2. 2022, 11:45 Falko Modler napísal(a):
> TBH, I haven't created an
Create a Jira ticket or PR for moving from Mvn 2.2.1 to 3.0.
That would be the way but not to stop this release only because the version
2.2.1 is old and ugly. The build works and M1 should be verified in
practice.
T
On Tue, Feb 1, 2022 at 10:54 PM Guillaume Nodet wrote:
> -1
>
> Would it be
+1
build ... ok
On Tue, Feb 1, 2022 at 9:40 PM Michael Osipov wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320=12351216
>
> There are still a couple of issues left in JIRA:
>
>
+1
sha ... ok
build ... ok
On Sat, Feb 5, 2022 at 10:42 PM Michael Osipov wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12341015
>
> There are still a couple of issues left in JIRA:
>
>
; "accept" because
> this is the thing everybody would utilize to involve a trojan horse.
>
> yep, at least one apache-committer's review is needed I think.
>
> And apache-committer is hard to become, as I myself even not being one.
>
> Tibor Digana 于2022年2月4日周五 19:46写道
reviews I think.
> > If a maintainer disagrees with this and they do think they can review
> every
> > prs inside the 3 days limit, then I will be glad to show him why he
> can't,
> > just tell me what repos he maintains.
> > I do have the ability (and experience)
at 12:23 PM Xeno Amess wrote:
> 3 days?
> according to my experience, usually you need 30 - 180 days.
>
> Tibor Digana 于2022年1月28日周五 06:40写道：
>
> > It's nice to write some rules but still the developers are not machines.
> > You can, for instance, get some vote fo
It's nice to write some rules but still the developers are not machines.
You can, for instance, get some vote for totally crazy things like removing
public method in a library which is widely used in ASF or in the world.
Yes, your right against the rules but was this according to the best
+1
On Thu, Jan 27, 2022 at 1:21 PM Michael Osipov wrote:
> Hi,
>
> We solved 7 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12351277
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MPIR/issues
>
> Staging
+1
Cheers
Tibor17
On Sun, Nov 14, 2021 at 2:28 PM Michael Osipov wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12350685
>
> There are still a couple of issues left in JIRA:
>
>
e) automatically, but I
> think it will be more complicated and in standard usage is not needed.
> For automatic detection we have many corner cases, like testng + junit4 -
> testng by default runs junit4 tests, so without special configuration for
> testng we run some
junit4 -
> testng by default runs junit4 tests, so without special configuration for
> testng we run some of the tests twice.
>
>
> śr., 3 lis 2021 o 15:09 Tibor Digana napisał(a):
>
> > Hi Slawomir,
> >
> > The reality is different.
> > It's not the frame
Hi Slawomir,
The reality is different.
It's not the frameworks but providers.
So the plugin iterates over providers.
You may choose whether you will define the provider artifacts in plugin
deps or you let the plugin to select the providers upon dependencies which
means that there is some logic
Hi Ivan,
Basically the process is simple.
You should fork the master to your branch named, e.g. MRESOLVER-7.
I think the process is not a big issue right now.
The big issue here is the analysis of the code and a proposed fix.
It would be fine to split the changes into several independent
Scope=system is not like the Maven has proposed its biggest strength with
Maven dependencies and GAV. This scope should be deprecated or even removed.
Dňa pi 24. 9. 2021, 16:43 Romain Manni-Bucau
napísal(a):
> Hi all,
>
> wonder if there is any reason to see this warning when using a jar in the
LauncherSessionListener can be obviously used as a hack by the end users
but I do not see the reason why we should use it.
We do not want to explicitly call fixture methods because this would lead
to maintenance if Junit5 introduces new fixture mechanisms.
On Sat, Sep 11, 2021 at 12:25 PM Tibor
I do not want to stick to the latest version 1.8.
We have to stick to version 1.3 as it is right now.
We do not have a critical issue which could not be solved by reflection.
This reflection call, I proposed in GH, is made only once, no performance
penalty.
T
On Sat, Sep 11, 2021 at 7:52 AM Marc
d
>
> Op vr 10 sep. 2021 23:00 schreef Tibor Digana :
>
> > Hi Emond,
> >
> > Are you looking for this?
> >
> >
> https://github.com/junit-team/junit5/blob/main/documentation/src/test/java/example/UsingTheLauncherDemo.java#L86-L96
> >
> > On Fri,
Hi Emond,
Are you looking for this?
https://github.com/junit-team/junit5/blob/main/documentation/src/test/java/example/UsingTheLauncherDemo.java#L86-L96
On Fri, Sep 10, 2021 at 10:49 PM Emond Papegaaij
wrote:
> On Fri, Sep 10, 2021 at 9:15 PM Emond Papegaaij >
> wrote:
>
> > On Fri, Sep 10,
Sorry for typos, I sent it from my mobile.
T
On Fri, Sep 10, 2021 at 6:18 PM Tibor Digana wrote:
> We have to dig into Junit 5. Surefire is a streamer of classes across the
> forks which is our load balancer. Therefore each class is running
> separately, pre and post fixtures. If th
. 2021, 18:03 Emond Papegaaij
napísal(a):
> On Fri, Sep 10, 2021 at 5:06 PM Tibor Digana
> wrote:
>
> > If you use forkCount > 1, the Surefire loads test classes via load
> > balancer.
> > If you use default forkCount = 0, all the classes are run eagerly as a
> &
Please read the documentation
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
On Fri, Sep 10, 2021 at 5:05 PM Tibor Digana wrote:
> If you use forkCount > 1, the Surefire loads test classes via load
> balancer.
> If you use default forkCount = 0, all
If you use forkCount > 1, the Surefire loads test classes via load balancer.
If you use default forkCount = 0, all the classes are run eagerly as a
suite via JUnit5 Launcher in one shot.
If you are aiming for Arquillian, testing the applications in the
application server, you should use
+1
On Wed, Aug 4, 2021 at 10:02 PM Michael Osipov wrote:
> Hi,
>
> We solved 68 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922=12349965
>
> There are still a couple of issues left in JIRA:
>
>
iled. Terminating the channel maven5.
> java.util.concurrent.TimeoutException: Ping started at 1626936861982 hasn't
> completed by 1626937101983
> at hudson.remoting.PingThread.ping(PingThread.java:134)
> at hudson.remoting.PingThread.run(PingThread.java:90)
>
> @Gavin McDonald In terms of ne
Can we cut a new release of m-shade-p?
Is there any pending bug fix or improvement that you want to include in the
release?
Cheers
Tibor
https://ci-maven.apache.org/configureTools/ ) thus I suppose that the
> > different JDKs are supposed to be installed directly on the agent ?
> > I am not sure how it was done on the previous environment
> >
> > On Sun, Jul 18, 2021 at 5:30 PM Tibor Digana
What's the cost of this task? A day?
Do you want to include it in the release version 3.4.0?
On Wed, Jul 21, 2021 at 8:09 AM Romain Manni-Bucau
wrote:
> Hi all,
>
> shade plugin pom defines java version to 7 (1.7) but it uses streams which
> are java 8 only, should javaVersion property be
to complete it asap and include the fix in release notes.
T
On Sun, Jul 18, 2021 at 5:53 PM Enrico Olivelli wrote:
> Tibor
>
> Il Dom 18 Lug 2021, 17:06 Tibor Digana ha
> scritto:
>
> > -1, the reason is that the contributors and committers are waiting for PR
> > #
-1, the reason is that the contributors and committers are waiting for PR
#90 and #95, and pls restart the Vote which is faster right now.
T
On Sun, Jul 18, 2021 at 12:34 PM Michael Osipov wrote:
> I need one more binding vote...
>
>
A good patch!
+1
T
On Sat, Jul 10, 2021 at 3:39 AM Hervé BOUTEMY wrote:
> Hi,
>
> We solved 17 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12346845=Text
>
> https://github.com/apache/maven-apache-parent/compare/apache-23...apache-24
>
> Staging repo:
>
+1
Tibor
On Wed, Jun 16, 2021 at 8:50 AM Olivier Lamy wrote:
> Hi
> As already proposed by Guillaume, it looks to be a good idea to
> import mvndaemon/mvnd here at Apache.
>
> I'd like to propose a vote for this.
> +1: import the project here
> 0 : no real idea
> -1 : no (please explain why)
Hi Ceki,
The Jira issue is https://jira.qos.ch/browse/SLF4J-515
T
On Thu, Jul 8, 2021 at 3:54 PM Ceki wrote:
> Hi Tibor,
>
> Your analysis makes sense. As SimpleLogger acts as an appender as found
> in log4j/logback backends, SimpleLogger should cater for concurrent
> access with some sort of
+1
On Thu, May 13, 2021 at 8:17 PM Michael Osipov wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12350159
>
> There are still a couple of issues left in JIRA:
>
>
+1
@Herve you'r welcome ;-)
T
On Sun, May 9, 2021 at 8:15 PM Hervé BOUTEMY wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322=12349726=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1647/
>
>
+1
On Sat, May 8, 2021 at 11:36 AM Michael Osipov wrote:
> Hi,
>
> we solved 23 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12349416
>
> There are still a couple of issues left in JIRA:
>
>
+1 but I have one negative remark to the tradition with "Merge pull
request". If you watch the code, you would think that the project
duplicates some code, but it is not real. Whole problem is with these Merge
requests because they join several commits together, you type some comments
to the
cause for this one.
T
On Sun, May 2, 2021 at 10:24 PM Dan Tran wrote:
> we are in pain with this issue :-)
>
> -D
>
> On Sun, Jan 24, 2021 at 2:56 PM Tibor Digana
> wrote:
>
> > Hi Falco,
> >
> > This is not the first time I have been talking about thes
+1
On Fri, Apr 23, 2021 at 2:56 PM Robert Scholte wrote:
> Hi,
>
> We solved 14 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12344365=Text
>
> There are still a couple of issues left in JIRA:
>
>
+1
On Sun, Apr 25, 2021 at 9:46 PM Michael Osipov wrote:
> Hi,
>
> We solved 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821=12349521
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/projects/MPIR/issues
>
> Staging
You must have different Java packages in Jar modules in order to have
regular JMPS modules.
One user of Maven reported a bug against IntelliJ IDEA that the IDE does
not understand src/test/java/module-info.java.
The only way on how to support one common Java package and two JPMS modules
too is to
+1
On Sun, Apr 18, 2021 at 9:12 PM Robert Scholte wrote:
> Hi,
>
> We solved 12 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527=12344185=Text
>
> There are still a couple of issues left in JIRA:
>
>
Tibor Digana
wrote:
> Port 0 does not exist, only in your code.
> 0 means that a new unused local port is allocated.
> Again you have to use local loopback 127.0.0.1 as me. I had the same
> problem and I solved it.
> T
>
> On Mon, Apr 19, 2021 at 8:41 AM Maarten Mulders
>
roblematic.
> >> What is the error?
> >>
> >> What is the status of using java8 for IT tests? (current ITs are using a
> >> very very old version of Jetty 9.0.4...)
> >>
> >>
> >> On Mon, 19 Apr 2021 at 06:56, Tibor Digana
> wrote:
>
I had exactly the same problem and I added one more step to the CI which
checked all open ports.
For instance they changed something in Github and 8081 or 8082 was
allocated.
There was a conflict with the ports and I had to shift mine, that;s it.
T
On Sun, Apr 18, 2021 at 8:17 PM Maarten Mulders
+1
On Mon, Apr 12, 2021 at 7:31 PM Robert Scholte wrote:
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12348079=Text
>
> There are still a couple of issues left in JIRA:
>
>
+1
On Mon, Apr 5, 2021 at 4:29 PM Robert Scholte wrote:
> To: "Maven Developers List"
> Subject: [VOTE] Release Apache Maven Wrapper Plugin version 3.0.2
>
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721=12348358=Text
>
> There are
What was the third run? It was one thread with GraalVM?
$ time mvnd install -DskipTests -Dinvoker.skip=true
real 0m11,295s
user 0m0,354s
sys 0m0,176s
On Wed, Apr 7, 2021 at 7:09 PM Romain Manni-Bucau
wrote:
> Le mer. 7 avr. 2021 à 17:08, Tibor Digana a
> écrit :
>
> > Rom
ent
> behavior is already impressive (I expected the boost to be important but
> less when I started the thread 4 years ago to be honest).
>
> Le mer. 7 avr. 2021 à 15:40, Tibor Digana a
> écrit :
>
> > I think two years ago we were talking about Maven dockerization.
> >
I think two years ago we were talking about Maven dockerization.
We had the work in progress and I think I will be able to find it again.
The Docker image included local repo.
I think the biggest latencies are when you are downloading artifacts.
Of course, you have one local repo, but that's
Hi Robert,
The release note contains points 1. and 2., but the problem is that 2. is
empty.
Here is the picture attached, pls have a look, thx.
[image: obrázok.png]
On Tue, Mar 30, 2021 at 10:59 PM Robert Scholte
wrote:
> Hi,
>
> For the details about this release, please read
>
It is only a milestone version which means a work in progress. The fixes
made so far are really minor, no need to make any release.
If you take a look at the road map, you will see that I do not need to fix
tiny issues, I need to rework the additional attributes which will transfer
events about
Hi Som Lima,
Regarding (1), the Maven Central works with HTTPS for some time already.
Regarding the Repository Managers, e.g. Nexus or JFrog they have to be
updated to HTTPS in companies which is normal work for the administrators
and devops teams, not for the users or devs, but nowadays the
here is mine +1.
The amount of work means more for me than the version 3.7.0 we skipped. We
can improve it in the future of course!
Regarding the issues found with the Warning on the console, these issues
can be fixed as always, right after.
T
On Mon, Mar 22, 2021 at 8:40 PM Robert Scholte
Hi all,
There are two groups of multi-module projects:
- with many modules
- with one large module
The extension "gitflow-incremental-builder" and the cache are useful in the
first alternative.
But can we provide an incremental Java compiler for the second alternative?
If there is an argument
+1
On Thu, Feb 4, 2021 at 4:40 PM Sylwester Lachiewicz
wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12344858=Text
>
> There are still a couple of issues left in JIRA:
>
>
+1
On Fri, Jan 22, 2021 at 11:30 PM Sylwester Lachiewicz <
slachiew...@apache.org> wrote:
> Hi,
>
> We solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345175=Text=12317922=Text
>
> ** Improvement
> * [MSHARED-879] - make build Reproducible
> **
1 - 100 of 1362 matches
Mail list logo
