There are some additional entries we need to get into the dependency
management section. To cite one example, now that Weld is working against EL
2.2, let's get the EL version setup correctly. Steven, let me know when you
are working on it and I will help out.
-Dan
On Fri, Feb 5, 2010 at 8:12 AM, Pete Muir <pmuir(a)redhat.com> wrote:
ASAP - once I get the Servlet 1.0.1.CR2 tagged.
On 5 Feb 2010, at 01:20, Steven Boscarine wrote:
> Hello Pete,
> The weld archetypes are getting their component library version info from
the weld-extensions-bom-1.0.0-CR2.
>
> At what point do you recommend I update the BOM version?
>
> Thanks,
> Steven
>
>
>
> On 02/04/2010 07:02 PM, Pete Muir wrote:
>> I have tagged and published to Maven version 1.0.SP1 of the APIs
(containing a bug fix to the CDI API, compiling against the 2.2 EL API and
improvements to the JavaDoc), and 1.0.0.CR2 of Weld. You can now commit to
core again.
>>
>> We won't be integrating this release in JBoss AS straight away, as they
are in a component update freeze, prior to releasing M2. Once that release
is out, we will integrate this release. I know Roger is planning to
integrate this release into GlassFish sometime soon.
>>
>> I've also tested the SE, Servlet and Wicket support as well as all the
examples, however I have yet to tag and release these, or build the
distribution zip. I'll do this tomorrow. For this reason, please hold
commits to these areas until then :-)
>>
>> Pete
>>
>> On 4 Feb 2010, at 18:34, Pete Muir wrote:
>>
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
--
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