At first blush it looks like there are just three util classes that
make the javamail-transport module dependent on our specific javamail
implementation.
[javac] import org.apache.geronimo.mail.util.Hex;
[javac] import org.apache.geronimo.mail.util.Base64;
[javac] import org.apache.geronimo.mail.util.XText
Is this the case or are there other things that make our javamail-
transport module dependent on our specific javamail implementation?
-David
On Feb 6, 2006, at 11:04 PM, Bruce Snyder wrote:
On 2/6/06, Jian Liao <[EMAIL PROTECTED]> wrote:
Geronimo spec updated. you have to rebuild it. But you still can
not make it
right after rebuild geronimo-spec, so I just bypass this module in
the top
maven.xml.
Jian is correct, the compilation errors are due to changes to the
geronimo-spec-javamail module today. In order to avoid the compilation
errors, you'll need to check out the whole specs trunk:
https://svn.apache.org/repos/asf/geronimo/specs/trunk/
and at least build the geronimo-spec-javamail module using Maven 2 and
the following command:
mvn clean install
This will place the updated javamail spec jar here:
~/.maven/repository/org.apache.geronimo.specs/jars/geronimo-
javamail_1.3.1_spec-1.1-SNAPSHOT.jar
which will then allow the javamail-transport module to be built
correctly.
HTH
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!
G;6%I;\"YC;VT*"
);'
Apache Geronimo (http://geronimo.apache.org/)
Castor (http://castor.org/)
