Obviously, the reporting is not the only one sectipn of pom where you use
the latest version of this plugin. See your logs and the goal=test of the
plugin.
T
Dňa št 5. 5. 2022, 16:14 Nelligan, Steven M
napísal(a):
>
> This is the only reference I have to "surefire" in my POM file.
> ...snip...
It should not be any issue if you switch to JDK8 and add maven sniffer
plugin along with compiler 1.7.
T
Dňa št 5. 5. 2022, 16:00 Antoine Mottier
napísal(a):
> Starting with version 3.0.0-M6 maven-surefire-plugin requires Java 8
> or higher. As you are running it using Java 7 this explains your
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!
dcard filter to the TestListResolver, but I don't know what that means.
> I'll be glad to test it when it's put into a released version.
>
> Is there any thought as to when this will go into a full release, instead
> of M releases?
>
> > -Original Message-
> > From: Tibor Digana
&
The principles in junit providers are +/- the same, or they should be. So
it was easy to find the difference and make the fix!
T
On Mon, Mar 21, 2022 at 12:25 AM Tibor Digana
wrote:
> Hey David,
>
> Here is the PR.
> You can see the integration test of documentation with the pri
wse/SUREFIRE-2040 .
>
> > -Original Message-
> > From: Tibor Digana
> > Sent: Sunday, March 20, 2022 12:03 PM
> > To: Maven Users List
> > Subject: Re: Can't get Surefire to run any JUnit 5 tests
> >
> > Hello David,
> >
> >
Thx David, I will ping you with a pull request on Github soon.
Cheers
Tibor
On Sun, Mar 20, 2022 at 8:23 PM KARR, DAVID wrote:
> Here's my ticket: https://issues.apache.org/jira/browse/SUREFIRE-2040 .
>
> > -Original Message-
> > From: Tibor Digana
> > Sent: S
:
> > -Original Message-
> > From: Tibor Digana
> > Sent: Sunday, March 20, 2022 6:42 AM
> > To: Maven Users List
> > Subject: Re: Can't get Surefire to run any JUnit 5 tests
> >
> > There was the same question maybe one week ago.
> > I h
Mar 20, 2022 at 1:46 AM David Karr
wrote:
> On Sat, Mar 19, 2022 at 5:06 PM Tibor Digana
> wrote:
>
> > My advice is not to listen to everyone but rather understand how things
> > work.
> > Open this link in your browser
> > https://repo1.maven.org/maven2/org/ju
mport org.junit.platform.suite.api.Suite;
>
> @Suite
> @SelectClasses(NoteResourceCT.class)
> public class ComponentTestSuite {
> }
>
> I have heard some mentions of "Tags" in Junit5 and "groups" in Surefire.
> I have e
more complicated.
> >
> > > -Original Message-
> > > From: Tibor Digana
> > > Sent: Saturday, March 19, 2022 1:27 PM
> > > To: Maven Users List
> > > Subject: Re: Can't get Surefire to run any JUnit 5 tests
> > >
> > > I
I believe that is at least one element that makes
> this more complicated.
>
> > -Original Message-
> > From: Tibor Digana
> > Sent: Saturday, March 19, 2022 1:27 PM
> > To: Maven Users List
> > Subject: Re: Can't get Surefire to run any JUnit 5 tests
I have created a project which proves that it works with Surefire 3.0.0-M5,
JUnit Jupiter 5.8.2 and Mockito Extension. Please do not use JUnit4 and
Vintage in this case. It is not necessary to use a dependency inside of the
plugin. Use a dependency in the project POM. Follow it on Github:
Cheers
Tibor
On Tue, Feb 15, 2022 at 11:06 AM Tibor Digana
wrote:
> Hi Alexander,
>
> I have realized that we can move straight ahead with the following.
> Basically your expectations are to shift the concrete phase execution of
> the build lifecycle to the end of the build.
> I
his thread.
>
> Kind regards
> --
> Alexander Kriegisch
> https://scrum-master.de
>
>
> Tibor Digana schrieb am 07.02.2022 23:16 (GMT +07:00):
>
> > I can imaging to utilize afterSessionEnd()
> >
> https://maven.apache.org/ref/3.8.4/maven-core/apidocs/index.html?
Kind regards
> --
> Alexander Kriegisch
> https://scrum-master.de
>
>
> Tibor Digana schrieb am 07.02.2022 23:16 (GMT +07:00):
>
> > I can imaging to utilize afterSessionEnd()
> >
> https://maven.apache.org/ref/3.8.4/maven-core/apidocs/index.html?org/apache/m
I can imaging to utilize afterSessionEnd()
https://maven.apache.org/ref/3.8.4/maven-core/apidocs/index.html?org/apache/maven/AbstractMavenLifecycleParticipant.html
Maybe this is the way to do it in a clear way via Maven Extensions, see
This is the implementation in maven-deploy-plugin
https://github.com/apache/maven-deploy-plugin/blob/36a2030c8851e21cd1e0bec01c3cea4dc6055a48/src/main/java/org/apache/maven/plugins/deploy/DeployMojo.java#L180
It is caching the objects of ProjectDeployerRequest and called via
maven-artifact.
I can
the CI system
> you use provides here.
>
>
> su 6. helmik. 2022 klo 14.08 Tibor Digana (tibordig...@apache.org)
> kirjoitti:
>
> > Alexander, all I wanted to say is to discuss the xxxAtEnd as a Maven
> > pattern.
> > Is it what we really want to have in Ma
) or making the build falsely report
> success in the end, is a perfectly valid use case. Who would not like to
> have that? Creating a report for all failing tests without cheating the
> build result to be successful would simply be useful.
>
> --
> Alexander Kriegisch
> https://
It is basically the same feature known in the maven-deploy-plugin
https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd
Not sure if the command
mvn deploy -DdeployAtEnd
would fail to deploy dependent modules if the first module fails.
We discussed this feature some
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
It is disabled by default, see
http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#enableProcessChecker
For more info see
https://maven.apache.org/surefire/maven-surefire-plugin/examples/shutdown.html
We wrote the reasons why the parameter is disabled. Basically the Java GC
ers, OSGi
> bundles or JPMS for that matter. Only with shared classpath junit
> “deployment”
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> ____
> Von: Tibor Digana
> Gesendet: Sunday, July 4, 2021 10:19:45 PM
> An: Maven Users List
>
thoughts. Would it be worthwhile for me to construct and
> share a minimal concrete example to motivate this discussion? It's not
> clear to me that you're open to the possibility that I'm describing a
> reasonable use case here.
>
> On Thu, Jul 8, 2021 at 4:06 PM Tibor Digana
rete example to motivate this discussion? It's not
> clear to me that you're open to the possibility that I'm describing a
> reasonable use case here.
>
> On Thu, Jul 8, 2021 at 4:06 PM Tibor Digana
> wrote:
>
> > The tests are dedicated to the module sources and not to t
The tests are dedicated to the module sources and not to the other module/s.
They were not designed to be inherited and it is logical because unit tests
have to test a small unit code where the unit is a method, class or a
module.
Integration tests are used to test the whole application which is a
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
I did not have time to read it all but I have to say that even the first
point is bad.
Many people want to share test JAR as they initially think it is a good
idea. And then the problems would come.
sharing stubs? This domain/project may not fit to other domain/project, and
it creates dangerous
Our users should read the documentations.
Let's start with the list of Maven Plugins where you can select the one you
need.
https://maven.apache.org/plugins/index.html
Then you click on a plugin named "surefire"
https://maven.apache.org/surefire/maven-surefire-plugin/
and then navigate to the
ioned behaviour?
> Maybe a screenshot of me "diffing" the two JARs before and after
> relocation? I am willing to provide any kind of information which makes
> someone engange in investigating and finally answering my question. Just
> kindly let me know how to do it right this
These Apache developers work with Jira based on objective materials
attached to Jira, like a reproducible project provided by you on Github or
a provided POM.
Then they will take care especially regarding the maven-shade-plugin they
want to improve this plugin, and there was a big effort given to
If two plugins with the same phase appear in the build section of one POM,
then their order matters.
If they split in build and a profile, then the order is not guaranteed
because there are no in one XML section and so the order cannot be
determined.
This might be possible in Maven 5. Let's ask
> On Tue, 13 Apr 2021 at 00:40, Tibor Digana wrote:
> >
> > Hi,
> >
> > threadCountSuites is related to JUnit4 Suite, see this:
> > https://github.com/junit-team/junit4/wiki/Aggregating-tests-in-suites
> >
> > threadCountClasses is related to the typic
DAG of the POM.
I am using IntelliJ IDEA for such things but you can also use
maven-dependency-plugin which prints the dependencies in the console.
On Tue, Apr 13, 2021 at 1:26 PM Delany wrote:
> Hi
>
> How can I get a DAG of the build?
> I want to see how projects are being scheduled in a
There are 3 suites in my example, so set threadCountSuites=3.
On Tue, Apr 13, 2021 at 9:39 AM Tibor Digana wrote:
> Hi,
>
> threadCountSuites is related to JUnit4 Suite, see this:
> https://github.com/junit-team/junit4/wiki/Aggregating-tests-in-suites
>
> threadCount
Hi,
threadCountSuites is related to JUnit4 Suite, see this:
https://github.com/junit-team/junit4/wiki/Aggregating-tests-in-suites
threadCountClasses is related to the typical classes, see this example:
https://github.com/junit-team/junit4/wiki/Assertions
Parallel packages do not exist, but you
Milestone means "work in progress" and if you are continuously breaking
backwards compatibility, you can do it in multiple milestones. It does not
make sense to release multiple release versions because it's risky for
users. This email has convinced me to publish a pull request with changes
shortly, the Maven 3.7.0 had the Jira issue, and I think resolved it, with
bumped versions of default plugins to the most recent ones.
We stopped 3.7.0 and we are developing 4.0.0 now.
T
On Sun, Mar 7, 2021 at 10:58 PM Greg Chabala wrote:
> You're taking the discussion to a place about building
My plan is to run these serially for local development and in parallel for
> TeamCity, and for TeamCity I think it will pick out the logs using flowId,
> so hopefully that will work.
>
> From: Tibor Digana
> Date: Wednesday, February 17, 2021 at 2:19 AM
> To: Maven Users List
In case of combining JUnit5 and Surefire/Failsafe, the configuration
parameters e.g. "parallel" and "threadCountClasses" are not bound to the
native JUnit parameters "junit.jupiter.execution.parallel.enabled" because
it was an agreement between Maven/JUnit teams and the solution became "by
Hi Mukul,
Sorry for my late reply.
I am checking pending emails.
Usually these errors appear in the test itself or the *libraries*.
As for instance, we found out that a Spring's library is implementing Kafka
stuff calling the "Runtime.getRuntime().halt( )".
The same bad thing is to call the
hanism for this out of the box
> then it would be highly desirable for it to do so based on the reasons
> outlined; of course, if the fork mechanism already supports doing this then
> it would be great to hear how to configure Surefire in order to get this
> behaviour.
>
> Cheers,
>
&g
You use jdk11. The jpms was activated. Deactivate it with the workaround,
config param "useModulePath" set to "false".
Dňa ne 5. 7. 2020, 15:27 Tibor Digana napísal(a):
> We do not provide a support. See the message properly. The test reports
> and dump files.
>
&g
We do not provide a support. See the message properly. The test reports and
dump files.
Dňa st 1. 7. 2020, 7:09 Mukul Gandhi napísal(a):
> Hi all,
> I've been facing some problem during last few weeks, when using the
> 'mvn clean test' command to run unit tests within my Maven project. At
Hi Martin,
Can you be more concrete with your business expectations?
What logger, what kind of notations about forked JVM id you want to express
in the logs or somewhere else?
Maybe you are not aware of new features in Surefire and Failsafe, but we
introduced Extensions API in 3.0.0-M4.
This way
lex
>
> Пятница, 3 июля 2020, 17:40 +03:00 от Tibor Digana >:
>
> Hi Alex,
>
> This is the documentation regarding this topic
> https://maven.apache.org/surefire/maven-surefire-plugin/examples/jpms.html
> and you can see the links with the integration tests for TestNG, JU
Hi Alex,
This is the documentation regarding this topic
https://maven.apache.org/surefire/maven-surefire-plugin/examples/jpms.html
and you can see the links with the integration tests for TestNG, JUnit4 and
JUnit5.
These tests use JPMS in main and tests as well. You should be able to
access
Hi Nigel,
I wrote a project for you
https://github.com/Tibor17/pojo-testing
It is related to the JUnit POJO testing with Maven Failsafe Plugin.
I guess you did not use the expected postfix. That's why there were 0 tests
to run.
Additionally, README file shows the command line example with
>> we started seeing Surefire JVM fork crashes on various Windows 10
workstations when Jansi was active
Can you show me the log how it crashed, and maybe the dump file from
target/surefire-reports?
On Sun, Jun 28, 2020 at 7:29 PM Falko Modler wrote:
> Hi everyone!
>
> I recently ran into
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 3.0.0-M5.
The release contains 40 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 emits a different exception than with 2.22.2 or running in IDE.
> 2.22.2 emits an IllegalStateException with root
> NoSuchBeanDefinitionException but per below M5 emits NoClassDefFoundError.
> Is this ok because you changed something locally or is this a concern?
>
>
> On Sat, Jun
We have changed the resolution of junit5 engines 2 times.
Now I have got the result with 3.0.0-M5. I think it is what you expect:
[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
surefire-no-build-fail ---
[INFO]
[INFO] ---
[INFO]
Can you upload the project, dump file and log to the gist?
I am sure it has nothing to do with the spring.
run with:
mvn test -X -e
On Sat, Jun 13, 2020 at 12:15 AM Jeff Jensen <
jeffjen...@upstairstechnology.com> wrote:
> I looked for this issue in JIRA but haven't found anything yet. Anyone
>
Enrico is right.
Surefire does NOT execute 3 Maven modules in parallel.
Opposite!
One module executes Surefire which divides the test into 3 additional
JVMs and the Surefire (module) is waiting for their completion.
On Thu, Apr 9, 2020 at 1:09 PM Debraj Manna wrote:
>
> Hi
>
> I am reading the
Enable the debug logs in Maven (i.e. mvn -X install) and read the logs
around when Downloading...
You may find the root cause this way.
T
On Thu, Mar 19, 2020 at 12:53 PM Robert Manikonda
wrote:
> Hi
> Please check the attached error and im unable to build maven project
>
> Thanks
>
> Br//
>
The TestReporter is not supported yet.
Currently, in M5, we are fixing the process communication via pipes and TCP.
Then we will work on this issue in M6 as well.
Meanwhile please use SLF4J logger or another one.
On Wed, Jan 15, 2020 at 8:45 AM Knoche, Heinz
wrote:
> I uploaded this simple
> is
> reached?
>
> On Mon, Dec 9, 2019 at 4:38 PM Tibor Digana
> wrote:
>
> > fixed typo:If your Jenkins sends SIGKILL to the Maven process then
> enable
> > the process checker, see more details in the documentaion:
> >
> >
> http://maven.ap
Hi Jeronimo,
The old version of Surefire and Failsafe required to have the Junit5 engine
in the test dependency.
But you do not have to declare it if you use the version 3.0.0-M4.
It's enough to have only Junit Jupiter API in the test dependency.
The plugin will find out the engine from Junit5.
-mojo.html#enableProcessChecker
On Mon, Dec 9, 2019 at 12:01 PM Tibor Digana wrote:
> Hi Debraj,
>
> >> to fail the build immediately when timeout is reached
>
> This feature exists for years:
>
> http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#fo
ely when timeout is reached and in other failure cases fail
> in the end. I am using Jenkins so here fail-on-end is set to true. Is it
> possible to do this?
>
>
> On Fri, 22 Nov 2019, 02:51 Tibor Digana, wrote:
>
> > Hi Debraj,
> >
> > It's over one month when
Hi Debraj,
It's over one month when you wrote this email.
How did you solve this issue, did you find the real root cause?
Let us know how you are doing, thx!
btw, we released the new version 3.0.0-M4 in Nov/17.
Cheers
Tibor17
On Thu, Oct 3, 2019 at 2:49 PM Debraj Manna
wrote:
> Sometimes I
Hi John,
Have you used the version 3.0.0-M4?
There were important fixes for Java 11/Linux (alt. Docker).
The message "The forked VM terminated without properly saying goodbye." is
too general error message.
Can you post the configuration of the plugin with the latest version in
your POM including
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 3.0.0-M4.
The release contains 43 bug fixes.
Again we received contributions from the community in form of bug reports
and bug fixes.
Thank you and keep them coming!
Hi Stephen,
You reported issues against Surefire and modular path. Since you also have
experiences with modular paths I would like to ask you about the CLI used
in Surefire and Failsafe.
Are you facing more needs to customize this CLI with Java modules?
Maybe you are facing more alternatives. You
Hi,
There are altogether 43 bugfixes in the JIRA.
I would like to start a new release Vote today evening.
Kind regards,
Tibor17
:24 PM Ryan Thomas wrote:
> Hi Tibor,
>
> That would be great. How would I go about doing that?
>
> *Ryan Thomas*
> *Sr. QA Engineer*
> BrainPOP
>
>
> On Mon, Nov 11, 2019 at 2:57 PM Tibor Digana
> wrote:
>
>> yes, i saw the code. So it is reproducible
d as skipped,
> but the getTestResultType check from the list or tries incorrectly reported
> it as a Failure. So it goes through the incorrect reporting type for the
> XML output, hence why it contains the system-out, and system-err sub
> elements
>
> Thank you for taking the ti
Hi Ryan,
I found this issue already reported in JIRA.
https://issues.apache.org/jira/browse/SUREFIRE-1556
There is no fix because we have not received any reproducible project.
IMO this section should not exist in the XML:
< message="This is a bug">
It looks like the
Hi Jamin,
Pls open a JIRA ticket and keep this discussion open.
Thx!
On Sat, Nov 2, 2019 at 7:17 PM Jamin Collins
wrote:
> I'm running into an issue with build-helper-maven-plugin in a project
> I'm attempting to build.
>
> I was previously (roughly about a year ago) able to build this project
t; RunListener so that I can call pleaseStop() from the listener when the
> timeout of a test expires? Is there any example code I can refer to?
>
> I am using Junit 4.12 and maven-surefire 2.22.2
>
> On Sat, Oct 5, 2019 at 6:27 PM Tibor Digana
> wrote:
>
> > Some users m
ion but it must be
> built in cause of nowdays needs (release, js build, cloud deployment,
> gh-pages, etc...)
>
> Le sam. 5 oct. 2019 à 15:18, Tibor Digana a
> écrit :
>
> > I have never seen a documentation for ship-maven-plugin.
> > It could be a good motivati
n both at once typically) but I disagree with last parts "skip the
> > test"
> > > - maven is also there to enforce tests as a good practise, if you don't
> > > automatically test it you can configure maven to skip tests for the
> > release
> > > but i
>
> 1. I get your testStarted part but it is still not clear to me about
> calling 'pleaseStop() on the listener'. Are you suggesting to add this in
> each of my test classes? Can you explain this a bit more?
>
> On Fri, Oct 4, 2019 at 11:52 PM Tibor Digana
> wrote:
>
> calling 'pleaseStop() on the listener'. Are you suggesting to add this in
> each of my test classes? Can you explain this a bit more?
>
> On Fri, Oct 4, 2019 at 11:52 PM Tibor Digana
> wrote:
>
> > Hi Debraj,
> >
> > It depends on your requirements.
> >
&g
t me if I have misunderstood anything.
>
>
>
> On Fri, Oct 4, 2019 at 3:18 PM Debraj Manna
> wrote:
>
> > Yeah sure ... thanks.
> >
> > On Thu, Oct 3, 2019 at 7:50 PM Tibor Digana
> > wrote:
> >
> >> Hi Debraj,
> >>
> >>
d Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le v
It would be worth to add a new goal called "release" to the
maven-release-plugin which merges "prepare" and "perform".
We developers in companies use both goals prepare and perform immediately
together because for us two goals do not make sense.
Two goals make sense for those who can wait days to
Hi Debraj,
There is nice technical idea from Enrico.
If you apply it and you are convinced that it would work properly for all
the Java community, feel free to show it and we can discuss it on how we
would adopt your solution in Surefire project.
Cheers
Tibor17
On Thu, Oct 3, 2019 at 2:49 PM
Hi Francois and Dan,
I understood it the same way as Francois mentioned. Not sure if NN in the
format "artifactId-version-timestamp-NN" is a bug. Who cares is probably
someone who downloads the artifact manually, maybe the QA.
Also downloading the artifacts from Nexus never was so trivial for QA
Dan, you know how we solved this problem, we wrote Jenkinsfile with
interactive GUI. The release manager of QA filled out the items in web GUI
of Jenkins, means Version, Deployment IP in QA machines and some build
options. Simply we moved the responsibility to the person who argued the
most about
I think the timestamp after "-SNAPSHOT" is something which should not be
customized as by Maven design.
The version before "-SNAPSHOT"is something which is up to you.
Some companies customize the version to *--* executed on Jenkins CI.
If it is a problem in multimodule project with messy timestamp
Hi John,
See this page, the toolchain and JAXB and much more is decribed there
https://maven.apache.org/surefire/maven-surefire-plugin/java9.html
We designed Surefire to understand the compiled sources (src/main/java)
with Java Modularity.
Not the modular test sources. I think we do not have any
gt;> this.
>> > Is there any new way to replace maven components?
>> >
>> > On Wed, Aug 28, 2019 at 11:57 PM Enrico Olivelli
>> > wrote:
>> >
>> > > It may be due to any change regarding jsr 330 like
>> > > ht
Is there any new way to replace maven components?
>> >
>> > On Wed, Aug 28, 2019 at 11:57 PM Enrico Olivelli
>> > wrote:
>> >
>> > > It may be due to any change regarding jsr 330 like
>> > > https://issues.apache.org/jira/plugins
livelli
> wrote:
>
>> It may be due to any change regarding jsr 330 like
>> https://issues.apache.org/jira/plugins/servlet/mobile#issue/MNG-6686
>>
>>
>> I think it is an issue for Idea and not for us.
>> It would be good to have some developer from Jetbrains
tId=16852351=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16852351
>
> I reported to Jetbrains https://youtrack.jetbrains.com/issue/IDEA-215315 <
> https://youtrack.jetbrains.com/issue/IDEA-215315> and is supposed to be
> fixed in 2019.3
>
> > On 28 Aug 2019, a
I used Maven 3.6.2 in the IntelliJ IDEA 2019.2.1 and I found these errors
in the log file:
~/.IntelliJIdea2019.2/system/log/idea.log
2019-08-28 21:31:32,072 [255937677] ERROR - #org.jetbrains.idea.maven
- com.google.inject.CreationException: Unable to create injector, see the
following
Hi Dirk,
This project is not worth a plugin, it is a pure converter of single class.
In this case it is legal to adopt this code according to the license.
Anyway the Maven is not the OSGi. The OSGi is not our key API we deliver to
our customers.
We have to save our energy on what makes Maven The
There's very good BND plugin org.apache.felix:maven-bundle-plugin.
+1 to retire and delete old https://maven.apache.org/shared/maven-osgi/
Cheers
Tibor17
On Fri, Aug 23, 2019 at 3:17 PM Robert Scholte wrote:
> Hi,
>
> The Apache Maven project consist of about 90 (sub)projects. Due to the
>
Hi Walid,
You are writing right on the time!
We could not make a new release because we interrupted important fix in
Surefire and we concentrated on:
+ build process issues
+ new Maven release 3.6.2
+ Resolver 1.4.1
+ JDK 1.8 vs Archetype 3.1.1 and 3.1.2
We have finished all these activities and
The Apache Maven team is pleased to announce the release of the Apache
Maven Archetype Plugin, version 3.1.2.
The Archetype Plugin allows the user to create a Maven project from an
existing template called an archetype. It also allows the user to create an
archetype from an existing project.
Hi,
Just an announcement.
Today I would like to release Archetype 3.1.2.
https://issues.apache.org/jira/projects/ARCHETYPE/versions/12345957
Cheers
Tibor17
The Apache Maven team is pleased to announce the release of the Maven
Resolver 1.4.1.
https://maven.apache.org/resolver/
Release Notes - Maven Resolver - Version 1.4.1
** Task
* [MRESOLVER-92] - Revert MRESOLVER-7
Enjoy,
-The Apache Maven team
+1
On Wed, Aug 7, 2019 at 9:13 PM Robert Scholte wrote:
> 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 these projects,
> including our
Ben, you have to delete the remote Tag from Git if you want to repeat the
release of the same version.
It happened many times to me and my colleagues that we had to delete the
tag for whatever reason, e.g. wrong SCM credentials or connectivity
problems.
So it was usual that we deleted the tag,
Hello Moina,
I have reported this issue in JIRA
https://issues.apache.org/jira/browse/SUREFIRE-1684
Cheers
Tibor17
On Fri, Jul 19, 2019 at 2:26 PM Moina Farheen
wrote:
> Hi,
>
> I am a beginner and just started to learn maven for my project. I was
> reading about surefire plugin on the site
btw, you did not attach the image.
You mean this?
(You can open a Jira ticket and fix in PR on
github.com/apache/maven-surefire)
The Surefire Report Plugin only has one goal (the other is a workaround):
- surefire-report:failsafe-report-only
Asking Andrew. Maven is still using the old version 2.12.4 but this will be
changed, see https://issues.apache.org/jira/browse/MNG-6169
On Sat, Jun 29, 2019 at 5:05 PM Thomas Broyer wrote:
> On Sat, Jun 29, 2019 at 4:50 PM Tibor Digana
> wrote:
>
> > Where do we use dependen
Where do we use dependency with groupId "org.codehaus.mojo"?
Thx
Tibor
On Sat, Jun 29, 2019 at 3:18 PM Thomas Broyer wrote:
> Artifacts using the org.codehaus.mojo groupId does not mean they "come
> from" the mojo.codehaus.org forge.
>
> All the (maintained) plugins and libraries have found a
1 - 100 of 150 matches
Mail list logo
