On Nov 5, 2008, at 2:55 AM, Reinhard Pötz wrote:
Steven Dolg wrote:
If everything fails moving the pom might be an option. Would that
produce a valid project file with your setup?
If that solves the problem with IDEA, we can (re)introduce the root
pom.
Actually I also have problems with creating releases because the Maven
release plugin doesn't support flat scenarios (although recommended by
Maven AFAIU).
Vadim, you can use cocoon3/trunk/release.pom.xml and rename it to
pom.xml. Then go to parent/pom.xml and remove the <modules> section
from
there. Then invoke all mvn commands from cocoon3/trunk instead of
cocoon3/trunk/parent.
Works beautifully!
Why not to have pom in root of the project? It seems to be the most
obvious thing to do, to run mvn from root of the project.
Vadim
