On Fri, May 7, 2010 at 10:57 AM, Simon Laws <[email protected]> wrote:
While the samples thread is ongoing I'll throw out this sugestion:
I think the one huge distribution is becoming too unwieldy so how
about changing to two binary distributions, a base one, and an extras
one.
- base (or some other appropriate name)
- requires JDK6, includes core runtime with Assembly
- Java impl/interface.java
- Web Services interface/binding support using JAX-WS
- distributed domain using Hazelcast
- impl.web and webapp support
- binding.jms support (as it has no dependencies in some
environments or in other environments can have just one ActiveMQ jar
which is easy to doc)
- binding.http which is OASIS draft spec with functionality merged
from binding.rest and binding.jsonp and all json using just Jackson
- extras
- herarchical directory structure with seperate folders for each option extra:
- JDK 5 dependencies
- impl.bpel support
- impl.spring support
- b.rmi (or maybe in base as it has no dependencies)
- ... folders for every other extension - corba, atom - etc
- tomcat deep integration war instead of that being separate download?
That would make the base distribtion work for the majority of what
most people use, it would be small (< 10Mb) and have less than 10 jars
so easy to understand and document so you can easily document how to
delete things like hazelcast or Jackson if you don't want those.
Things change and grow over time so to deal with that we'd say to add
something to the base distribution that adds more dependencies or size
or complexity or unusualness requires asking and consensus but anyone
can add anything to a new folder in the extras distribution. In the
releases base would be fully tested but the extras distribution would
be as-is on a best can do basis and the only thing verified is it
meets ASF legal requirements.
There would still be just one source distribution containing everything.
Comments?
...ant
