RE: [Embedlets-dev] Here is the announcement....

[Christopher S. <cs...@oo...>]

Andrzej,

When are you going to post the full source tree to the Embedlets repository?
Until you do this it is impossible for anyone else to do any code
development. We will have no revision control until this is done as well.

I know that it is not your intention to code the complete project yourself!

Chris

> Topic tags:[ARCH][JAPL][WIRING][DOCS][MGMT][STRATEGY][NEWBIE]
> _______________________________________________
>
> ...that will go up as soon as I (or you) manage to get the stuff
> posted to
> CVS.
>
> Just thought you might want to know, so you could "play" earlier. ;-)
>
>
> .....A
>
> ------------------------------------------------
>
> I just posted the next release of all the code and executables in
> the release
> directory in the CVS repository.
>
> There are 3 zip files you can download:
>
> embedlet_003.zip		The core interfaces/contracts/base
> classes (the spec),
> 						Ver 0.03
>
> outpost_003.zip		The Outpost Container Reference
> Implementation.
> 						Ver 0.03
>
> outhouse_001.zip		The sample application (embedlet
> pipeline).  Ready to run!
>
> Each archive is independent of the others.  If all you want to do
> is to run
> the test application, all you need is Outhouse.
>
> This set of releases will build and run on Windows, Linux, aJile
> (JStamp/SaJe) and TINI!  You can run Outhouse on any of these
> platforms.  The
> binary builds of Outhouse for aJile/TINI are not included to keep the
> distribution sizes down, but there are Ant targets that will let
> you build
> them easily.  Be sure to read the devnotes.txt file in theOuthouse  /doc
> subdir if you want to run on these embedded platforms since
> you'll have to
> modify the build.properties file (to point to where you have your
> aJile/TINI
> SDK's installed) and on editing the aJile .ajp files.
>
> Check the respective history.html files (in the /doc subdirs) for
> what's new.
>
> Major stuff added in this set of releases:
>
> 1) Implementation of the Outpost Timer Service (both one shot and
> periodic
> timers).
>
> 2) Implementation of event type matching and wildcard capability
>
> 3) Move of the sample application code into the Outhouse archive
> (no longer
> part of the Outpost distribution).
>
> 4) Change of the sample application to use the Timer Service to drive the
> ProducerEmbedlet event production process.
>
>
>
> Andrzej Jan Taramina
> Chaeron Corporation: Enterprise System Solutions
> http://www.chaeron.com
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of TotalView,
> The debugger
> for complex code. Debugging C/C++ programs can leave you feeling lost and
> disoriented. TotalView can help you find your way. Available on
> major UNIX
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> Embedlets-developer mailing list
> Emb...@li...
> https://lists.sourceforge.net/lists/listinfo/embedlets-developer
>