On Jun 9, 2010, at 7:48 PM, Donald Woods wrote:
Now that I have the initial web profile assemblies created and hooked
into our TCK harness, I'd like to circle back around on this.
Personally, I like Option #1 - Upgrade and rename minimal assemblies to
EBA based assemblies. This way, all
On 6/10/10 11:22 AM, Kevan Miller wrote:
On Jun 9, 2010, at 7:48 PM, Donald Woods wrote:
Now that I have the initial web profile assemblies created and hooked
into our TCK harness, I'd like to circle back around on this.
Personally, I like Option #1 - Upgrade and rename minimal
On Jun 10, 2010, at 10:44 AM, Donald Woods wrote:
On 6/10/10 11:22 AM, Kevan Miller wrote:
On Jun 9, 2010, at 7:48 PM, Donald Woods wrote:
Now that I have the initial web profile assemblies created and hooked
into our TCK harness, I'd like to circle back around on this.
Now that I have the initial web profile assemblies created and hooked
into our TCK harness, I'd like to circle back around on this.
Personally, I like Option #1 - Upgrade and rename minimal assemblies to
EBA based assemblies. This way, all of the assemblies we build and
release will support the
I remember we had some discussion about dropping the minimal assemblies
from the 3.0 builds awhile back, but can't find where a decision was
made, so here goes...
Option 1 - We upgrade the minimal assemblies to support EBA apps by
using the eba-* instead of wab-* plugingroups, so all of our base
