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.
The weld-dev mailing list is used for development discussion only (no support questions!) relating to Weld, JSR-299 and the TCK. You may subscribe to the weld-dev mailing list here.
We use Maven to build Weld. More details can be found on the Weld in Maven page.
We use Hudson to produce automated builds of both Weld and the CDI TCK. Use the following links to access the automated build results for both Weld and the TCK.
The CDI TCK is developed alongside Weld. You can read more about the CDI TCK, if you'd like to know how to develop TCK tests and execute the TCK against the RI.
The CDI TCK is licensed under the Apache License 2.0.
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
Weld uses Git for SCM. Access is via github
# Clone the 1.0 development branch: git clone git://github.com/weld/core.git
We operate the Integration Manager workflow; you can send pull requests when you have changes you would like merged.
To build Weld from SCM, get a copy of Maven 3.0 Beta1 or later, and run mvn install in weld/. You'll find the built artifacts and current set of libraries in your maven repository. To update JBoss AS with this version of Weld, run mvn install -Pupdate-jboss-as.
For more information, see the Weld Build page.
Start by checking out the current trunk from SCM. 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.
Here's a list of the issues the Weld development team have marked as good starting points:
Weld is being tested for performance regression. There is a special job in Hudson which is started automatically once a day and monitors performance. If the performance regression is higher than 5% the particular build will fail and an email describing the situation will be sent to recipients (Seam/Weld QA team). Then a real performance benchmark will be started to verify the regression.
The performance of Weld is being compared to the previous build and it is also being compared to the build two back to prevent us from running into the situation when the performance is regressing continuously in small steps without noticing it.
A public instance of the Hudson job is available at http://hudson.jboss.org/hudson/job/perf-weld-numberguess-regression/
The file report.txt (one of the Last Successful Artifacts of the job) contains results (a comparison to previous builds).