The difference is that the first invocation is just simply wrong. When you call
a mvn lifecycle phase it will run through all prior phases. If you specify 2
lifecycle phase from the same lifecycle (the default cycle) .. you run through
things twice..
E.g.
mvn install
runs
initialize, ..
I thought so too but I have a project where calling mvn clean install
deploy causes Maven to use wrong paths for some modules. I think I
should create bug report for this.
Best,
Oliver
Am 18.09.18 um 00:02 schrieb Marco Schulz:
jupp they have the same result. because. frist both run the clean
jupp they have the same result. because. frist both run the clean lifecycle
then comes the build lifecycle wich step through all phases. install is defined
before deploy. so you don't need to call it when you plan to deploy
keep in mind deploy is a publishing to a remote repository like nexus. y
Hi all,
I stumbled on a strange problem with Maven. Therefore I would like to
know if the following commands should have the same result or not:
1. mvn clean install deploy
2. mvn clean deploy
Best,
Oliver
-
To unsubscribe
Hi,
It seems to be, that surefire and failsafe currently don't work the same.
Because surefire puts jpms modules on module path, but failsafe doesn't. See my
issue here https://issues.apache.org/jira/browse/SUREFIRE-1570
>Понедельник, 17 сентября 2018, 17:35 +03:00 от John Patrick
>:
>
>s
surefire and failsafe plugins appear to work the same
I've had to use the 2.22.0 versions
I defined my plugin in a pluginManagement section and had to add this
${project.custom.failsafe.argLine.jpms}
then in each project I add properties as required like this for
surefire or failsafe depending
