Hi guys: Just want to note that before we tag AS, let's be sure to run the EmbeddedAS TestSuite to ensure nothing's broken there in the interim. This isn't covered by the AS TestSuite itself. S, ALR

As it stands, EmbeddedAS is a standalone project which depends upon AS. To bring this into the AS build/testsuite is to introduce a cyclic dependency. The reasoning behind this structure was to decouple "EmbeddedAS", a combined API for lifecycle/config/deployment from AS proper. We can bring in the entire AS dependency chain transitively in one declaration, thus making for a single entry point for users. In turn, this is how the Embedded tests are set up/run. If we need to rethink this relationship, now is the time and I welcome all comments. To be honest I started developing outside in this little sandbox for prototyping and it's stood since. Will sleep on it and post more ideas to the list as they come. S, ALR On 10/23/2009 11:25 AM, Bill Burke wrote: > Why not? From my own experience, i suggest you make embedded a part of > the AS testsuite run or you'll find it often broken. > > Andrew Lee Rubinger wrote: >> Hi guys: >> >> Just want to note that before we tag AS, let's be sure to run the >> EmbeddedAS TestSuite to ensure nothing's broken there in the interim. >> This isn't covered by the AS TestSuite itself. >> >> S, >> ALR >> >