<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I should have mentioned this previously, but I would like to see new
releases for all modules that currently use WeldX to be completed by
the end of this week. If you don't think you can meet this deadline
for your module, please speak up now so that we know about it and
can allocate additional resources to your module to help with the
release.<br>
<br>
Thanks,<br>
Shane<br>
<br>
On 21/12/10 10:38, Dan Allen wrote:
<blockquote
cite="mid:AANLkTi=8U-D=nkssaabSFs44vuvzTsYQB7ukwZ1t4-qO@mail.gmail.com"
type="cite">As Shane mentioned, Seam Solder is now available.
Here's the complete announcement:
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://in.relation.to/Bloggers/WeldExtensionsBecomesSeamSolder300Beta1NowAvailable">http://in.relation.to/Bloggers/WeldExtensionsBecomesSeamSolder300Beta1NowAvailable</a></div>
<div><br>
</div>
<div>I am currently working on new versions of seam-parent and
seam-bom. It likely won't all happen in one shot, so we may end
up with a couple incremental releases. I'm looking over all the
modules and "pulling up" common dependencies into these two
super poms.</div>
<div><br>
</div>
<div>Module leads, I'll let you know when there is a new version
available so you can start switching over your modules. However,
if your module currently depends on Weld Extensions, go ahead
and begin refactoring to Seam Solder. I encourage you to open an
issue in your module's JIRA to track the work. </div>
<div><br>
</div>
<div>-Dan<br>
<br>
<div class="gmail_quote">On Mon, Dec 20, 2010 at 6:49 AM, Shane
Bryzak <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
We've now released the artifacts to Maven, so all module
leads could you<br>
please update your module/s to use Solder and remove any
WeldX<br>
dependencies from your code and Maven poms. The released
version is<br>
3.0.0.Beta1, I've updated the BOM with this version (I'm not
sure if<br>
snapshots are currently getting published for this, however
you can just<br>
build it locally - <a moz-do-not-send="true"
href="https://github.com/seam/dist" target="_blank">https://github.com/seam/dist</a>).<br>
<br>
Maven artifact details are as follows:<br>
<br>
group id: org.jboss.seam.solder<br>
artifact id: seam-solder<br>
<br>
Once again, if you need assistance updating your module
please speak up<br>
and we'll make sure that someone gives you a helping hand.<br>
<br>
Thanks,<br>
<font color="#888888">Shane<br>
</font>
<div>
<div class="h5"><br>
On 15/12/10 08:00, Shane Bryzak wrote:<br>
> As most of you know, the Weld Extensions project
has been moved under<br>
> the Seam umbrella in the form of Seam Solder. We
are currently<br>
> addressing the few remaining Seam Solder issues
from JIRA and then<br>
> hopefully will have a release out in the next few
days. This has an<br>
> important implication for the other Seam modules -
once Solder is<br>
> released, we need to update each module accordingly
to use Seam Solder<br>
> (instead of WeldX) and release a new version of
that module. This step<br>
> should happen quite quickly, as the implications of
pulling in both<br>
> Solder and WeldX into the same Seam application are
unknown (but<br>
> possibly bad).<br>
><br>
> The goal is currently to have the Solder release
out on Friday/Saturday<br>
> this week. If we successfully get this release out
at this time, then<br>
> module leads should update their module as soon as
possible and prepare<br>
> it for release. If you need help with your module
(or will be<br>
> unavailable - it is the holiday season after all)
please let us know on<br>
> seam-dev and we will make sure that someone else
can help out.<br>
><br>
> I think this should be a pretty straight forward
operation, but of<br>
> course if there are any questions or concerns,
please bring them up.<br>
><br>
> Shane<br>
> _______________________________________________<br>
> seam-dev mailing list<br>
> <a moz-do-not-send="true"
href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
> <a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/seam-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/seam-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div>Dan Allen</div>
Principal Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br>
<br>
<a moz-do-not-send="true" href="http://mojavelinux.com"
target="_blank">http://mojavelinux.com</a><br>
<a moz-do-not-send="true"
href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a moz-do-not-send="true"
href="http://www.google.com/profiles/dan.j.allen"
target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
</div>
</blockquote>
<br>
</body>
</html>