Leszek Gawron wrote:
> my bad .. I had cocoon:deploy plugin defined at parent pom so it ran 
> twice (still seems like a maven bug to me).
> 
> other problems still apply
> 
Hmm, that's bad - I don't see a solution for this now. But we discussed
at the GT an alternative handling of our blocks which would make the
cocoon:deploy plugin obsolete.

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Reply via email to