Re: project & checkstyle update
Go ahead ! On 16/05/2021 17:45, Stefan Seelmann wrote: On 5/11/21 4:06 AM, Emmanuel Lécharny wrote: I will commit my changes in project-45 and checkstyle-configuration-2.0.1 if no one objects. I'd release the checkstyle-configuration-2.0.1 or to be more precise the buildtools project, ok? - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org -- *Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE T. +33 (0)4 89 97 36 50 P. +33 (0)6 08 33 32 61 emmanuel.lecha...@busit.com https://www.busit.com/ - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
Re: project & checkstyle update
On 5/11/21 4:06 AM, Emmanuel Lécharny wrote: > I will commit my changes in project-45 and > checkstyle-configuration-2.0.1 if no one objects. I'd release the checkstyle-configuration-2.0.1 or to be more precise the buildtools project, ok? - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
Re: project & checkstyle update
Many thanks, Stefan !
On 13/05/2021 09:42, Stefan Seelmann wrote:
Committed and pushed, all issues are resolved, OSGi tests work again.
On 5/13/21 9:20 AM, Emmanuel Lécharny wrote:
OH, GREAT !
Please commit, I'll check for the missing deps.
On 13/05/2021 08:46, Stefan Seelmann wrote:
I got them to run, but some fail because of unresolved requirements. Let
me know if I should commit it and investigate further:
diff --git a/osgi-integ/pom.xml b/osgi-integ/pom.xml
index f993450965..527b31c51f 100644
--- a/osgi-integ/pom.xml
+++ b/osgi-integ/pom.xml
@@ -249,8 +249,8 @@
- org.junit.jupiter
- junit-jupiter-engine
+ junit
+ junit
test
@@ -312,6 +312,7 @@
runtime
${project.build.directory}/test-classes/deps.txt
+
org.junit.jupiter,org.junit.platform,org.apiguardian
@@ -327,6 +328,13 @@
1
1
+
+
+ org.apache.maven.surefire
+ surefire-junit47
+ 3.0.0-M3
+
+
On 5/13/21 8:13 AM, Emmanuel Lécharny wrote:
The weird thing is that there is only one difference between the working
osgi-integ version and the not running one:
org.junit.jupiter
junit-jupiter-engine
test
replaced
junit
junit
test
If I roll back this change, I get the same result.
So it must be something on the parent pom.
On 13/05/2021 07:45, Emmanuel Lécharny wrote:
Ok, I know that the OSGi tests were running on commit
2ec1117fec41919a68d04ba3a51724562e3b46f8 ("Updating Jetty to
9.4.34.v20201102", made by Colm on Nov 6th) and stopped being run with
commit 04212704be56cdcb750ca571081a5e55fa03bfb8 ("Started the
migration to Junit 5", made by me on Dec, 23th).
On 12/05/2021 09:18, Emmanuel Lécharny wrote:
Will analyse further tonite.
FTR I have added a test class, which get executed, which means the
tests are somehow visible. May be an issue with the
RunWith(PaxExam.class) ?
On 12/05/2021 06:47, Stefan Seelmann wrote:
On 5/11/21 11:45 PM, Emmanuel Lécharny wrote:
And after going back to the existing project (44) parent, I can't
have
the osgi-integ test run at all :
[INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
apacheds-osgi-integ ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
...
This is more than bizarre...
Same happens currently in master e.g. on Jenkins. I assume we need to
add the junit-vintage dependency.
-
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
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecha...@busit.com https://www.busit.com/
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
Re: project & checkstyle update
Committed and pushed, all issues are resolved, OSGi tests work again.
On 5/13/21 9:20 AM, Emmanuel Lécharny wrote:
> OH, GREAT !
>
> Please commit, I'll check for the missing deps.
>
>
> On 13/05/2021 08:46, Stefan Seelmann wrote:
>> I got them to run, but some fail because of unresolved requirements. Let
>> me know if I should commit it and investigate further:
>>
>> diff --git a/osgi-integ/pom.xml b/osgi-integ/pom.xml
>> index f993450965..527b31c51f 100644
>> --- a/osgi-integ/pom.xml
>> +++ b/osgi-integ/pom.xml
>> @@ -249,8 +249,8 @@
>>
>>
>>
>> - org.junit.jupiter
>> - junit-jupiter-engine
>> + junit
>> + junit
>> test
>>
>>
>> @@ -312,6 +312,7 @@
>>
>> runtime
>>
>> ${project.build.directory}/test-classes/deps.txt
>> +
>> org.junit.jupiter,org.junit.platform,org.apiguardian
>>
>>
>>
>>
>> @@ -327,6 +328,13 @@
>>
>> 1
>> 1
>>
>> +
>> +
>> + org.apache.maven.surefire
>> + surefire-junit47
>> + 3.0.0-M3
>> +
>> +
>>
>>
>>
>>
>>
>> On 5/13/21 8:13 AM, Emmanuel Lécharny wrote:
>>> The weird thing is that there is only one difference between the working
>>> osgi-integ version and the not running one:
>>>
>>>
>>> org.junit.jupiter
>>> junit-jupiter-engine
>>> test
>>>
>>>
>>> replaced
>>>
>>>
>>> junit
>>> junit
>>> test
>>>
>>>
>>>
>>> If I roll back this change, I get the same result.
>>>
>>> So it must be something on the parent pom.
>>>
>>> On 13/05/2021 07:45, Emmanuel Lécharny wrote:
Ok, I know that the OSGi tests were running on commit
2ec1117fec41919a68d04ba3a51724562e3b46f8 ("Updating Jetty to
9.4.34.v20201102", made by Colm on Nov 6th) and stopped being run with
commit 04212704be56cdcb750ca571081a5e55fa03bfb8 ("Started the
migration to Junit 5", made by me on Dec, 23th).
On 12/05/2021 09:18, Emmanuel Lécharny wrote:
> Will analyse further tonite.
>
> FTR I have added a test class, which get executed, which means the
> tests are somehow visible. May be an issue with the
> RunWith(PaxExam.class) ?
>
> On 12/05/2021 06:47, Stefan Seelmann wrote:
>> On 5/11/21 11:45 PM, Emmanuel Lécharny wrote:
>>> And after going back to the existing project (44) parent, I can't
>>> have
>>> the osgi-integ test run at all :
>>>
>>> [INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
>>> apacheds-osgi-integ ---
>>> [INFO]
>>> [INFO] ---
>>> [INFO] T E S T S
>>> [INFO] ---
>>> [INFO]
>>> [INFO] Results:
>>> [INFO]
>>> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>>> [INFO]
>>> ...
>>>
>>>
>>> This is more than bizarre...
>>
>> Same happens currently in master e.g. on Jenkins. I assume we need to
>> add the junit-vintage dependency.
>>
>>
>> -
>> 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
Re: project & checkstyle update
On 13/05/2021 09:02, Stefan Seelmann wrote: apacheds-core-annotation and apacheds-server-annotation still have dependencies to junit4 (org.junit.runner package) This is probably something to remove... - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
Re: project & checkstyle update
OH, GREAT !
Please commit, I'll check for the missing deps.
On 13/05/2021 08:46, Stefan Seelmann wrote:
I got them to run, but some fail because of unresolved requirements. Let
me know if I should commit it and investigate further:
diff --git a/osgi-integ/pom.xml b/osgi-integ/pom.xml
index f993450965..527b31c51f 100644
--- a/osgi-integ/pom.xml
+++ b/osgi-integ/pom.xml
@@ -249,8 +249,8 @@
- org.junit.jupiter
- junit-jupiter-engine
+ junit
+ junit
test
@@ -312,6 +312,7 @@
runtime
${project.build.directory}/test-classes/deps.txt
+
org.junit.jupiter,org.junit.platform,org.apiguardian
@@ -327,6 +328,13 @@
1
1
+
+
+ org.apache.maven.surefire
+ surefire-junit47
+ 3.0.0-M3
+
+
On 5/13/21 8:13 AM, Emmanuel Lécharny wrote:
The weird thing is that there is only one difference between the working
osgi-integ version and the not running one:
org.junit.jupiter
junit-jupiter-engine
test
replaced
junit
junit
test
If I roll back this change, I get the same result.
So it must be something on the parent pom.
On 13/05/2021 07:45, Emmanuel Lécharny wrote:
Ok, I know that the OSGi tests were running on commit
2ec1117fec41919a68d04ba3a51724562e3b46f8 ("Updating Jetty to
9.4.34.v20201102", made by Colm on Nov 6th) and stopped being run with
commit 04212704be56cdcb750ca571081a5e55fa03bfb8 ("Started the
migration to Junit 5", made by me on Dec, 23th).
On 12/05/2021 09:18, Emmanuel Lécharny wrote:
Will analyse further tonite.
FTR I have added a test class, which get executed, which means the
tests are somehow visible. May be an issue with the
RunWith(PaxExam.class) ?
On 12/05/2021 06:47, Stefan Seelmann wrote:
On 5/11/21 11:45 PM, Emmanuel Lécharny wrote:
And after going back to the existing project (44) parent, I can't have
the osgi-integ test run at all :
[INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
apacheds-osgi-integ ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
...
This is more than bizarre...
Same happens currently in master e.g. on Jenkins. I assume we need to
add the junit-vintage dependency.
-
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
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecha...@busit.com https://www.busit.com/
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
Re: project & checkstyle update
apacheds-core-annotation and apacheds-server-annotation still have
dependencies to junit4 (org.junit.runner package)
On 5/13/21 8:46 AM, Stefan Seelmann wrote:
> I got them to run, but some fail because of unresolved requirements. Let
> me know if I should commit it and investigate further:
>
> diff --git a/osgi-integ/pom.xml b/osgi-integ/pom.xml
> index f993450965..527b31c51f 100644
> --- a/osgi-integ/pom.xml
> +++ b/osgi-integ/pom.xml
> @@ -249,8 +249,8 @@
>
>
>
> - org.junit.jupiter
> - junit-jupiter-engine
> + junit
> + junit
>test
>
>
> @@ -312,6 +312,7 @@
>
>runtime
>
> ${project.build.directory}/test-classes/deps.txt
> +
> org.junit.jupiter,org.junit.platform,org.apiguardian
>
>
>
> @@ -327,6 +328,13 @@
>
> 1
> 1
>
> +
> +
> + org.apache.maven.surefire
> + surefire-junit47
> + 3.0.0-M3
> +
> +
>
>
>
>
>
> On 5/13/21 8:13 AM, Emmanuel Lécharny wrote:
>> The weird thing is that there is only one difference between the working
>> osgi-integ version and the not running one:
>>
>>
>> org.junit.jupiter
>> junit-jupiter-engine
>> test
>>
>>
>> replaced
>>
>>
>> junit
>> junit
>> test
>>
>>
>>
>> If I roll back this change, I get the same result.
>>
>> So it must be something on the parent pom.
>>
>> On 13/05/2021 07:45, Emmanuel Lécharny wrote:
>>> Ok, I know that the OSGi tests were running on commit
>>> 2ec1117fec41919a68d04ba3a51724562e3b46f8 ("Updating Jetty to
>>> 9.4.34.v20201102", made by Colm on Nov 6th) and stopped being run with
>>> commit 04212704be56cdcb750ca571081a5e55fa03bfb8 ("Started the
>>> migration to Junit 5", made by me on Dec, 23th).
>>>
>>>
>>>
>>> On 12/05/2021 09:18, Emmanuel Lécharny wrote:
Will analyse further tonite.
FTR I have added a test class, which get executed, which means the
tests are somehow visible. May be an issue with the
RunWith(PaxExam.class) ?
On 12/05/2021 06:47, Stefan Seelmann wrote:
> On 5/11/21 11:45 PM, Emmanuel Lécharny wrote:
>> And after going back to the existing project (44) parent, I can't have
>> the osgi-integ test run at all :
>>
>> [INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
>> apacheds-osgi-integ ---
>> [INFO]
>> [INFO] ---
>> [INFO] T E S T S
>> [INFO] ---
>> [INFO]
>> [INFO] Results:
>> [INFO]
>> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>> [INFO]
>> ...
>>
>>
>> This is more than bizarre...
>
> Same happens currently in master e.g. on Jenkins. I assume we need to
> add the junit-vintage dependency.
>
>
> -
> 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
Re: project & checkstyle update
I got them to run, but some fail because of unresolved requirements. Let
me know if I should commit it and investigate further:
diff --git a/osgi-integ/pom.xml b/osgi-integ/pom.xml
index f993450965..527b31c51f 100644
--- a/osgi-integ/pom.xml
+++ b/osgi-integ/pom.xml
@@ -249,8 +249,8 @@
- org.junit.jupiter
- junit-jupiter-engine
+ junit
+ junit
test
@@ -312,6 +312,7 @@
runtime
${project.build.directory}/test-classes/deps.txt
+
org.junit.jupiter,org.junit.platform,org.apiguardian
@@ -327,6 +328,13 @@
1
1
+
+
+ org.apache.maven.surefire
+ surefire-junit47
+ 3.0.0-M3
+
+
On 5/13/21 8:13 AM, Emmanuel Lécharny wrote:
> The weird thing is that there is only one difference between the working
> osgi-integ version and the not running one:
>
>
> org.junit.jupiter
> junit-jupiter-engine
> test
>
>
> replaced
>
>
> junit
> junit
> test
>
>
>
> If I roll back this change, I get the same result.
>
> So it must be something on the parent pom.
>
> On 13/05/2021 07:45, Emmanuel Lécharny wrote:
>> Ok, I know that the OSGi tests were running on commit
>> 2ec1117fec41919a68d04ba3a51724562e3b46f8 ("Updating Jetty to
>> 9.4.34.v20201102", made by Colm on Nov 6th) and stopped being run with
>> commit 04212704be56cdcb750ca571081a5e55fa03bfb8 ("Started the
>> migration to Junit 5", made by me on Dec, 23th).
>>
>>
>>
>> On 12/05/2021 09:18, Emmanuel Lécharny wrote:
>>> Will analyse further tonite.
>>>
>>> FTR I have added a test class, which get executed, which means the
>>> tests are somehow visible. May be an issue with the
>>> RunWith(PaxExam.class) ?
>>>
>>> On 12/05/2021 06:47, Stefan Seelmann wrote:
On 5/11/21 11:45 PM, Emmanuel Lécharny wrote:
> And after going back to the existing project (44) parent, I can't have
> the osgi-integ test run at all :
>
> [INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
> apacheds-osgi-integ ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> ...
>
>
> This is more than bizarre...
Same happens currently in master e.g. on Jenkins. I assume we need to
add the junit-vintage dependency.
-
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
Re: project & checkstyle update
The weird thing is that there is only one difference between the working
osgi-integ version and the not running one:
org.junit.jupiter
junit-jupiter-engine
test
replaced
junit
junit
test
If I roll back this change, I get the same result.
So it must be something on the parent pom.
On 13/05/2021 07:45, Emmanuel Lécharny wrote:
Ok, I know that the OSGi tests were running on commit
2ec1117fec41919a68d04ba3a51724562e3b46f8 ("Updating Jetty to
9.4.34.v20201102", made by Colm on Nov 6th) and stopped being run with
commit 04212704be56cdcb750ca571081a5e55fa03bfb8 ("Started the migration
to Junit 5", made by me on Dec, 23th).
On 12/05/2021 09:18, Emmanuel Lécharny wrote:
Will analyse further tonite.
FTR I have added a test class, which get executed, which means the
tests are somehow visible. May be an issue with the
RunWith(PaxExam.class) ?
On 12/05/2021 06:47, Stefan Seelmann wrote:
On 5/11/21 11:45 PM, Emmanuel Lécharny wrote:
And after going back to the existing project (44) parent, I can't have
the osgi-integ test run at all :
[INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
apacheds-osgi-integ ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
...
This is more than bizarre...
Same happens currently in master e.g. on Jenkins. I assume we need to
add the junit-vintage dependency.
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecha...@busit.com https://www.busit.com/
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
Re: project & checkstyle update
Ok, I know that the OSGi tests were running on commit
2ec1117fec41919a68d04ba3a51724562e3b46f8 ("Updating Jetty to
9.4.34.v20201102", made by Colm on Nov 6th) and stopped being run with
commit 04212704be56cdcb750ca571081a5e55fa03bfb8 ("Started the migration
to Junit 5", made by me on Dec, 23th).
On 12/05/2021 09:18, Emmanuel Lécharny wrote:
Will analyse further tonite.
FTR I have added a test class, which get executed, which means the tests
are somehow visible. May be an issue with the RunWith(PaxExam.class) ?
On 12/05/2021 06:47, Stefan Seelmann wrote:
On 5/11/21 11:45 PM, Emmanuel Lécharny wrote:
And after going back to the existing project (44) parent, I can't have
the osgi-integ test run at all :
[INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @
apacheds-osgi-integ ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
...
This is more than bizarre...
Same happens currently in master e.g. on Jenkins. I assume we need to
add the junit-vintage dependency.
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecha...@busit.com https://www.busit.com/
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
Re: project & checkstyle update
Will analyse further tonite. FTR I have added a test class, which get executed, which means the tests are somehow visible. May be an issue with the RunWith(PaxExam.class) ? On 12/05/2021 06:47, Stefan Seelmann wrote: On 5/11/21 11:45 PM, Emmanuel Lécharny wrote: And after going back to the existing project (44) parent, I can't have the osgi-integ test run at all : [INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @ apacheds-osgi-integ --- [INFO] [INFO] --- [INFO] T E S T S [INFO] --- [INFO] [INFO] Results: [INFO] [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] ... This is more than bizarre... Same happens currently in master e.g. on Jenkins. I assume we need to add the junit-vintage dependency. - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org -- *Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE T. +33 (0)4 89 97 36 50 P. +33 (0)6 08 33 32 61 emmanuel.lecha...@busit.com https://www.busit.com/ - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
Re: project & checkstyle update
On 5/11/21 11:45 PM, Emmanuel Lécharny wrote: > And after going back to the existing project (44) parent, I can't have > the osgi-integ test run at all : > > [INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @ > apacheds-osgi-integ --- > [INFO] > [INFO] --- > [INFO] T E S T S > [INFO] --- > [INFO] > [INFO] Results: > [INFO] > [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > ... > > > This is more than bizarre... Same happens currently in master e.g. on Jenkins. I assume we need to add the junit-vintage dependency. - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
Re: project & checkstyle update
And after going back to the existing project (44) parent, I can't have the osgi-integ test run at all : [INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @ apacheds-osgi-integ --- [INFO] [INFO] --- [INFO] T E S T S [INFO] --- [INFO] [INFO] Results: [INFO] [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] ... This is more than bizarre... On 11/05/2021 09:40, Emmanuel Lécharny wrote: Ok, i have tried with ApacheDS too, and I have some issues with OSGi tests: [INFO] Running org.apache.directory.server.osgi.integ.ServerInterceptorsAuthNOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerInterceptorsAuthNOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerInterceptorsAuthNOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/apiguardian-api-1.1.0.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerCoreSharedOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerCoreSharedOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerCoreSharedOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/hamcrest-core-1.3.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerServiceBuilderOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerServiceBuilderOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerServiceBuilderOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/apiguardian-api-1.1.0.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerAnnotationsOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerAnnotationsOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerAnnotationsOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/hamcrest-core-1.3.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerJdbmPartitionOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerJdbmPartitionOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerJdbmPartitionOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/hamcrest-core-1.3.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) [ERROR] System Exit has timed out in the forked process 1 log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerProtocolLdapOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerProtocolLdapOsgiTest [ERROR]
Re: project & checkstyle update
Ok, i have tried with ApacheDS too, and I have some issues with OSGi tests: [INFO] Running org.apache.directory.server.osgi.integ.ServerInterceptorsAuthNOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerInterceptorsAuthNOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerInterceptorsAuthNOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/apiguardian-api-1.1.0.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerCoreSharedOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerCoreSharedOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerCoreSharedOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/hamcrest-core-1.3.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerServiceBuilderOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerServiceBuilderOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerServiceBuilderOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/apiguardian-api-1.1.0.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerAnnotationsOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerAnnotationsOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerAnnotationsOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/hamcrest-core-1.3.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerJdbmPartitionOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerJdbmPartitionOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerJdbmPartitionOsgiTest Time elapsed: 0 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/hamcrest-core-1.3.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) [ERROR] System Exit has timed out in the forked process 1 log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. [INFO] Running org.apache.directory.server.osgi.integ.ServerProtocolLdapOsgiTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 s <<< FAILURE! - in org.apache.directory.server.osgi.integ.ServerProtocolLdapOsgiTest [ERROR] org.apache.directory.server.osgi.integ.ServerProtocolLdapOsgiTest Time elapsed: 0.001 s <<< ERROR! org.ops4j.pax.exam.TestContainerException: [file:/Users/elecharny/apacheds/directory-server-M27/osgi-integ/target/dependency/apiguardian-api-1.1.0.jar] is not a valid bundle (bundleSymbolicName and bundleName are null) log4j:WARN No appenders could be found for logger (org.ops4j.pax.exam.spi.DefaultExamSystem). log4j:WARN Please initialize the log4j system properly. log4j:WARN See
Re: project & checkstyle update
On 5/11/21 4:06 AM, Emmanuel Lécharny wrote: > before we cut a LDAP API and Studio release, I have done a few updates > in the 'checkstyle' and 'project' projects. There are a hell of maven > plugin version sthat have changed since the last release. > > I checked with LDAP API and beside an issue with checkstyle ( a property > was not anymorre supported in TreeWalker), the build went fine. > > I will commit my changes in project-45 and > checkstyle-configuration-2.0.1 if no one objects. Sure, go ahead! - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
project & checkstyle update
Hi, before we cut a LDAP API and Studio release, I have done a few updates in the 'checkstyle' and 'project' projects. There are a hell of maven plugin version sthat have changed since the last release. I checked with LDAP API and beside an issue with checkstyle ( a property was not anymorre supported in TreeWalker), the build went fine. I will commit my changes in project-45 and checkstyle-configuration-2.0.1 if no one objects. Thanks ! -- *Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE T. +33 (0)4 89 97 36 50 P. +33 (0)6 08 33 32 61 emmanuel.lecha...@busit.com https://www.busit.com/ - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
