Module has been moved. Source still needs repackaging under org.jboss.seam (as do the
POMs) (see SEAMWICKET-13 and SEAMWICKET-12).
Yes, IMO this was blurring that line and moving it will make the line
a bit sharper.
On 16 Apr 2010, at 15:55, Clint Popetz wrote:
> It's fine with me; I've never understood the line between weld and
> seam3 anyway :)
>
> -Clint
>
> On Fri, Apr 16, 2010 at 9:39 AM, Pete Muir <pmuir(a)redhat.com> wrote:
>> Hi all,
>>
>> Since we've started developing Seam 3, I've started to think that the
Wicket support is a better fit for Seam rather than Weld. Most of the Weld sub projects
handle integrating Weld into other environments (such as Java SE) or provide support for
using Weld (e.g. Weld extensions, archetypes).
>>
>> There wasn't a consensus in our meeting yesterday, so I wanted to open it up
for discussion.
>>
>> Pete
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
>
>
> --
> Clint Popetz
>
http://42lines.net
> Scalable Web Application Development
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev