Hi Norman,
first of all thank you for taking care of this, too.
I guess the release version should probably be 0.3 (the last release on
sourceforge is 0.2).
Before tagging and voting we should change the xdocs to reflect the fact
that the release is no more on sourceforge:
http://james.apache.org/mime4j/index.html
http://james.apache.org/mime4j/start/download.html
Also
http://james.apache.org/mime4j/start/build.html
Refer to the ibiblio repository that we instead disabled because we use
a "local repository".
In the mean time we should fix the
http://james.apache.org/mime4j/start/build.html
So to explain that "mvn eclipse:eclipse" have problems with javacc
generated sources and after the .project/.classpath have been created
they will need a manual fix on source folders for the project.
I think we should try to use the maven release plugin for ASF that
automatically sign the artifacts, automatically removes the "-SNAPSHOT"
suffix, builds, checks, tags and increment the next version automatically.
I will be happy to help with this issues if everyone agree we need a
release.
Please note that the only build system for mime4j is maven2. I want to
be sure everyone (Noel) know this before we start working on the release
because I don't want to waste my time ;-)
Stefano
Norman Maurer ha scritto:
Hi guys,
I think mime4j deserve to get a release under the ASF.. What the others
think, are we ready for release version 0.4 ?
bye
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
