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