Built with Seam
You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
| Online: | 8 Members of 8153 |
Status of the specification
The Contexts and Dependency Injection for Java EE specification is being developed by the JSR-299 Expert Group. The specification is currently in the proposed final draft phase and is collecting feedback from the community via the comments alias jsr-299-comments@jcp.org. The Expert Group needs your help to make JSR-299 the best Java EE specification ever.
The Expert Group is lead by Gavin King.
Status of the RI
The JSR-299 RI (Weld) and TCK are developed together. The final release is scheduled for late autumn. You may subscribe to the Development of Weld moderated discussion list.
You can download nightly snapshots of Weld from maven.
If you want to keep up to date with activity via email, you may subscribe to JIRA Issue Notifications or SVN Commit Notifications. Hudson provides results of the automated build.
Weld is licensed under the Apache License 2.0.
Weld development is lead by Pete Muir.
Status of the JSR-299 TCK
The JSR-299 TCK is being developed with the RI and uses many of the same resources. You may subscribe to the Development of Weld moderated discussion list which is also used for TCK development discussions.
You can download nightly snapshots of the TCK at http://snapshots.jboss.org.
If you want to keep up to date with activity via email, you may subscribe to JIRA Issue Notifications or SVN Commit Notifications. Hudson provides results of the automated build.
You can read more about the JSR-299 TCK infrastructure or you can skip right to developing the JSR-299 TCK against the Weld RI.
The JSR-299 TCK is licensed under the Apache License 2.0.
The JSR-299 TCK development is lead by Pete Muir.
Getting the RI code
The Weld SVN repository supports SVN anonymous access
Reporting issues
Issues with the RI or TCK may be reported in the RI JIRA or the TCK JIRA. You can read more about how Weld's JIRA projects.
I want to help with Weld development and contribute code
Start by checking out the current trunk from SVN. Read the Guidelines for Weld development for more.
Finally, pick an open issue and submit your patch. We typically grant commit access to Weld after a developer submits useful patches. Red Hat Inc. also hires exceptional contributors as full-time open source developers.
You may also be interested in reading about the how the Weld Build works.
Here's a list of the issues the Weld development team have marked as good starting points:
Open issues, by priority and affected component
No issues found.
Profiling Weld
When profiling Weld, there are a number of classes which are safe to exclude from analysis;
org.jboss.weld, -org.jboss.weld.integration, -org.jboss.weld.logging, -org.jboss.weld.util.CleanableMethodHandler, -org.jboss.weld.literal.AnyLiteral, -org.jboss.weld.literal.DefaultLiteral, -org.jboss.weld.bootstrap.api.Environments, -org.jboss.weld.test, -org.jboss.weld.tck, -org.jboss.weld.bootstrap.api.helpers.IsolatedStaticSingletonProvider
