Bernd Fondermann wrote:
Possible solutions I can think of are... o go on patching JAMES-442, don't change anything right now
+0
o move to a svn-sandbox, allow for more review, feedback and tests
+0.5
o make it a subproject
+1
o merge into James Server codebase (option: hold on until mvn2 modularization is in effect)
-1 (even if we introduce modules Postage doesn't belong to James Server, imho)
o move to JMeter
Well, I think that JMeter will have much more requirements for Postage to be included in its repository. At least it would share a common infrastructure with JMeter and probably they will not like the James dependencies. Btw this is not an option I can vote on.
I'd favor "subproject", at least as a mid-term perspective. If I understand correctly, this would require PMC attention.
I'm starting a vote for this. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]