I got the stuff building by restoring parent/pom.xml and deploying in to the repository. I think we should restore it until we have a replacement. Otherwise, working modules like remoting can&#39;t be built.<br><br>I couldn&#39;t check in build/parent/pom.xml, though, because it says I don&#39;t have write permissions. I&#39;m not sure what happened there.<br>
<br>Also, I thought we were moving to Git anyway. Since Seam 3 is totally borked, why not just make the move now? I communicated with a lot of folks about this vision of autonomous forks and I&#39;d like to see that become a reality.<br>
<br>-Dan<br><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>