Make jSPF a multimodule project
-------------------------------
Key: JSPF-63
URL: https://issues.apache.org/jira/browse/JSPF-63
Project: jSPF
Issue Type: Wish
Affects Versions: 0.9.6
Reporter: Stefano Bagnara
Assignee: Stefano Bagnara
Priority: Minor
Fix For: 0.9.7
This issue is to track and record this proposal:
-----------------------
I'm proposing to:
- move the main source tree to a "resolver" module
- promote the "stage" folder to a module (like we did in server-trunk: this
move our stage repository "hack" to a module and is better handled by maven)
- create an "openspf-tester" module including the code used to run openspf
tests on the wire (introducing a fake yaml based dns service).
- Maybe during the refactoring it will be necessary to introduce
a "core" or "common" module including code used by both modules (I didn't
evaluate this yet).
The advantage of this change is mainly that we have a new "product", the
openspf-tester that can be used even outside from jSPF to prove OpenSPF
compliance. This should also simplify our efforts to have jSPF declared as
compliant in the page http://www.openspf.org/Implementations (we are "currently
being evaluated" since 2006-12-04/r76)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
