🚀 go-pugleaf

I got it to work after thinking about how I could explicitly add the Meta-INf files to the jar instead of just the class path to the Meta-Inf files.  Thanks for your help.

The answer is to go to Properties for the Archive.  Then select the content tab.  Click the add files button and add the following files:  Meta-inf\javamail.charset.map, Meta-inf\javamail.default.address.map,Meta-inf\javamail.default.providers.I do not know if all of them are needed or not but the providers file is required.  Select OK, make the project and the mail should work.  The no such provider error should not show up.


Roy McBrayer
"Roy McBrayer" <roymcbrayer@austin.rr.com> wrote:
>
>I am sure it can be done but I just haven't hit upon the answer yet.  When you say "explicity added", what specifically do you mean?  I have added the meta-inf directory to a library as a class path only and this is included in the jar.  Is there something else that I need to do?
>
>Thanks for your help.
>
>Roy
>
>"R.F. Pels" <ruurd@acklin.nl> wrote:
>>Roy McBrayer wrote:
>>
>>> I found this statement on JGuru regarding the mail.jar file.
>>> 
>>> "Here's something of note that we found while coming up with the solution.
>>> The Java Mail package has a manifest as well as other textual data at the
>>> root of the jar package it is deployed in. If you try to include the Mail
>>> package in your own application package it will fail because your package
>>> will have its own manifest, not the one the JavaMail needs.
>>
>>Because that textual data needs to be added EXPLICITLY by you when creating 
>>a jar that also contains JAF and JavaMail jar-content. It CAN be done, at 
>>least, I HAVE done it and it WORKS. 
>>
>>> Therefore, you MUST always use the mail API in your classpath, never as
>>> part of your own package.
>>
>>This is a replay of what Sun tells you in the JavaMail documentation. But 
>>it can be circumvented.
>>
>>--
>>
>>Ruurd
>