Can't build XWiki Extension because of Spoon plugin ( error 500 )

Help / Discuss
1

Hello

We are working with XWiki 12.10.4 since few years now, we didn’t really had time to perform the last upgrade so far.

But recently ( 3 days ago ? ) we noticed that the build of our XWiki Extension using as parent parent-platform-distribution 12.10.4 doesn’t works anymore

mvn clean install -q -e
82793 [ERROR] Failed to execute goal fr.inria.gforge.spoon:spoon-maven-plugin:3.4.2:check (spoon-main) on project xwiki-distribution-collaboratory ( it s our extension ): Execution spoon-main of goal fr.inria.gforge.spoon:spoon-maven-plugin:3.4.2:check failed: Plugin fr.inria.gforge.spoon:spoon-maven-plugin:3.4.2 or one of its dependencies could not be resolved: Failed to collect dependencies at fr.inria.gforge.spoon:spoon-maven-plugin:jar:3.4.2 -> fr.inria.gforge.spoon:spoon-core:jar:7.5.0 -> org.eclipse.jdt:org.eclipse.jdt.core:jar:3.16.0 -> org.eclipse.platform:org.eclipse.core.resources:jar:3.12.0 -> org.eclipse.platform:org.eclipse.core.expressions:jar:3.5.100 -> org.eclipse.platform:org.eclipse.core.runtime:jar:3.12.0 -> org.eclipse.platform:org.eclipse.equinox.preferences:jar:3.10.1 -> org.osgi:org.osgi.service.prefs:jar:1.1.1-SNAPSHOT: Failed to read artifact descriptor for org.osgi:org.osgi.service.prefs:jar:1.1.1-SNAPSHOT: Could not transfer artifact org.osgi:org.osgi.service.prefs:pom:1.1.1-SNAPSHOT from/to maven.inria.fr-snapshot (http://maven.inria.fr/artifactory/spoon-public-snapshot/): status code: 500, reason phrase: Internal Server Error (500) -> [Help 1]

So it’s not XWiki fault at all, as you can see http://maven.inria.fr/artifactory/spoon-public-snapshot/ return an error 500 now

Did you encounter this too and is there a work around other that upgrading XWiki to last version ( 15 or 16 ). And can you confirm it still works with last versions of XWiki or maybe they are still using this repo and are broken too ?

I don’t remember if XWiki 12.10 was an LTS, is it possible to have a fix if it’s an easy fix ?

Worst case I will process to upgrade from 12.10 to 15 but it’s a long process.

Thanks for any helps :slight_smile:

Regards,

Axel
Human Brain Project / EBRAINS

2

Yes, quite a few extensions were impacted by this problem.

The most common workaround (to be applied on the extension) is to use the 12.10-1 version of the contrib parent instead of 12.10, or apply the same workaround.

4

Thanks it works with 12.10-1 !

1 Like