[xwiki-devs] openguide: plugins and skins
Hi, I'm building a customized version of the xwiki enterprise. So far i've created a new skin and a new plugin. I want to: - define the new skin as default. I mean, instead of changing the xwiki.cfg or the skin class i would like to make it default at compile level. Everytime i do mvn install i should be selected as default. - include my new plugin in WEB-INF/lib automatically everytime i compile (just like the other plugins - jodatime etc) thank you very much for you attention. regards, Luis Ferreira
Hi Luis, What you ask is outside the scope of the xwiki project. You're asking for some general maven help. The maven build that xwiki provides is for building what the xwiki project wants to distribute. It's not for building any custom version of xwiki. What you should do: * create your own maven build * have a build module that depends on the XE WAR and that replaces the xwiki.cfg file by your own and that adds your own plugins to the WEB- INF/lib directory. Thanks -Vincent On Nov 20, 2007, at 2:05 AM, Luis Alves Ferreira wrote:
Hi,
I'm building a customized version of the xwiki enterprise.
So far i've created a new skin and a new plugin.
I want to: - define the new skin as default. I mean, instead of changing the xwiki.cfg or the skin class i would like to make it default at compile level. Everytime i do mvn install i should be selected as default.
- include my new plugin in WEB-INF/lib automatically everytime i compile (just like the other plugins - jodatime etc)
thank you very much for you attention.
regards, Luis Ferreira _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Vincent Massol wrote:
Hi Luis,
What you ask is outside the scope of the xwiki project. You're asking for some general maven help.
The maven build that xwiki provides is for building what the xwiki project wants to distribute. It's not for building any custom version of xwiki.
What you should do: * create your own maven build * have a build module that depends on the XE WAR and that replaces the xwiki.cfg file by your own and that adds your own plugins to the WEB- INF/lib directory.
Actually, we could make the default skin name a parameter, since xwiki.cfg is generated by velocity. As for including the plugin, you can either modify xwiki-platform-pom/pom.xml and/or xwiki-product-enterprise/web/pom.xml and add your plugin to the list of plugins and do a mvn install. Now you need to find a way to also include the jar in the package, the best way is to define a maven project for it and add you project as a dependency. Cool thing this maven, right?
Thanks -Vincent
On Nov 20, 2007, at 2:05 AM, Luis Alves Ferreira wrote:
Hi,
I'm building a customized version of the xwiki enterprise.
So far i've created a new skin and a new plugin.
I want to: - define the new skin as default. I mean, instead of changing the xwiki.cfg or the skin class i would like to make it default at compile level. Everytime i do mvn install i should be selected as default.
- include my new plugin in WEB-INF/lib automatically everytime i compile (just like the other plugins - jodatime etc)
thank you very much for you attention.
regards, Luis Ferreira
Sergiu
On Nov 20, 2007, at 10:15 AM, Sergiu Dumitriu wrote:
Vincent Massol wrote:
Hi Luis,
What you ask is outside the scope of the xwiki project. You're asking for some general maven help.
The maven build that xwiki provides is for building what the xwiki project wants to distribute. It's not for building any custom version of xwiki.
What you should do: * create your own maven build * have a build module that depends on the XE WAR and that replaces the xwiki.cfg file by your own and that adds your own plugins to the WEB- INF/lib directory.
Actually, we could make the default skin name a parameter, since xwiki.cfg is generated by velocity.
Yes, that's possible but we would also need to make that config parameter a maven property so that it can be changed in a user profile. I think our highest priority in this domain would be to separate the skins in their own maven projects. However even this is very low priority compared to what remains to be done for the final 1.2 relase :) -Vincent
As for including the plugin, you can either modify xwiki-platform-pom/pom.xml and/or xwiki-product-enterprise/web/pom.xml and add your plugin to the list of plugins and do a mvn install. Now you need to find a way to also include the jar in the package, the best way is to define a maven project for it and add you project as a dependency.
Cool thing this maven, right?
Thanks -Vincent
On Nov 20, 2007, at 2:05 AM, Luis Alves Ferreira wrote:
Hi,
I'm building a customized version of the xwiki enterprise.
So far i've created a new skin and a new plugin.
I want to: - define the new skin as default. I mean, instead of changing the xwiki.cfg or the skin class i would like to make it default at compile level. Everytime i do mvn install i should be selected as default.
- include my new plugin in WEB-INF/lib automatically everytime i compile (just like the other plugins - jodatime etc)
thank you very much for you attention.
regards, Luis Ferreira
Sergiu _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (3)
-
Luis Alves Ferreira -
Sergiu Dumitriu -
Vincent Massol