[seam-dev] Modules have been moved

Shane Bryzak sbryzak at redhat.com
Fri Dec 11 04:27:24 EST 2009


Pete and I removed the parent and version matrix modules as part of the 
module cleanup.  I'm not sure what the ultimate intent is here, Pete 
said he was going to work on the build so I guess he can let us know 
when he's back next week.

This shouldn't stop us in the meantime, it just means we need to remove 
the dependency to parent from whatever module we want to build (and add 
the version numbers).  We can always add the parent in later.

On 11/12/09 16:07, Dan Allen wrote:
> Shane and Pete,
>
> 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.
>
> 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:
>
> build/trunk/parent/pom.xml
> build/trunk/bom/pom.xml
>
> But I don't know if that's how you want it.
>
> Ultimately, the modules should have a pom which looks something like:
>
> <project>
> <parent>
> <groupId>org.jboss.seam</groupId>
> <artifactId>seam-parent</artifactId>
> <version>1</version>
> </parent>
>    ...
> <groupId>org.jboss.seam</groupId>
> <artifactId>seam-XXX</artifactId>
> <packaging>jar</packaging>
> <version>3.0.0-SNAPSHOT</version>
>
>    ...
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.seam</groupId>
> <artifactId>seam-bom</artifactId>
> <version>${seam.version}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencyManagement>
>    ....
> </project>
>
> 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 ;)
>
> -Dan
>
> -- 
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen



More information about the seam-dev mailing list