I just noticed Andreas has got rid of the javamail dependency completely. May be you can revert the changes to pom.
Thank you. Rajika On Thu, Aug 1, 2013 at 5:57 PM, Hiranya Jayathilaka <[email protected]>wrote: > > On Aug 1, 2013, at 2:52 PM, Rajika Kumarasiri <[email protected]> > wrote: > > +1. I wonder how this triggers now. > > > It's somehow related to your build environment. I was able to reproduce > the issue, when I deleted the javamail jar from my local m2 repo and tried > to build the vfs transport. Since javamail is an undeclared transitive > dependency, it doesn't try to download it at build time. > > Thanks, > Hiranya > > > Rajika > > > On Thu, Aug 1, 2013 at 5:46 PM, Hiranya Jayathilaka > <[email protected]>wrote: > >> >> On Aug 1, 2013, at 2:34 PM, Hiranya Jayathilaka <[email protected]> >> wrote: >> >> This is interesting. VFS transport has a compile time dependency on a >> javamail API, but the dependency is not declared on any of the POMs. It >> looks like Maven still manages to find the dependency via a transitive >> dependency in Axiom. That's probably why it works most of the time. >> >> I think we can replace the use of javamail API with an Axiom API. That >> way we'll be able to get rid of this compile time dependency on javamail. >> >> >> Actually it's not that simple :( >> >> VFS transport implements some Axis2 interfaces, and these interfaces >> require types defined in the javamail API (especially the ContentType >> class). I see that latest Axiom snapshot has a ContentType class which can >> be used to replace these usages of javamail. But until Axis2 switches to >> this new API, we will have to keep using javamail. Correct solution at this >> point is to properly declare the javamail dependency in Synapse poms. >> >> Thanks, >> Hiranya >> >> >> Thanks, >> Hiranya >> >> On Aug 1, 2013, at 12:02 PM, Rajika Kumarasiri < >> [email protected]> wrote: >> >> No I am building online. >> >> Rajika >> >> >> On Thu, Aug 1, 2013 at 2:49 PM, Hiranya Jayathilaka <[email protected] >> > wrote: >> >>> Hi Rajika, >>> >>> Nothing has changed since yesterday. It builds fine for me and the last >>> Jenkins build has also been successful. This is probably an environment >>> issue specific to your build setup. From the looks of it maven is unable to >>> locate a dependency (probably javamail). Are you building offline? >>> >>> Thanks, >>> Hiranya >>> >>> On Aug 1, 2013, at 10:02 AM, Rajika Kumarasiri < >>> [email protected]> wrote: >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile >>> (default-compile) on project synapse-vfs-transport: Compilation failure: >>> Compilation failure: >>> [ERROR] >>> /home/rajika/project/apache/synapse/trunk/modules/transports/core/vfs/src/main/java/org/apache/synapse/transport/vfs/VFSTransportListener.java:[43,26] >>> package javax.mail.internet does not exist >>> [ERROR] >>> /home/rajika/project/apache/synapse/trunk/modules/transports/core/vfs/src/main/java/org/apache/synapse/transport/vfs/VFSTransportListener.java:[44,26] >>> package javax.mail.internet does not exist >>> [ERROR] >>> /home/rajika/project/apache/synapse/trunk/modules/transports/core/vfs/src/main/java/org/apache/synapse/transport/vfs/VFSTransportListener.java:[495,41] >>> cannot find symbol >>> [ERROR] symbol : class ContentType >>> [ERROR] location: class >>> org.apache.synapse.transport.vfs.VFSTransportListener >>> [ERROR] >>> /home/rajika/project/apache/synapse/trunk/modules/transports/core/vfs/src/main/java/org/apache/synapse/transport/vfs/VFSTransportListener.java:[497,25] >>> cannot find symbol >>> [ERROR] symbol : class ParseException >>> [ERROR] location: class >>> org.apache.synapse.transport.vfs.VFSTransportListener >>> [ERROR] -> [Help 1] >>> [ERROR] >>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>> -e switch. >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>> [ERROR] >>> [ERROR] For more information about the errors and possible solutions, >>> please read the following articles: >>> [ERROR] [Help 1] >>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >>> [ERROR] >>> [ERROR] After correcting the problems, you can resume the build with the >>> command >>> [ERROR] mvn <goals> -rf :synapse-vfs-transport >>> >>> >>> -- >>> Hiranya Jayathilaka >>> Mayhem Lab/RACE Lab; >>> Dept. of Computer Science, UCSB; http://cs.ucsb.edu >>> E-mail: [email protected] <[email protected]>; Mobile: +1 (805) >>> 895-7443 >>> Blog: >>> http://techfeast-hiranya.**blogspot.com<http://techfeast-hiranya.blogspot.com/> >>> >>> >> >> -- >> Hiranya Jayathilaka >> Mayhem Lab/RACE Lab; >> Dept. of Computer Science, UCSB; http://cs.ucsb.edu >> E-mail: [email protected] <[email protected]>; Mobile: +1 (805) >> 895-7443 >> Blog: >> http://techfeast-hiranya.**blogspot.com<http://techfeast-hiranya.blogspot.com/> >> >> >> -- >> Hiranya Jayathilaka >> Mayhem Lab/RACE Lab; >> Dept. of Computer Science, UCSB; http://cs.ucsb.edu >> E-mail: [email protected] <[email protected]>; Mobile: +1 (805) >> 895-7443 >> Blog: >> http://techfeast-hiranya.**blogspot.com<http://techfeast-hiranya.blogspot.com/> >> >> > > -- > Hiranya Jayathilaka > Mayhem Lab/RACE Lab; > Dept. of Computer Science, UCSB; http://cs.ucsb.edu > E-mail: [email protected] <[email protected]>; Mobile: +1 (805) 895-7443 > Blog: > http://techfeast-hiranya.**blogspot.com<http://techfeast-hiranya.blogspot.com/> > >
