+1. Keep it simple; strip out the overhead of having to make sure all
this ancillary stuff works from anything other than a checkout.
I see JBC's maven build doesn't publish a
jbosscache-core-X.X.X-sources.jar though. A source jar whose contents
mirror the jbosscache-core-X.X.X.jar binary. That's very useful as a
mavenized project depending on JBC will pull down that file to the local
repo, where it's easy to tell your IDE to use it as the source. That to
me handles the main use case for a source distribution.
Must be simple to get that -sources.jar publishing that going, as a
couple of my projects do it and I didn't do anything to make it happen. ;)
Manik Surtani wrote:
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
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com