On Thu, Apr 15, 2010 at 7:44 AM, Pete Muir <pmuir(a)redhat.com> wrote:
> While I'm on the topic of build poms, I don't understand why dist is not
in the build root. We currently have:
>
> build/trunk/parent/pom.xml
> dist/trunk/pom.xml
>
> Yet the dist is the bom. I'm confused every time I build. I think it
should be:
Yeah. This is probably my fault.
This is the stack POM which defines a distribution. It doesn't normally
appear directly in the hierarchy of the Seam POMs. Instead it should be
imported by the various modules (and defines the version of Seam they are
building against).
IOW we would end up with:
Seam Faces 3.0.0.Alpha1 imports Seam 3.0.0.Beta1 and uses the dep versions
it suggests.
Seam 3.0.0.Beta2 specifies an upgraded stack of deps, including Seam Faces
3.0.0.Alpha1.
When imported into a project, it is closer to the project, and so has *its*
versions used rather than those which are imported from the stack POM via
Seam Faces.
I know, this is slightly confusing, but will work :-)
It has a separate SVN structure as we need to tag it separately from the
build stuff (which just defines the build environment).
I will try to write this all up today and also review module's usage.
We punted for the Seam Faces Alpha 1 release by depending on weld-parent and
importing the weld-api-bom:1.0-SP1. We'll need to solidify the relationship
w/ seam-parent before we switch to using it in modules.
-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