This should only be used if the server in which to install XWiki has no network access, and no other means to install the user interface is available.


  • a staging / development server which has access to the internet, to collect the necessary resources from there 
  • a minimal development environment on the staging server including the mvn tool, as if you want to build XWiki from Source
  • a way to copy the resources from the staging to the production server 
  • write access to the on the server

Download the UI resources

First make sure that you have the right settings.xml on the staging server, which has the XWiki repositories enabled.
You also might want to move away your current $HOME/.m2/repository temporarily to mimimize the amount of files to be transferred to production later.

Create an empty directory and place the following file as pom.xml in it:

 <project xmlns="" xmlns:xsi="" xsi:schemaLocation="">
 <name>dummy download package</name>

Make sure to update the version numbers (here 7.4) in both the <parent> and the <dependencies>.

Open a command line, change to the directory created in the previous step and issue the command:

mvn clean install

This will fail with an error message like:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce (enforce-valid-poms) on project never-mind: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]

 Never mind; as long as it has downloaded the "dependencies" you are set for the next step.

Install the resources on the server

As the next step, copy the complete /.m2/repository to a directory on the production server where the user running the XWiki webapp can read it.
(TODO: figure out if only parts of the directory are sufficient, i.e. /.m2/repository/org/xwiki)

Configure in the the destination directory on the server as the "main xwiki" repository:


Restart the server (if already running), remove/move away the "permanent directory" (wherever the property ${environment.permanentDirectory} points to) - just in case it remembers previous failed install attempt (when upgrading, better only move aside ${environment.permanentDirectory}/jobs )  - and access XWiki via the browser to see if the distribution wizard comes up again.

This time it should find the necessary files from the local repository and install the UI.


Get Connected