9:08 p.m.
Hi All,
So I'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 ).
I'm looking for some lessons learned and what you would change if you could.
- Does the single parent pom work well when you have different modules with
very different dependencies?
- 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 ).
- 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.
- I know you guys are using ant builds instead of mvn assembly plugin. Was
this just because the assembler sucks, or something else?
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
http://seamframework.org/Weld/WeldCoreReleases page, but agree with other
posts that some of the process is "learn as you go". It is still much
better than many other projects, and I'll help out if I get the time, but I
can't promise anything right now.
More question to come for sure,
- Jay
--
blog: http://in.relation.to/Bloggers/Jay
3:44 a.m.
Jay,
regarding the checkout/update script, there is one for Seam 3. See
http://seamframework.org/Seam3/CheckOutAndBuildSeam for details.
On 03/17/2010 03:08 AM, Jay Balunas wrote:
Hi All,
So I'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 ).
I'm looking for some lessons learned and what you would change if you
could.
- Does the single parent pom work well when you have different modules
with very different dependencies?
- 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 ).
- 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.
- I know you guys are using ant builds instead of mvn assembly plugin.
Was this just because the assembler sucks, or something else?
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 http://seamframework.org/Weld/WeldCoreReleases page, but agree
with other posts that some of the process is "learn as you go". It is
still much better than many other projects, and I'll help out if I get
the time, but I can't promise anything right now.
More question to come for sure,
- Jay
--
blog: http://in.relation.to/Bloggers/Jay
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
9:26 a.m.
On Mon, Mar 22, 2010 at 4:44 AM, Jozef Hartinger <jharting(a)redhat.com>wrote:
Jay,
regarding the checkout/update script, there is one for Seam 3. See
http://seamframework.org/Seam3/CheckOutAndBuildSeam for details.
Yup - I found that about 15 min after sending the email :-( Thanks though.
On 03/17/2010 03:08 AM, Jay Balunas wrote:
> Hi All,
>
> So I'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 ).
>
> I'm looking for some lessons learned and what you would change if you
> could.
>
> - Does the single parent pom work well when you have different modules
> with very different dependencies?
>
> - 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 ).
>
> - 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.
>
> - I know you guys are using ant builds instead of mvn assembly plugin.
> Was this just because the assembler sucks, or something else?
>
> 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 http://seamframework.org/Weld/WeldCoreReleases page, but agree
> with other posts that some of the process is "learn as you go". It is
> still much better than many other projects, and I'll help out if I get
> the time, but I can't promise anything right now.
>
> More question to come for sure,
> - Jay
>
> --
> blog: http://in.relation.to/Bloggers/Jay
>
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
>
--
blog: http://in.relation.to/Bloggers/Jay
4:58 a.m.
On 17 Mar 2010, at 02:08, Jay Balunas wrote:
Hi All,
So I'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 ).
I'm looking for some lessons learned and what you would change if you could.
- Does the single parent pom work well when you have different modules with very
different dependencies?
It works well to a degree - aka the common superset of dependencies only (and plugin
control of course). In fact, we are now using composition rather than inheritance, as it a
lot more flexible.
We also use a "stack" POM with composition to specify a distribution.
- 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 ).
- 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.
For Weld there is only a top level dist, as that is all we distribute. Each Seam module
may have a distro, not decided yet.
- I know you guys are using ant builds instead of mvn assembly plugin. Was this just
because the assembler sucks, or something else?
Because I couldn't work out how to use assembly plugin originally. Now I have, and new
builds use the assembly plugin (and we are converting others).
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
http://seamframework.org/Weld/WeldCoreReleases page, but agree with other posts that some
of the process is "learn as you go". It is still much better than many other
projects, and I'll help out if I get the time, but I can't promise anything right
now.
Yeah - also, as I wrote them, and wrote the build, I suspect I fell foul of making
assumptions ;-)
Pete
5132
days inactive
5154
days old
3 comments
3 participants
participants (3)
-
Jay Balunas -
Jozef Hartinger -
Pete Muir