Grégory Joseph wrote:

> I think part of the reason this isn't part of official docs (yet! - I think 
> it's linked to, though), is that the articles require a fairly good 
> understanding of Maven, and it's hardly translatable as-is to other 
> tools/OSes. These are guidelines, and will have to be adapted to every 
> project's situation.

It's definitely the best way to use Magnolia CMS with your own modifications 
and it's the way we work with it. I don't feel you need a very deep 
understanding of Maven to follow your articles. Anyway, it's definitely better 
than building Magnolia CMS from source in my opinion.

> Anyhow, as to the error encountered by OP, it's hard to say what's wrong, 
> since the original error wasn't included. It looks like OP is using Maven 3, 
> which may or may not be part of the problem (we're still using Maven 2.2.10) 
> - what was the original command/goal ?

We're using Maven 3 on our projects, but we're not building Magnolia CMS 
ourselves, so I wouldn't know if that might be a problem.

Nils.

------------------------------------------------------------------------
 VPRO   www.vpro.nl
------------------------------------------------------------------------


----------------------------------------------------------------
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