I've resolved the problem. I've packed a new ear with a new jar and new war, using the same content for xml plans as the old ear and deployment is fine using the deployer of Geronimo 2.2. I don't know why, but I think the ear file was corrupt and only G2.2 is able to detect it if deployment is performed through command line.
Thanks for your time -- View this message in context: http://apache-geronimo.328035.n3.nabble.com/Deploy-ear-with-Geronimo-2-2-tp1294285p1309179.html Sent from the Development mailing list archive at Nabble.com.
