Comment inline... 2012/8/7 Achim Nierbeck <bcanh...@googlemail.com>: > Hi > > just a quick upfront hint. I'm planning on releasing 2.1.0 of Pax Web > shortly so if there is some > last minute changes to get into give me a hint so I'll postpone it a > bit longer. >
Good to know, I'll stay out of your way and not commit anything to Pax Web (on any branch) before the 2.1.0 release. > I also have CDI (thanks to harald) on my roadmap I hope to fit it into > the 3.0 branch, again this will reduce the amount of branches to > maintain. Will there be a 3.0 branch, or will the master branch be 3.0.0-SNAPSHOT after the 2.1.0 release? I have started making some CDI-related changes on a "cdi" feature branch in my local repo (not yet in a shape to be pushed), so the question is whether or not we really need a cdi branch on GitHub, or could this all go straight into the 3.0 branch (or master, see above), given that this branch will be experimental anyway? I've created a dependency from Pax CDI to Pax Web, but Pax Web itself will not get new dependencies. There is a new API class for other extenders to customize the servlet context. Pax CDI itself is progressing nicely but still highly experimental and depends on third-party snapshots. Due to missing features and/or bugs in the latest official releases of Weld and OpenWebBeans I'm currently working with snapshots of both CDI providers. Moreover, Jetty support in OpenWebBeans is less complete than in Weld, so I'm currently focusing on Weld for the Pax Web integration. An OSGi-friendly Weld 1.2.0 release is in preparation, but for the moment, I've created Hudson jobs for the required snapshots of Weld and OpenWebBeans to build Pax CDI on our CI server. So we could aim at the following: - Pax CDI 0.2.0 with web support - based on Weld 1.2.0 - limited web features with OpenWebBeans 1.1.5-SNAPSHOT, in an optional profile, not part of the release - based on Pax Web 3.0.0.M1 with the new customization API. What do you think? Best regards, Harald _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
