15 Mar
2010
15 Mar
'10
5:52 p.m.
On 03/15/2010 05:17 PM, Bogdan Flueras wrote:
Ok got it.
I want to build just the Platform, not the Enterprise.
Are you saying that if i want to build just the platform/web/standard it
wont work? Ive just folowed the steps from Building
Wiki<http://dev.xwiki.org/xwiki/bin/view/Community/Building%20>(Build…
XWiki Platform). It is written that Maven is smart enough to handle the
dependencies.
Yes, Maven is smart enough, just that we didn't say that those plugins
are needed for the standalone platform build. This is wrong, it should
be fixed on our side, but in the meantime you have three options:
- build enterprise/web
- manually copy the needed jars into the exploded war, and edit
xwiki.cfg to enable those plugins
- change the standalone pom.xml to include the extra plugins and build again
What about the missing plugins in the resulting jar
(obtained when building
platform)? See my first post.
2010/3/15 Sergiu Dumitriu<sergiu(a)xwiki.com>
> On 03/15/2010 04:46 PM, Bogdan Flueras wrote:
>> With AND without them. The content of the file does not really mater, as
> it
>> were my hackings.
>> Still the problem remains with the original code.
>> The content of the javascript.vm is spit with no processing in the
> resulted
>> HTML.
>>
>> Ex:
>>
>> $xwiki.jsfx.use('js/scriptaculous/effects.js', true)
>> $xwiki.jsfx.use('js/xwiki/widgets/modalPopup.js', true)
>> $xwiki.ssfx.use('js/xwiki/widgets/modalPopup.css', true)
>
> This means that the skin extension plugin is not active.
>
> You should not build platform/web/standard to obtain the war, but
> enterprise/web/ which also packages the plugins.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/