We spoke about this briefly on the conf call today - I've created a JIRA about it here [1]. What do people think? Personally, I think a single distro containing jars and docs is all we should ship, with a README containing info on how to check out and run tests from Subversion, and how to download and run the JBoss Cache GUI Demo. Comments? Cheers Manik [1] http://jira.jboss.org/jira/browse/JBCACHE-1385 -- Manik Surtani Lead, JBoss Cache manik(a)jboss.org _______________________________________________ jbosscache-dev mailing list jbosscache-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosscache-dev

We spoke about this briefly on the conf call today - I've created a JIRA about it here [1]. What do people think? Personally, I think a single distro containing jars and docs is all we should ship, with a README containing info on how to check out and run tests from Subversion, and how to download and run the JBoss Cache GUI Demo.

On 8 Jul 2008, at 08:55, Bela Ban wrote: > IMO, we should > - Not have to ship the unit tests with the binary release > - DEFINITELY include the GUI demo with the distro > - NOT have to compile the GUI demo when running it through ant +1 on all those counts, but do we: - ship test srcs with the src distro?

- ship the GUI demo srcs with the src distro?

(keep in mind it is a separate package in SVN, complete with it's own versioning.

Bringing this up again. So to sum things up, here is what I propose: 1. A -bin distro that contains: * jbc-core.jar * lib dependencies * License docs, READMEs * Sample cfgs * Mircea's config translation scripts 2. An -all distro that contains the above, plus: * the GUI demo and scripts needed to launch the demo * documentation 3. A -docs distro that contains just the documentation 4. A -src distro that contains the entire contents of the tagged directory, as checked out of SVN. So this will have code + test srcs. The Maven scripts will be modified to add a -src.jar artifact to the Maven repos, so that we can attach them to IDEs, etc. The ant scripts that are shipped with the -all distro will be removed, since this has little use beyond launching the old demo and running tests. Comments? Cheers Manik On 8 Jul 2008, at 11:29, Bela Ban wrote: > > > Manik Surtani wrote: >> >> On 8 Jul 2008, at 08:55, Bela Ban wrote: >> >>> IMO, we should >>> - Not have to ship the unit tests with the binary release >>> - DEFINITELY include the GUI demo with the distro >>> - NOT have to compile the GUI demo when running it through ant >> >> +1 on all those counts, but do we: >> >> - ship test srcs with the src distro? > > yes > >> - ship the GUI demo srcs with the src distro? > > yes. IMO, we should ship all of the src with a src distro. Srcs are > not big anyway > >> (keep in mind it is a separate package in SVN, complete with it's >> own versioning. > > The GUI demo is in a separate SVN repo ? How come ? I think it > should be part of JBC... > > > -- > Bela Ban > Lead JGroups / Clustering Team > JBoss - a division of Red Hat -- Manik Surtani Lead, JBoss Cache manik(a)jboss.org _______________________________________________ jbosscache-dev mailing list jbosscache-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosscache-dev

IMO, the GUI demo should be part of the core distro Manik Surtani wrote: > Bringing this up again. > > So to sum things up, here is what I propose: > > 1. A -bin distro that contains: > > * jbc-core.jar > * lib dependencies > * License docs, READMEs > * Sample cfgs > * Mircea's config translation scripts > > 2. An -all distro that contains the above, plus: > > * the GUI demo and scripts needed to launch the demo > * documentation > > 3. A -docs distro that contains just the documentation > > 4. A -src distro that contains the entire contents of the tagged > directory, as checked out of SVN. So this will have code + test > srcs. > > The Maven scripts will be modified to add a -src.jar artifact to > the Maven repos, so that we can attach them to IDEs, etc. > > The ant scripts that are shipped with the -all distro will be > removed, since this has little use beyond launching the old demo > and running tests. > > Comments? > > > > > > -- Bela Ban Lead JGroups / Clustering Team JBoss - a division of Red Hat

Manik Surtani wrote: > The problem is that pulls in a bunch of dependencies that no one > would want on what is primarily a server-side library. A demo ? Then something is wrong with the demo... I believe the demo should be shipped with the core distro, because it is the first thing people will want to try out -- Bela Ban Lead JGroups / Clustering Team JBoss - a division of Red Hat