Re: [Email] To release or not to release
) at com.dumbster.smtp.SimpleSmtpServer.run(Unknown Source) at java.lang.Thread.run(Unknown Source) org.apache.commons.mail.EmailException: javax.mail.NoSuchProviderException: smtp at org.apache.commons.mail.Email.send(Email.java:824) at org.apache.commons.mail.SimpleEmailTest.testSend(SimpleEmailTest.java:12 4) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTe stRunner.java:325) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnit Task.java:848) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask .java:556) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask .java:532) at org.apache.tools.ant.Task.perform(Task.java:341) at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:232) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.j ava:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAc tion(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:616 ) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.cli.App.doMain(App.java:486) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: javax.mail.NoSuchProviderException: smtp at javax.mail.Session.getService(Session.java:750) at javax.mail.Session.getTransport(Session.java:689) at javax.mail.Session.getTransport(Session.java:632) at javax.mail.Session.getTransport(Session.java:612) at javax.mail.Session.getTransport(Session.java:667) at javax.mail.Transport.send0(Transport.java:148) at javax.mail.Transport.send(Transport.java:80) at org.apache.commons.mail.Email.send(Email.java:821) ... 44 more [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 0,541 sec [junit] [ERROR] TEST org.apache.commons.mail.SimpleEmailTest FAILED jar:jar: [jar] Building jar: C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\email\target\common s-email-1.0.jar Copying: from 'C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\email\target\commo ns-email-1.0.jar' to: 'C:\Dokumente und Einstellungen\Administrator\.maven\repository\commons-email\jars\commons -email-1.0.jar' Copying: from 'C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\email\project.xml' to: 'C:\Dokumente und Einstellungen\Administrator\.maven\repository\commons-email\poms\commons -email-1.0.pom' BUILD SUCCESSFUL Total time: 1 minutes 13 seconds Finished at: Thu Jan 20 10:03:52 CET 2005 -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 18, 2005 2:58 PM To: Matthias Wessendorf; 'Jakarta Commons Developers List' Subject: RE: [Email] To release or not to release
RE: [Email] To release or not to release
) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTe stRunner.java:325) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeInVM(JUnit Task.java:848) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask .java:556) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask .java:532) at org.apache.tools.ant.Task.perform(Task.java:341) at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:232) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.j ava:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAc tion(MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at com.werken.werkz.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.Goal.attainPrecursors(Goal.java:488) at com.werken.werkz.Goal.attain(Goal.java:573) at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:616 ) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) at org.apache.maven.cli.App.doMain(App.java:486) at org.apache.maven.cli.App.main(App.java:1215) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: javax.mail.NoSuchProviderException: smtp at javax.mail.Session.getService(Session.java:750) at javax.mail.Session.getTransport(Session.java:689) at javax.mail.Session.getTransport(Session.java:632) at javax.mail.Session.getTransport(Session.java:612) at javax.mail.Session.getTransport(Session.java:667) at javax.mail.Transport.send0(Transport.java:148) at javax.mail.Transport.send(Transport.java:80) at org.apache.commons.mail.Email.send(Email.java:821) ... 44 more [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 0,541 sec [junit] [ERROR] TEST org.apache.commons.mail.SimpleEmailTest FAILED jar:jar: [jar] Building jar: C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\email\target\common s-email-1.0.jar Copying: from 'C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\email\target\commo ns-email-1.0.jar' to: 'C:\Dokumente und Einstellungen\Administrator\.maven\repository\commons-email\jars\commons -email-1.0.jar' Copying: from 'C:\Programme\eclipse-SDK-3.0-win32\eclipse\workspace\email\project.xml' to: 'C:\Dokumente und Einstellungen\Administrator\.maven\repository\commons-email\poms\commons -email-1.0.pom' BUILD SUCCESSFUL Total time: 1 minutes 13 seconds Finished at: Thu Jan 20 10:03:52 CET 2005 -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 18, 2005 2:58 PM To: Matthias Wessendorf; 'Jakarta Commons Developers List' Subject: RE: [Email] To release or not to release At 10:04 AM +0100 1/18/05, Matthias Wessendorf wrote: h..., I just set up my box. checked out [email] but build fails because of the old story regarding download of javamail I run maven jar:install I have forgotten, what to do... After all works (again) for me, I will do produce and signing the release, since I have commit priviledg. You need to do one of two things: 1) manually install the JARs where Maven wants them
RE: [Email] To release or not to release
h..., I just set up my box. checked out [email] but build fails because of the old story regarding download of javamail I run maven jar:install I have forgotten, what to do... After all works (again) for me, I will do produce and signing the release, since I have commit priviledg. Thanks! -Original Message- From: Matthias Wessendorf [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 4:20 PM To: 'Jakarta Commons Developers List'; 'Dion Gillard' Subject: RE: [Email] To release or not to release +1 -Original Message- From: Dion Gillard [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 11:32 AM To: Jakarta Commons Developers List; Corey Scott Subject: Re: [Email] To release or not to release I'm +1. On Mon, 17 Jan 2005 17:12:20 +0800, Corey Scott [EMAIL PROTECTED] wrote: Can someone with commit priviledge please change email over from RC1 to v.1.0? The RC has been out for quite a while now and so far there are no complaints about this. There are several other things waiting for this release, e.g. a proposed change to the jelly email classes (change to Commons Email) and some proposed extensions to Email itself, so completing the release would be greatly appreciated. Many Thanks, Corey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Email] To release or not to release
At 10:04 AM +0100 1/18/05, Matthias Wessendorf wrote: h..., I just set up my box. checked out [email] but build fails because of the old story regarding download of javamail I run maven jar:install I have forgotten, what to do... After all works (again) for me, I will do produce and signing the release, since I have commit priviledg. You need to do one of two things: 1) manually install the JARs where Maven wants them: $MAVEN_LOCAL_REPO/javamail/jars/javamail-1.3.2.jar $MAVEN_LOCAL_REPO/activation/jars/activation-1.0.2.jar 2) indicate with Maven properties that you want to override those specifications. You can do this on the command line with -D, but I prefer to use a build.properties file in the project directory. It would look something like this: maven.jar.override=on maven.jar.javamail=/path/to/javamail.jar maven.jar.activation=/path/to/activation.jar (You can also specify simply a version number in the value to the override properties, if the jars are in your Maven repository. details at http://maven.apache.org/reference/user-guide.html#Overriding_Stated_Dependencies) Joe Thanks! -Original Message- From: Matthias Wessendorf [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 4:20 PM To: 'Jakarta Commons Developers List'; 'Dion Gillard' Subject: RE: [Email] To release or not to release +1 -Original Message- From: Dion Gillard [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 11:32 AM To: Jakarta Commons Developers List; Corey Scott Subject: Re: [Email] To release or not to release I'm +1. On Mon, 17 Jan 2005 17:12:20 +0800, Corey Scott [EMAIL PROTECTED] wrote: Can someone with commit priviledge please change email over from RC1 to v.1.0? The RC has been out for quite a while now and so far there are no complaints about this. There are several other things waiting for this release, e.g. a proposed change to the jelly email classes (change to Commons Email) and some proposed extensions to Email itself, so completing the release would be greatly appreciated. Many Thanks, Corey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com Narrow minds are weapons made for mass destruction -The Ex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Email] To release or not to release
I'm +1. On Mon, 17 Jan 2005 17:12:20 +0800, Corey Scott [EMAIL PROTECTED] wrote: Can someone with commit priviledge please change email over from RC1 to v.1.0? The RC has been out for quite a while now and so far there are no complaints about this. There are several other things waiting for this release, e.g. a proposed change to the jelly email classes (change to Commons Email) and some proposed extensions to Email itself, so completing the release would be greatly appreciated. Many Thanks, Corey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Email] To release or not to release
+1 -Original Message- From: Dion Gillard [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 11:32 AM To: Jakarta Commons Developers List; Corey Scott Subject: Re: [Email] To release or not to release I'm +1. On Mon, 17 Jan 2005 17:12:20 +0800, Corey Scott [EMAIL PROTECTED] wrote: Can someone with commit priviledge please change email over from RC1 to v.1.0? The RC has been out for quite a while now and so far there are no complaints about this. There are several other things waiting for this release, e.g. a proposed change to the jelly email classes (change to Commons Email) and some proposed extensions to Email itself, so completing the release would be greatly appreciated. Many Thanks, Corey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Email] To release or not to release
+0 (I don't have time to do things like produce and sign distributions right now, but I agree that it's ready to go.) On Mon, 17 Jan 2005 17:12:20 +0800, Corey Scott [EMAIL PROTECTED] wrote: Can someone with commit priviledge please change email over from RC1 to v.1.0? The RC has been out for quite a while now and so far there are no complaints about this. There are several other things waiting for this release, e.g. a proposed change to the jelly email classes (change to Commons Email) and some proposed extensions to Email itself, so completing the release would be greatly appreciated. Many Thanks, Corey -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com Narrow minds are weapons made for mass destruction -The Ex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Email] To release or not to release
I'm actually +1 *only* if we make the minor API changes that I suggested last week. These changes are to the new caching API: * Change setTagForScript in JellyContext to setScriptData. This method should take a key of type Script, not TagScript. * Also in JellyContext, change the name of tagHolderMap to scriptData. It shouldn't be a WeakHashMap. * All access to the scriptData map should be through a protected method getScriptDataMap * Separate the clearing of script data into a method clearScriptData, leaving the clear method to its original meaning. If it's OK with all, I'll commit these changes today. Also, I'll make the script data cache thread safe... which will mean that you have to clear the cache from the thread that invoked it. This will preserve the threading guarantees for Tag implementations. I'll do this today, too. Hans -Original Message- From: Corey Scott [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 4:12 AM To: Jakarta Commons Developers List Subject: [Email] To release or not to release Can someone with commit priviledge please change email over from RC1 to v.1.0? The RC has been out for quite a while now and so far there are no complaints about this. There are several other things waiting for this release, e.g. a proposed change to the jelly email classes (change to Commons Email) and some proposed extensions to Email itself, so completing the release would be greatly appreciated. Many Thanks, Corey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Email] To release or not to release
Hans, the vote was for releasing commons-email, not Jelly. I'm +1 on your changes to Jelly :-) On Mon, 17 Jan 2005 14:07:00 -0500, Hans Gilde [EMAIL PROTECTED] wrote: I'm actually +1 *only* if we make the minor API changes that I suggested last week. These changes are to the new caching API: * Change setTagForScript in JellyContext to setScriptData. This method should take a key of type Script, not TagScript. * Also in JellyContext, change the name of tagHolderMap to scriptData. It shouldn't be a WeakHashMap. * All access to the scriptData map should be through a protected method getScriptDataMap * Separate the clearing of script data into a method clearScriptData, leaving the clear method to its original meaning. If it's OK with all, I'll commit these changes today. Also, I'll make the script data cache thread safe... which will mean that you have to clear the cache from the thread that invoked it. This will preserve the threading guarantees for Tag implementations. I'll do this today, too. Hans -Original Message- From: Corey Scott [mailto:[EMAIL PROTECTED] Sent: Monday, January 17, 2005 4:12 AM To: Jakarta Commons Developers List Subject: [Email] To release or not to release Can someone with commit priviledge please change email over from RC1 to v.1.0? The RC has been out for quite a while now and so far there are no complaints about this. There are several other things waiting for this release, e.g. a proposed change to the jelly email classes (change to Commons Email) and some proposed extensions to Email itself, so completing the release would be greatly appreciated. Many Thanks, Corey - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
