I created this issue to track Geronimo related stuff I worked on the
past days: https://issues.apache.org/jira/browse/JAMES-845
In order to build james server against geronimo implementation (after I
removed every com.sun.* usage) the following change is needed in
"include.properties":
------------
- path.lib.javamail=javax.mail/jars
+ path.lib.javamail=org.apache.geronimo.javamail/jars
- path.lib.activation=javax.activation/jars
+ path.lib.activation=org.apache.geronimo.specs/jars
- jarname.javax-mail.jar=mail-1.4.1.jar
+ jarname.javax-mail.jar=geronimo-javamail_1.4_mail-1.5-SNAPSHOT.jar
- jarname.javax-activation.jar=activation-1.1.1.jar
+
jarname.javax-activation.jar=geronimo-activation_1.1_spec-1.0.3-SNAPSHOT.jar
------------
I added some comment to include.properties to point this out.
I also wanted to simplify the effort of changing the javamail
implementation in the m2 process, so I changed each pom to declare sun's
artifactid as a "provided" dependency and then added the dependency to
the main pom. This way to build and run tests against geronimo we simply
have to change the main pom (in a similar way to the ant build).
I was about proposing to use geronimo as the standard library to build
james against (while keeping sun's implementation in the runtime/binary
distribution), but this would require us to move to java5 because
geronimo classes (also the spec classes) are version 49 (don't know if
this is wanted or a bug).
That said, should we add geronimo jars to the stage repository at this
point? (They are 500kb in size and our stage is near 15MB already)
I'm -0 on my own proposal :-/
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
