Yes, the optional state has two reasons:
- decouple from overall compile/testsuite until module is stable.
- mark the module as "should be installed via a separate, additional
binary dist"
I think that the current jboss dist is very heavyweight and nearly everybody
needs to cut it down to exactly the configuration that is needed ... I
prefer having a leaner main dist and several additional ("optional")
packages, although that was not quite that easy in the past having that
central .jcml File ... But now RH rulez!
Best,
CGJ
-----Ursprüngliche Nachricht-----
Von: Scott M Stark [mailto:[EMAIL PROTECTED]]
Gesendet: Sonntag, 24. Februar 2002 06:22
An: [EMAIL PROTECTED]
Betreff: Re: [JBoss-dev] JBoss/IIOP & JBoss/.Net optional -> standard
Yes, we will always have raw contrib stuff and experiments. It simply
should not affect the base compile or tests. If something isn't being
supported though we ditch it.
> May be a good idea to have an experimental group though. For example,
> the jmx stuff might go there until it has been polished, then migrated
> to the standard group (or rather core in this case... depending on if it
> does not have any external depends).
>
> --jason
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
