Yes, that's what I was looking for - one assembly that users could then drop blog, trader, ... into instead of requiring unique assemblies for each.
-Donald On 2/22/10 4:36 PM, Jeremy Hughes wrote: > Hi Don, (hope you don't mind I've separated this discussion out) > > On 19 February 2010 16:27, Donald Woods <[email protected]> wrote: >> What about creating a common assembly under samples based on the current >> blog-assembly, which would allow users to drop-in the Blog, AriesTrader >> or their own wab/eba? > > So are you suggesting making blog-assembly a module purely for > building the blog sample assembly - .eba file. Then to have a child > module of samples whose target dir would act as a place to run the > OSGi framework, contain the 'load' dir for samples to be dropped into? > I think it's good to separate these concerns out. So I'm +1 for this > (if it's what you meant :-) > >> >> >> -Donald >> >> >> On 1/26/10 12:34 PM, Jeremy Hughes wrote: >>> There's been a lot of activity lately so I'd like to propose we do a >>> release so we can get some wider user feedback. I think we should give >>> it a version of 0.1 and stick to versions <1 while we're in the >>> Incubator. >>> >>> Then there is the question of whether to independently version the >>> high level modules or keep them lock-step. For now I think we should >>> keep them lock-step until we feel a need to change that. >>> >>> What does everyone think? >>> >>> Thanks, >>> Jeremy >>> >> >
