From line 0 added to lines 0 to 14:
<b>28 Sept 2011: Update</b>
We'd like to thank everyone for their comments - on twitter, on IRC and in the comments section. There have been some excellent concerns raised, and, believe it or not, those same reasons are at the heart of why we want to make the changes we discussed here. We have exactly the same concerns the community has raised.
We would like to reassure everyone on a few points:
= We are convinced that one of things that drove people to adopt Seam 1 and Seam 2 was *strong focus* on how to build *real* applications. We are well aware that Seam 3 hasn't offered that and we want to focus on providing that
= We *still believe* in portability and standards, and we want to take the knowledge we have about building portable standards and applications out of the Seam silo, and to the rest of the Java EE ecosystem. We will continue to standardise APIs and ideas that we believe are necessary
= That we love the Seam community and their passion and that we want bring this community into the heart of the Java EE community, where it belongs
= We *will ensure* that apps built using Seam 3.x will continue to run. We will continue to support anyone who wants to build a CDI extension
However we made a mistake. We told you about the outcome we think is the right way to address this. We didn't tell you why we want to do it, or how it supports these goals. We don't want to jump right in with a half-baked position right now, and make that mistake again. So we ask that you give us the benefit of the doubt, and trust that we do have the community's best interests at heart, and watch this space for the whole picture over the next couple of days.
<hr/>
We'd like to thank everyone for their comments - on twitter, on IRC and in the comments section. There have been some excellent concerns raised, and, believe it or not, those same reasons are at the heart of why we want to make the changes we discussed here. We have exactly the same concerns the community has raised.
We would like to reassure everyone on a few points:
= We are convinced that one of things that drove people to adopt Seam 1 and Seam 2 was *strong focus* on how to build *real* applications. We are well aware that Seam 3 hasn't offered that and we want to focus on providing that
= We *still believe* in portability and standards, and we want to take the knowledge we have about building portable standards and applications out of the Seam silo, and to the rest of the Java EE ecosystem. We will continue to standardise APIs and ideas that we believe are necessary
= That we love the Seam community and their passion and that we want bring this community into the heart of the Java EE community, where it belongs
= We *will ensure* that apps built using Seam 3.x will continue to run. We will continue to support anyone who wants to build a CDI extension
However we made a mistake. We told you about the outcome we think is the right way to address this. We didn't tell you why we want to do it, or how it supports these goals. We don't want to jump right in with a half-baked position right now, and make that mistake again. So we ask that you give us the benefit of the doubt, and trust that we do have the community's best interests at heart, and watch this space for the whole picture over the next couple of days.
<hr/>
From lines 37 to 51 deleted to line 52:
<hr/>
<b>28 Sept 2011: Update</b>
We'd like to thank everyone for their comments - on twitter, on IRC and in the comments section. There have been some excellent concerns raised, and, believe it or not, those same reasons are at the heart of why we want to make the changes we discussed here. We have exactly the same concerns the community has raised.
We would like to reassure everyone on a few points:
= We are convinced that one of things that drove people to adopt Seam 1 and Seam 2 was *strong focus* on how to build *real* applications. We are well aware that Seam 3 hasn't offered that and we want to focus on providing that
= We *still believe* in portability and standards, and we want to take the knowledge we have about building portable standards and applications out of the Seam silo, and to the rest of the Java EE ecosystem. We will continue to standardise APIs and ideas that we believe are necessary
= That we love the Seam community and their passion and that we want bring this community into the heart of the Java EE community, where it belongs
= We *will ensure* that apps built using Seam 3.x will continue to run. We will continue to support anyone who wants to build a CDI extension
However we made a mistake. We told you about the outcome we think is the right way to address this. We didn't tell you why we want to do it, or how it supports these goals. We don't want to jump right in with a half-baked position right now, and make that mistake again. So we ask that you give us the benefit of the doubt, and trust that we do have the community's best interests at heart, and watch this space for the whole picture over the next couple of days.
