> On May 17, 2021, at 12:26 PM, Stefan Seelmann <m...@stefan-seelmann.de> wrote:
>
> Reminds me of those scenes :)
> https://www.youtube.com/watch?v=w4aLThuU008
> https://www.youtube.com/watch?v=r3FEhHF_fzM
>
>
That’s a good one :-)
> Well, it happens when changing the parent pom to version 45 which
> defines aven-surefire-plugin:3.0.0-M3:
>
> diff --git a/pom.xml b/pom.xml
> index c8a59c0e..b4fc66a3 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -22,7 +22,7 @@
> <parent>
> <groupId>org.apache.directory.project</groupId>
> <artifactId>project</artifactId>
> - <version>35</version>
> + <version>45</version>
> <relativePath />
> </parent>
>
>
>
> On 5/17/21 6:37 PM, Shawn McKinney wrote:
>>
>>> On May 17, 2021, at 10:52 AM, Emmanuel Lécharny <elecha...@gmail.com> wrote:
>>>
>>> On 17/05/2021 15:07, Shawn McKinney wrote:
>>>>> On May 16, 2021, at 8:51 AM, Emmanuel Lécharny <elecha...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi !
>>>>>
>>>>> yesterday, I tried to launch a mvn clean install on fortress-cofre, but
>>>>> it seems there is an issue with a LDAP server that is not available.
>>>>>
>>>>> Should I use one of the QUICKSTART to run the tests ?
>>>>>
>>>> Hi Emmanuel,
>>>> mvn install doesn’t run the tests by design.
>>>
>>> Actually, it does.
>>>
>>
>> You’re saying that mvn projects generally runs the tests on install? No
>> argument there. But, fortress core doesn’t because (rationale) they take
>> too long to run, and (more important) having an environment setup to run
>> them is non trivial.
>>
>> So, the user must invoke by name, e.g.
>>
>> mvn -Dtest=FortressJUnitTest test
>>
>> You already know this as we’ve discussed (debated?) many times, but wanted
>> to point it out in case I’m missing something else.
>>
>>> But, if you want to run them, yes, the docker quickstarts are probably best
>>> because they don’t require installing bins to your machine, other than
>>> docker of course.
>>>
>>> Ok, will follow the guide.
>>>
>>> Thanks Shawn !
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
>> For additional commands, e-mail: dev-h...@directory.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
> For additional commands, e-mail: dev-h...@directory.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
