IIRC the test code in magnolia uses clover for which you need a commercial 
license.
I'd build with -Dskip.tests=true to avoid those problems (after all, you don't 
really need the tests).

Regards from Vienna,

Richard

Von: [email protected] [mailto:[email protected]] 
Im Auftrag von Thomas Joseph
Gesendet: Sonntag, 09. März 2014 13:09
An: [email protected]
Betreff: [magnolia-dev] Building Magnolia CMS

Hi,

I am curiously new to Magnolia and as a curious developer, I am trying to build 
Magnolia!

I am aware of Greg's post asking not to build Magnolia, but I do really want to 
"build Magnolia", and not my project running on Magnolia! And that is why I am 
posting this here. When I try to build, I find a lot of tests cases failing and 
compilation errors. Being a developer myself, I can put some extra effort to 
fix them, but I may run the risk of not having built it correctly. Hence I 
would like to have some pointers from Magnolia developers on this. Any help 
would be much appreciated.!

On a side note, my effort is to understand the architecture of Magnolia by 
looking through the code and building it myself.

--
Thanks and Regards,
/Thomas Joseph

LinkedIn: http://www.linkedin.com/in/ethomasjoseph
Twitter: http://twitter.com/ethomasjoseph

------------------------------------------------------------
Promote Open Source - Promote Liberty of Ideas and Software.
------------------------------------------------------------


________________________________
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 
<[email protected]<mailto:[email protected]>>
----------------------------------------------------------------


----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to