OK. That kind of make sense (along with what Eoghan said). However, I really think there needs to at least be a "README" in the distributions that describes a little what it is along with pointers to the walkthroughs and such on the website.
Right now, I download and unpack the the tarball and I look at it and say "uhh..... what do I do with this?" We definitely need a readme in there to describe things as well as provide pointers off to the web site, the users@ list for questions, etc..... Dan On Tue May 5 2009 5:31:49 am David Bosschaert wrote: > Hi Dan, > > On the samples, they are not part of the distribution because they can > be installed straight from the internet. All of the DOSGi > documentation is available here: > http://cxf.apache.org/distributed-osgi.html and which contains links > to the sample source code and a very detailed walkthrough of the > greeter sample: > http://cxf.apache.org/distributed-osgi-greeter-demo-walkthrough.html > As the OSGi containers install stuff straight from the internet, you > don't have to have the bundles available locally. Once the release is > out I'm planning to update this page to point straight to the sample > artefacts in maven. > > There is no such page for the spring-dm demo, I'll take an action to > provide such a page with the DOSGi documentation, but I don't think > this should hold up the release. > > Hope this makes sense to you, > > David > > 2009/5/4 Daniel Kulp <[email protected]>: > > I think I have to -1 this. Couple legal things need to get ironed out: > > > > 1) Since this is a full "distribution" type thing, what parts of that > > staging area will go into www.apache.org/dist/cxf? I ASSUME the > > mutimodule bundle, but not really sure. Also, there needs to be a > > tar.gz or zip of a "source" distribution of the whole contents of the > > tag. That would also go into dist. > > > > 2) I think some stuff in the NOTICE can be removed. For example: DOSGi > > doesn't ship the MTOSI stuff, that could be removed. Not major, but if > > a build has to be respun, let's get that cleaned up. > > > > 3) For the "distribution" builds, the LICENSE file needs to have at least > > the pointers to the LICENSES of the bundled deps appended to it. See > > the LICENSE in the cxf distributions. (remote-resources can do that, I > > may be able to help out tomorrow if I get out from under my backlog of > > email. :-( ) > > > > 4) Actually, IS there a distribution that includes the samples, possible > > a readme, etc...? Should there be? Not a big deal either way, but a > > bit strange. > > > > > > Dan > > > > On Fri May 1 2009 12:39:48 pm Eoghan Glynn wrote: > >> Folks, > >> > >> I'm calling a vote to release CXF Distributed OSGi 1.0. > >> > >> The dOSGi subproject of CXF provides the Reference Implementation of > >> the Distribution Software (DSW) component of the Distributed OSGi > >> Specification[1]. > >> > >> The staging area can be found at: > >> > >> http://people.apache.org/~eglynn/stage_cxf_dosgi > >> > >> This release is tagged with cxf-dosgi-ri-1.0 at: > >> > >> http://svn.apache.org/repos/asf/cxf/dosgi/tags/cxf-dosgi-ri-1.0 > >> > >> The vote will remain open for at least 72 hours. > >> > >> Please consider this call to vote as my +1. > >> > >> Cheers, > >> Eoghan > >> > >> [1] See RFC 119 in > >> http://www.osgi.org/download/osgi-4.2-early-draft3.pdf > > > > -- > > Daniel Kulp > > [email protected] > > http://www.dankulp.com/blog -- Daniel Kulp [email protected] http://www.dankulp.com/blog
