I created a maven2-port branch for mime4j and I did the following changes:
- reorganized to maven2 standard directory layout
- updated build script to maven2 (including javacc and jjtree code
generation by maven2 plugin)
- updated source file headers to follow the latest ASF rules
- updated javacc/jjtree files to be javacc4 compliant (the maven2 plugin
is for javacc4.0).
The tests passes but due to the javacc update I would like to have some
sort of review on my changes.
Can anyone review the branch and tell me if the generated jar is still
working like before or if I introduced any problem with the changes to
the *.jj *.jjt files?
I then generated the website (mvn site) and committed it to the site/www
repository. You can see the result here:
http://people.apache.org/~bago/james/www/mime4j/
If everything is ok this will become official on the next "svn update"
on minotaur.
We should also make sure that ASF is the main channel for the website
and releases of mime4j.
Who does control the www.mime4j.org domain?
Why the 0.2 release has been done on SourceForge and not here in the ASF?
I didn't copy the samples folder to the maven2 branch because I'm not
sure on the best approach with this. Maybe the best thing would be to
have a different maven2 project for the samples, any other idea?
What about the issue tracking for Mime4J? I see that we don't have a
JIRA project for it and that on sourceforge there is an old issue
tracker. Should we create the JIRA "MIME4J" subproject (like we did for
JSPF, JSIEVE, POSTAGE)?
Niklas, Joe: can you update us on the status of this project? Do you
currenlty use mime4j? Are you still working on it/interested in working
on it? Are there other mime4j users around?
Stefano
