<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 2/19/10 9:57 AM, Lincoln Baxter, III wrote:
<blockquote
cite="mid:a3f2f0581002190757g75688bb4g1629d6bb66e5f55f@mail.gmail.com"
type="cite">In reviewing: <a moz-do-not-send="true"
href="http://seamframework.org/Weld">http://seamframework.org/Weld</a>
to get started checking out the Weld source, it took me several scans
of the page to find this link:<br>
<br>
Weld, the JSR-299 RI (Reference Implementation) and the JSR-299 TCK
(Technology Compatibility Kit) are being [[[[<a moz-do-not-send="true"
href="http://seamframework.org/Weld/WeldDevelopmentOverview" target=""
class="regularLink">developed here]]]]</a> at <tt><a
moz-do-not-send="true" href="http://seamframework.org">seamframework.org</a></tt>.
Both are licensed under the Apache License, Version 2.0.
<br clear="all">
<br>
I'd like to recommend making a "Get Involved" section more visible,
since right now, that one tiny link is the only I could find.<br>
</blockquote>
I agree wholeheartedly. In fact, I'd kinda like to see the Weld and
Seam information completely separated. At the moment, they're two
different products, so having to sift through the info for one to get
to the other is strange. And frustrating. For example, I looked high
and low to find the Weld API documentation (spec and impl classes) and
couldn't find it, so I ended up checking out the code and building the
docs locally. That shouldn't be required, I think.<br>
<br>
When Seam 3 comes along and builds on top of Weld/CDI, then it might
make more sense to see the information more closely together. <br>
<pre class="moz-signature" cols="72">--
Jason Lee
President, Oklahoma City Java Users Group
Senior Member of Technical Staff at Oracle
<a class="moz-txt-link-freetext" href="http://blogs.steeplesoft.com">http://blogs.steeplesoft.com</a></pre>
</body>
</html>