Re: Spec compliance as new Commons component

2009-06-07 Thread Niklas Gustavsson
On Wed, Jun 3, 2009 at 2:22 AM, sebbseb...@gmail.com wrote:
 On 02/06/2009, Niklas Gustavsson nik...@protocol7.com wrote:
 Interesting.

 Could be useful for parts of Commons Codec, Mail, Net.

 Seems to me it fits in with the Commons charter, and other projects
 that could benefit from it (e.g. Tomcat, HttpComponents) may well
 already be using other Commons components.

So, if we would like to move forward on this (just checking, we have
not formally voted over at MINA), what would be the procedure?

/niklas

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: Spec compliance as new Commons component

2009-06-02 Thread sebb
On 02/06/2009, Niklas Gustavsson nik...@protocol7.com wrote:
 Hi

  Over at Apache MINA, we have voted in Vysper as a subproject. The
  Vysper project came with a bunch of code for tracking compliance to a
  specification (e.g. RFC) using a set of annotations. it also contains
  an APT based tool for producing reports based on these annotations.
  Here's the current code:
  
 https://svn.apache.org/repos/asf/mina/sandbox/vysper/trunk/src/main/java/org/apache/vysper/compliance/

  You can find an example of annotated source code here:
  
 https://svn.apache.org/repos/asf/mina/sandbox/vysper/trunk/src/main/java/org/apache/vysper/xmpp/addressing/stringprep/NodePrep.java

  An example of a generated report can be found here (Javadocs has not
  been uploaded, so some links will not work):
  http://people.apache.org/~ngn/spec_compliance.html

  Now to the question: this code is of interest to some other projects,
  and potentially to many projects. Thus, we would like to move it out
  of the Vysper code base. Now, MINA is not the most obvious place for
  this code, so we thought we should ask over here :-). Of course, we do
  not plan to throw the code over the fence but would rather like to
  participate in maintaining it at commons. What do you think, would
  this be a good fit at commons?

Interesting.

Could be useful for parts of Commons Codec, Mail, Net.

Seems to me it fits in with the Commons charter, and other projects
that could benefit from it (e.g. Tomcat, HttpComponents) may well
already be using other Commons components.

  /niklas

  -
  To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
  For additional commands, e-mail: dev-h...@commons.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org