Andy Clark wrote:
>
> Edwin Goei wrote:
> > +1, sounds good to me. I'd support moving portions of code that
> > are not maintained and which few people use to a separate package.
>
> Exactly. How do you feel about creating a new "contrib" directory
> in the xml-xerces module where this code is placed? It would then
> be required to have its own Ant build script and would NOT be
> built and packaged into a Xerces2 release by default.
Not sure... Pro: it is clear what is core vs. contrib. Con: it is
difficult to move code from core to contrib or vice-versa. There may be
some code like the WML package itself that gets added to core and then
becomes no longer maintained and peripheral and so it takes extra effort
to move to contrib.
Someone (Jeremy Carroll) suggested having 2 distributions: 1) core and
2) jumbo = core + contrib. This seems like a good idea to me.
Maybe instead of having two separate directory hierarchies (core and
contrib), the separation could be done in a single Ant build file where
it is easier to change and make sure all components build.
After thinking about it, I'm leaning towards this last option: a single
Ant build.xml file that produces a core distribution and a jumbo
distribution. Not all code in jumbo would be supported.
>
> What about documentation and such? Where would that go? Who would
> be responsible for generating the JavaDocs? etc.
In the single build.xml file option, the target would determine the
amount of javadoc produced. E.g. "jumbo" produces both the core and
contrib docs.
-Edwin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
