We also need to get a wiki page together than explains to someone step-by-step how to build Seam 3 and start hacking on it (one that is up to date). I don't mind putting it together, or working with a community member on it, but first I need to know what I'm writing.<br>
<br>Again, don't mean to pressure, I'm just saying that I have people e-mailing me asking to get started, and I have to tell them to just wait.<br><br>-Dan<br><br><div class="gmail_quote">On Fri, Dec 11, 2009 at 1:07 AM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Shane and Pete,<br><br>I like the new structure, it makes a lot more sense. However, this is one major problem. During the restructuring, the seam-parent got nuked. I don't see it anywhere, so I'm going to assume it was an oversight.<br>
<br>As we try to get this thing off the ground, I think there is one crucial aspect that needs to be resolved first and foremost (which I think is what you were implying, Pete, in your last response). We need to get a solid seam-parent and seam-bom (or whatever the version matrix now called). I'm looking at Weld and I can't figure out how that maps back to Seam. Here is one approach:<br>
<br>build/trunk/parent/pom.xml<br>build/trunk/bom/pom.xml<br><br>But I don't know if that's how you want it.<br><br>Ultimately, the modules should have a pom which looks something like:<br><br><project><br>
<parent><br>
<groupId>org.jboss.seam</groupId><br> <artifactId>seam-parent</artifactId><br> <version>1</version><br> </parent><br> ...<br> <groupId>org.jboss.seam</groupId><br>
<artifactId>seam-XXX</artifactId><br> <packaging>jar</packaging><br> <version>3.0.0-SNAPSHOT</version><br><br> ...<br> <dependencyManagement><br> <dependencies><br>
<dependency><br> <groupId>org.jboss.seam</groupId><br> <artifactId>seam-bom</artifactId><br> <version>${seam.version}</version><br> <type>pom</type><br>
<scope>import</scope><br> </dependency><br> </dependencyManagement><br> ....<br></project><br><br>This needs to be resolved or I can't bring contributors into the project because I just don't know what to tell them to do. And we have contributors waiting at the door. The time is ripe ;)<div>
<div></div><div class="h5"><br>
<br>-Dan<br clear="all"><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" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
</div></div></blockquote></div><br><br clear="all"><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>