Hi All,<div><br></div><div>So I&#39;m starting to refactor the RichFaces 4.0 build and I am looking at what other projects are doing.  This includes weld and seam 3 builds ( especially because we have a similar module concept ).<div>
<br></div><div>I&#39;m looking for some lessons learned and what you would change if you could.  </div><div><br></div><div>- Does the single parent pom work well when you have different modules with very different dependencies?</div>
<div><br></div><div>- Do you guys have any scripts in your back pocket for making the svn co/update, and build easier?  We have a top level pom that does nothing but build all our modules from their trunk.  Might be worth checking in ( or I might of just missed it ).</div>
<div><br></div><div>- Dist building - I was thinking of modularizing our dist builds so CDK could be responsible for building CDK dist, UI would do the same, while having a top level build put these together into the primary dist.  Was there thoughts of this for weld/seam 3?  It appears to me that there is really only a top level distribution build.  I think both have merits, just wondering what the thoughts were.</div>
<div><br></div><div>- I know you guys are using ant builds instead of mvn assembly plugin.  Was this just because the assembler sucks, or something else?</div><div><br></div><div>FYI - I think a lot of the build wiki pages are great, and has good details ( RF needs the same for release process).  I made a minor update to the <a href="http://seamframework.org/Weld/WeldCoreReleases">http://seamframework.org/Weld/WeldCoreReleases</a> page, but agree with other posts that some of the process is &quot;learn as you go&quot;.  It is still much better than many other projects, and I&#39;ll help out if I get the time, but I can&#39;t promise anything right now.</div>
<div><br></div><div>More question to come for sure,</div><div>- Jay</div><div><br>-- <br>blog: <a href="http://in.relation.to/Bloggers/Jay">http://in.relation.to/Bloggers/Jay</a><br>
</div></div>