The difficulty is the license isn't it?
Since it is GPL people should take an explicit decision to deploy it.
e.g. we can bundle JTS in the distribution with an installer to ask if they want it
or with JBoss5 it could be an option in the profile service configuration
I'd recommend initially that the JTS test coverage on the appserver was a
seperate project that
1) pulled in the JBossAS build
2) changed the config to use JTS
3) ran its own testsuite
This avoids any license issues for the main JBossAS distribution.
I'm not suggesting we ship the JTS with AS, although we could consider it. However, because it's supported it needs better QA than it currently has.
> 3) ran its own testsuite
My point is that the JTS replaces the JTA for customers that use it. It may have additional tests, but it needs to pass all the regular AS testsuite ones too. The AS (or at least the EAP) should not ship unless it does. If the QA is separate it will remain a second class citizen and that's a asking for support trouble.
You can still run the JBossAS Testsuite from the other project,
it should just be a case of invoking its ant's script from your ant script
(perhaps passing different parameters - we could even "macroise" the
test targets if you need to start an ORB for all test clients).
It's a long standing issue that the testsuite is not very flexible
or even as modular as it first appears.
I guess this won't be resolved until we move to Maven?
Whenever that is. :-)
I'm not suggesting we ship the JTS with AS, although we could consider it.
It was considered back in November 2005, when we decided it (and WS-TX support) should be a separate download and not part of the AS distro.