Help

I'm happy to announce new Weld 1.1.3.Final release.

With this release we finally moved Weld Core Arquillian tests by default to JBoss AS7, making the build easier and faster -- thanks Stuart.

But this of course doesn't mean we forgot about other containers;

  • it's still fully tested against latest GlassFish (thanks GF guys!),
  • added new web container tests (Tomcat 7; thanks Matija) and
  • reduced Jetty config a bit (thanks Geoffrey).

Other interesting issues or features include:

  • better conversation handling - thanks Lincoln and George; btw, LB3 I expect more patches from now on ;-)

Weld' github master will now be the basis of future 1.2 releases, moving current to branch 1.1.

(since there already is an abandoned 1.1 branch, we'll first move that one to 1.1-legacy)


I also have a few exciting announcements - in case you missed them:


Onward to Weld 1.2 and 2.0!!

p.s.: let us know if there are any new issues with the latest release ;-)

5 comments:
 
09. Nov 2011, 22:23 CET | Link

What versions of jetty are supported?

ReplyQuote
 
10. Nov 2011, 07:36 CET | Link
The Release Notes link is wrong
 
10. Nov 2011, 17:37 CET | Link
Geoffrey De Smet
The upgrade went fine, just noticed one glitch: I had to remove jetty-web.xml for it to work.

Please adjust the latest manual:
  http://docs.jboss.org/weld/reference/latest/en-US/html_single/#d0e5286
which still states "Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:"

Nice work! :)
 
10. Nov 2011, 22:12 CET | Link
Ara wrote on Nov 09, 2011 16:23:
What versions of jetty are supported?

All versions should work.

If they don't, create an issue, and we'll try to fix it asap.

 
10. Nov 2011, 22:13 CET | Link
Geoffrey De Smet wrote on Nov 10, 2011 11:37:
Please adjust the latest manual: http://docs.jboss.org/weld/reference/latest/en-US/html_single/#d0e5286 which still states Weld also supports Servlet injection in Jetty 6. To enable this, add the file META-INF/jetty-web.xml with the following content to your war:

Hmmm, it should still work if jetty-web.xml is there. What's the issue?

For the manual adjust, create a pull request. ;-)

Post Comment