Re: [VOTE] Apache Geronimo BatchEE 2.0.0 - Binaries
+1 Am 1. Mai 2024 17:22:04 MESZ schrieb fpapon : >Hi everyone, > >A problem occured with the stagging repository of the release (the repo has >been dropped), so had to redeploy them to a new stagging repo. > >I submit Apache Geronimo BatchEE 2.0.0 release binaries to your vote. > >Staging Maven repository: >https://repository.apache.org/content/repositories/orgapachebatchee-1015 > >Please vote to approve this release: >[ ] +1 Approve the release >[ ] -1 Don't approve the release (please provide specific comments) > >This vote will be open for at least 72 hours. > >-- >-- >François >
[jira] [Closed] (GERONIMO-6864) Pass Batch TCK for EE10
[ https://issues.apache.org/jira/browse/GERONIMO-6864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed GERONIMO-6864. - Resolution: Abandoned > Pass Batch TCK for EE10 > --- > > Key: GERONIMO-6864 > URL: https://issues.apache.org/jira/browse/GERONIMO-6864 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: BatchEE > Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GERONIMO-6868) Upgrade test-dependencies (Joda Time 2.12.7 + Jackson 2.17.0)
[ https://issues.apache.org/jira/browse/GERONIMO-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed GERONIMO-6868. - Resolution: Abandoned > Upgrade test-dependencies (Joda Time 2.12.7 + Jackson 2.17.0) > - > > Key: GERONIMO-6868 > URL: https://issues.apache.org/jira/browse/GERONIMO-6868 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: BatchEE > Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Apache Geronimo BatchEE 2.0.0
Hi, thanks for preparing. +1 (non binding) Gruß Richard Am Montag, dem 22.04.2024 um 21:56 +0200 schrieb fpapon: > Hi everyone, > > I submit Apache Geronimo BatchEE 2.0.0 release to your vote. > > Release Notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924=12352769 > > Staging Maven repository: > https://repository.apache.org/content/repositories/orgapachebatchee-1012 > > Staging dist repository: > https://dist.apache.org/repos/dist/dev/geronimo/batchee/ > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. >
Re: [batch] 2.0.0 release?
Guess, you can go for it :-) I am done with my changes. Gruß Richard Am 21. April 2024 10:01:44 MESZ schrieb Francois Papon : >+1 > >I can try to run the release process if needed, just ask me :) > >regards, > >François > >On 19/04/2024 21:02, Richard Zowalla wrote: >> Hi all, >> >> since the TCK challenge is resolved and we are passing the full Batch >> TCK and updated most of the dependencies of BatchEE, what do you think >> about doing a 2.0.0 release? >> >> Gruß >> Richard
[batch] 2.0.0 release?
Hi all, since the TCK challenge is resolved and we are passing the full Batch TCK and updated most of the dependencies of BatchEE, what do you think about doing a 2.0.0 release? Gruß Richard
[jira] [Closed] (GERONIMO-6867) BVAL 3.0.0
[ https://issues.apache.org/jira/browse/GERONIMO-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed GERONIMO-6867. - Resolution: Duplicate > BVAL 3.0.0 > -- > > Key: GERONIMO-6867 > URL: https://issues.apache.org/jira/browse/GERONIMO-6867 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: BatchEE > Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GERONIMO-6866) OWB 4.0.2
[ https://issues.apache.org/jira/browse/GERONIMO-6866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed GERONIMO-6866. - Resolution: Duplicate > OWB 4.0.2 > - > > Key: GERONIMO-6866 > URL: https://issues.apache.org/jira/browse/GERONIMO-6866 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: BatchEE > Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GERONIMO-6865) OpenJPA 4.0.0
[ https://issues.apache.org/jira/browse/GERONIMO-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed GERONIMO-6865. - Resolution: Duplicate > OpenJPA 4.0.0 > - > > Key: GERONIMO-6865 > URL: https://issues.apache.org/jira/browse/GERONIMO-6865 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: BatchEE > Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GERONIMO-6863) Johnzon 2.0.1
[ https://issues.apache.org/jira/browse/GERONIMO-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed GERONIMO-6863. - Resolution: Duplicate > Johnzon 2.0.1 > - > > Key: GERONIMO-6863 > URL: https://issues.apache.org/jira/browse/GERONIMO-6863 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: BatchEE > Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GERONIMO-6862) JAXB Runtime 4.0.3
[ https://issues.apache.org/jira/browse/GERONIMO-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed GERONIMO-6862. - Resolution: Duplicate > JAXB Runtime 4.0.3 > -- > > Key: GERONIMO-6862 > URL: https://issues.apache.org/jira/browse/GERONIMO-6862 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: BatchEE > Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GERONIMO-6861) TomEE 10.0.0-M1
[ https://issues.apache.org/jira/browse/GERONIMO-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed GERONIMO-6861. - Resolution: Duplicate > TomEE 10.0.0-M1 > --- > > Key: GERONIMO-6861 > URL: https://issues.apache.org/jira/browse/GERONIMO-6861 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: BatchEE > Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > > Upgrade to TomEE 10.0.0-M1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Apache XBean 4.25 release
+1 (non-binding) Am Montag, dem 15.04.2024 um 17:43 +0200 schrieb Mark Struberg via dev: > +1 > > txs and LieGrue, > strub > > > > Am 15.04.2024 um 13:34 schrieb fpapon : > > > > Hi everyone, > > > > I submit Apache XBean 4.25 release to your vote. > > > > This release mainly includes (other issue description is available > > on > > the release note): > > > > * Bug > > - [XBEAN-343] - consistent handling of NoClassDefFoundError > > > > * Improvement > > - [XBEAN-345] - Upgrade to ASM 9.7 > > > > * Task > > - [XBEAN-342] - remove xbean-classpath module > > > > Staging Maven repository: > > https://repository.apache.org/content/repositories/orgapachegeronimo-1169 > > > > Staging dist repository: > > https://dist.apache.org/repos/dist/dev/geronimo/xbean/ > > > > Please vote to approve this release: > > [ ] +1 Approve the release > > [ ] -1 Don't approve the release (please provide specific comments) > > > > This vote will be open for at least 72 hours. > > > > -- > > -- > > François > > > signature.asc Description: This is a digitally signed message part
[jira] [Created] (GERONIMO-6868) Upgrade test-dependencies (Joda Time 2.12.7 + Jackson 2.17.0)
Richard Zowalla created GERONIMO-6868: - Summary: Upgrade test-dependencies (Joda Time 2.12.7 + Jackson 2.17.0) Key: GERONIMO-6868 URL: https://issues.apache.org/jira/browse/GERONIMO-6868 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: BatchEE Reporter: Richard Zowalla Assignee: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6867) BVAL 3.0.0
Richard Zowalla created GERONIMO-6867: - Summary: BVAL 3.0.0 Key: GERONIMO-6867 URL: https://issues.apache.org/jira/browse/GERONIMO-6867 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: BatchEE Reporter: Richard Zowalla Assignee: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6866) OWB 4.0.2
Richard Zowalla created GERONIMO-6866: - Summary: OWB 4.0.2 Key: GERONIMO-6866 URL: https://issues.apache.org/jira/browse/GERONIMO-6866 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: BatchEE Reporter: Richard Zowalla Assignee: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6865) OpenJPA 4.0.0
Richard Zowalla created GERONIMO-6865: - Summary: OpenJPA 4.0.0 Key: GERONIMO-6865 URL: https://issues.apache.org/jira/browse/GERONIMO-6865 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: BatchEE Reporter: Richard Zowalla Assignee: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6864) Pass Batch TCK for EE10
Richard Zowalla created GERONIMO-6864: - Summary: Pass Batch TCK for EE10 Key: GERONIMO-6864 URL: https://issues.apache.org/jira/browse/GERONIMO-6864 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: BatchEE Reporter: Richard Zowalla Assignee: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6862) JAXB Runtime 4.0.3
Richard Zowalla created GERONIMO-6862: - Summary: JAXB Runtime 4.0.3 Key: GERONIMO-6862 URL: https://issues.apache.org/jira/browse/GERONIMO-6862 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: BatchEE Reporter: Richard Zowalla Assignee: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GERONIMO-6861) TomEE 10.0.0-M1
[ https://issues.apache.org/jira/browse/GERONIMO-6861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6861: -- Fix Version/s: (was: 2.0) > TomEE 10.0.0-M1 > --- > > Key: GERONIMO-6861 > URL: https://issues.apache.org/jira/browse/GERONIMO-6861 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: BatchEE > Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > > Upgrade to TomEE 10.0.0-M1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6861) TomEE 10.0.0-M1
Richard Zowalla created GERONIMO-6861: - Summary: TomEE 10.0.0-M1 Key: GERONIMO-6861 URL: https://issues.apache.org/jira/browse/GERONIMO-6861 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: BatchEE Reporter: Richard Zowalla Assignee: Richard Zowalla Fix For: 2.0 Upgrade to TomEE 10.0.0-M1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6863) Johnzon 2.0.1
Richard Zowalla created GERONIMO-6863: - Summary: Johnzon 2.0.1 Key: GERONIMO-6863 URL: https://issues.apache.org/jira/browse/GERONIMO-6863 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: BatchEE Reporter: Richard Zowalla Assignee: Richard Zowalla -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (GERONIMO-6860) Remove dependency towards Apache James from Jakarta Mail Spec Jar
[ https://issues.apache.org/jira/browse/GERONIMO-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla closed GERONIMO-6860. - Resolution: Won't Do Going to close this as it isn't the actual issue. Depending on the outcome of the Mail Thread in the TomEE dev list, I will create a new issue to investigate the missed fixes between 1.4 and 1.6 (and 2.1) > Remove dependency towards Apache James from Jakarta Mail Spec Jar > - > > Key: GERONIMO-6860 > URL: https://issues.apache.org/jira/browse/GERONIMO-6860 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: 1.4-to-1.6.diff, > GERONIMO-Mail-Spec-Apache-James-Removal.patch > > > Seems the reference to mime4j from James was dropped between 1.5 ( > [https://github.com/apache/geronimo-specs/blob/0f0956795ad0839ec698e11fd3a7049f0114623c/geronimo-javamail_1.4_spec/src/main/java/javax/mail/internet/MimeUtility.java] > ) and 1.6 > ([https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-javamail_1.6_spec/src/main/java/javax/mail/internet/MimeUtility.java] > ) > We can drop it from the 2.1 mail spec jar as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GERONIMO-6860) Remove dependency towards Apache James from Jakarta Mail Spec Jar
[ https://issues.apache.org/jira/browse/GERONIMO-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832640#comment-17832640 ] Richard Zowalla commented on GERONIMO-6860: --- Here is the diff between [^1.4-to-1.6.diff] > Remove dependency towards Apache James from Jakarta Mail Spec Jar > - > > Key: GERONIMO-6860 > URL: https://issues.apache.org/jira/browse/GERONIMO-6860 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: 1.4-to-1.6.diff, > GERONIMO-Mail-Spec-Apache-James-Removal.patch > > > Seems the reference to mime4j from James was dropped between 1.5 ( > [https://github.com/apache/geronimo-specs/blob/0f0956795ad0839ec698e11fd3a7049f0114623c/geronimo-javamail_1.4_spec/src/main/java/javax/mail/internet/MimeUtility.java] > ) and 1.6 > ([https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-javamail_1.6_spec/src/main/java/javax/mail/internet/MimeUtility.java] > ) > We can drop it from the 2.1 mail spec jar as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GERONIMO-6860) Remove dependency towards Apache James from Jakarta Mail Spec Jar
[ https://issues.apache.org/jira/browse/GERONIMO-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6860: -- Attachment: 1.4-to-1.6.diff > Remove dependency towards Apache James from Jakarta Mail Spec Jar > - > > Key: GERONIMO-6860 > URL: https://issues.apache.org/jira/browse/GERONIMO-6860 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: 1.4-to-1.6.diff, > GERONIMO-Mail-Spec-Apache-James-Removal.patch > > > Seems the reference to mime4j from James was dropped between 1.5 ( > [https://github.com/apache/geronimo-specs/blob/0f0956795ad0839ec698e11fd3a7049f0114623c/geronimo-javamail_1.4_spec/src/main/java/javax/mail/internet/MimeUtility.java] > ) and 1.6 > ([https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-javamail_1.6_spec/src/main/java/javax/mail/internet/MimeUtility.java] > ) > We can drop it from the 2.1 mail spec jar as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GERONIMO-6860) Remove dependency towards Apache James from Jakarta Mail Spec Jar
[ https://issues.apache.org/jira/browse/GERONIMO-6860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832635#comment-17832635 ] Richard Zowalla commented on GERONIMO-6860: --- Romain mention in slack, that 1.5 was done from a random state of 1.4 and misses fixes. Therefore, 1.6 and 2.1 also miss these fixes, which means, that mime4j might be required and the attached patch is useless. Requires some more investigation / digging to see, what is actual missing from 1.4 in 2.1 :D > Remove dependency towards Apache James from Jakarta Mail Spec Jar > - > > Key: GERONIMO-6860 > URL: https://issues.apache.org/jira/browse/GERONIMO-6860 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-Mail-Spec-Apache-James-Removal.patch > > > Seems the reference to mime4j from James was dropped between 1.5 ( > [https://github.com/apache/geronimo-specs/blob/0f0956795ad0839ec698e11fd3a7049f0114623c/geronimo-javamail_1.4_spec/src/main/java/javax/mail/internet/MimeUtility.java] > ) and 1.6 > ([https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-javamail_1.6_spec/src/main/java/javax/mail/internet/MimeUtility.java] > ) > We can drop it from the 2.1 mail spec jar as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6860) Remove dependency towards Apache James from Jakarta Mail Spec Jar
Richard Zowalla created GERONIMO-6860: - Summary: Remove dependency towards Apache James from Jakarta Mail Spec Jar Key: GERONIMO-6860 URL: https://issues.apache.org/jira/browse/GERONIMO-6860 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: mail Reporter: Richard Zowalla Attachments: GERONIMO-Mail-Spec-Apache-James-Removal.patch Seems the reference to mime4j from James was dropped between 1.5 ( [https://github.com/apache/geronimo-specs/blob/0f0956795ad0839ec698e11fd3a7049f0114623c/geronimo-javamail_1.4_spec/src/main/java/javax/mail/internet/MimeUtility.java] ) and 1.6 ([https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-javamail_1.6_spec/src/main/java/javax/mail/internet/MimeUtility.java] ) We can drop it from the 2.1 mail spec jar as well -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Apache Geronimo BatchEE 1.0.4
+1 (non binding), thx! (staging repo works now) Am Samstag, dem 23.03.2024 um 20:07 +0100 schrieb Romain Manni-Bucau: > +1, thanks François. > > @rzo1 can you give it another try? > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book > > > Le sam. 23 mars 2024 à 18:35, Richard Zowalla a > écrit : > > Hi François, > > > > can you close the repo? > > > > 404 - Repository "orgapachebatchee-1011 (staging: open)" > > [id=orgapachebatchee-1011] exists but is not exposed. > > Repository "orgapachebatchee-1011 (staging: open)" > > [id=orgapachebatchee-1011] exists but is not exposed. > > > > Gruß > > Richard > > > > Am Freitag, dem 22.03.2024 um 21:40 +0100 schrieb fpapon: > > > Hi everyone, > > > > > > I submit Apache Geronimo BatchEE 1.0.4 release to your vote. > > > > > > Release Notes: > > > > > > * [BATCHEE-169] - Apache Parent POM 31 > > > * [BATCHEE-170] - Jackson 2.17.0 > > > * [BATCHEE-171] - Johnzon 1.2.21 > > > * [BATCHEE-172] - TomEE 8.0.16 > > > * [BATCHEE-173] - XBean 4.24 > > > * [BATCHEE-174] - Deltaspike 1.9.6 > > > * [BATCHEE-175] - Use createAnnotatedType(Class,String) to > > > avoid > > > NoSuchMethodErrors in CDI-4 > > > > > > Staging Maven repository: > > > https://repository.apache.org/content/repositories/orgapachebatchee-1011 > > > > > > Staging dist repository: > > > https://dist.apache.org/repos/dist/dev/geronimo/batchee/ > > > > > > Please vote to approve this release: > > > [ ] +1 Approve the release > > > [ ] -1 Don't approve the release (please provide specific > > > comments) > > > > > > This vote will be open for at least 72 hours. > > > > > > > > > François > > > > >
Re: [VOTE] Apache Geronimo BatchEE 1.0.4
Hi François, can you close the repo? 404 - Repository "orgapachebatchee-1011 (staging: open)" [id=orgapachebatchee-1011] exists but is not exposed. Repository "orgapachebatchee-1011 (staging: open)" [id=orgapachebatchee-1011] exists but is not exposed. Gruß Richard Am Freitag, dem 22.03.2024 um 21:40 +0100 schrieb fpapon: > Hi everyone, > > I submit Apache Geronimo BatchEE 1.0.4 release to your vote. > > Release Notes: > > * [BATCHEE-169] - Apache Parent POM 31 > * [BATCHEE-170] - Jackson 2.17.0 > * [BATCHEE-171] - Johnzon 1.2.21 > * [BATCHEE-172] - TomEE 8.0.16 > * [BATCHEE-173] - XBean 4.24 > * [BATCHEE-174] - Deltaspike 1.9.6 > * [BATCHEE-175] - Use createAnnotatedType(Class,String) to avoid > NoSuchMethodErrors in CDI-4 > > Staging Maven repository: > https://repository.apache.org/content/repositories/orgapachebatchee-1011 > > Staging dist repository: > https://dist.apache.org/repos/dist/dev/geronimo/batchee/ > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > > François >
Re: Release of BatchEE ?
As far as I can remember, yes. Am 19. März 2024 15:48:47 MEZ schrieb Francois Papon : >For TomEE it's just for tests purpose? > >On 19/03/2024 15:46, Richard Zowalla wrote: >> TomEE 10 requires BatchEE 2.0.0 :-) >> Don't know if we really need the Deltaspike integration (for now) >> >> >> Am 19. März 2024 15:42:11 MEZ schrieb Francois Papon >> : >> >> There is some SNAPSHOT dependencies used by BatchEE (tomEE and >> deltaspike): >> https://github.com/apache/geronimo-batchee/blob/master/pom.xml I >> think it would be better to not use SNAPSHOT in our release. WDYT? >> regards, François On 19/03/2024 14:47, Richard Zowalla wrote: >> >> Great. Go for it, François :) TCK runs in GH actions. Am >> Dienstag, dem 19.03.2024 um 11:59 +0100 schrieb Francois Papon: >> >> Sounds good :) Let me give it a try. regards, François On >> 19/03/2024 11:37, Romain Manni-Bucau wrote: >> >> Hi, mainly just "mvn release:prepare release:perform" >> then standard ASF process (dist area), my totally >> unwritten and unofficial tip would be to 1. ensure the >> build passes (mvn install) with tcks then deactivate >> the tests (skipTests in a profile property of your >> settings.xml) since it is long and totally useless >> during the release. Romain Manni-Bucau @rmannibucau >> | Blog | Old Blog | Github | LinkedIn | Book Le mar. >> 19 mars 2024 à 10:42, Francois Papon >> a écrit : >> >> Hi, I never did release for BatchEE before but if >> it can help I can try to run the process. >> regards, François On 19/03/2024 09:34, Richard >> Zowalla wrote: > Hey all, > > since the PR got >> merged, can anyone trigger a release for BatchEE >> 2.0.0 > ? The TCK challenge is open and might >> take some more time until it is > resolved, but I >> don't think, that we need to wait that long. > > >> wdyt? > > Gruß > Richard >
Re: Release of BatchEE ?
TomEE 10 requires BatchEE 2.0.0 :-) Don't know if we really need the Deltaspike integration (for now) Am 19. März 2024 15:42:11 MEZ schrieb Francois Papon : >There is some SNAPSHOT dependencies used by BatchEE (tomEE and deltaspike): > >https://github.com/apache/geronimo-batchee/blob/master/pom.xml > >I think it would be better to not use SNAPSHOT in our release. > >WDYT? > >regards, > >François > >On 19/03/2024 14:47, Richard Zowalla wrote: >> Great. Go for it, François :) >> TCK runs in GH actions. >> >> Am Dienstag, dem 19.03.2024 um 11:59 +0100 schrieb Francois Papon: >>> Sounds good :) >>> Let me give it a try. >>> regards, >>> François >>> On 19/03/2024 11:37, Romain Manni-Bucau wrote: >>> >>>> Hi, >>>> >>>> mainly just "mvn release:prepare release:perform" then standard ASF >>>> process (dist area), my totally unwritten and unofficial tip would >>>> be to 1. ensure the build passes (mvn install) with tcks then >>>> deactivate the tests (skipTests in a profile property of your >>>> settings.xml) since it is long and totally useless during the >>>> release. >>>> >>>> Romain Manni-Bucau >>>> @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book >>>> Le mar. 19 mars 2024 à 10:42, Francois Papon >>>> a écrit : >>>> >>>>> Hi, >>>>> I never did release for BatchEE before but if it can help I can >>>>> try to >>>>> run the process. >>>>> regards, >>>>> François >>>>> On 19/03/2024 09:34, Richard Zowalla wrote: >>>>> > Hey all, >>>>> > >>>>> > since the PR got merged, can anyone trigger a release for >>>>> BatchEE 2.0.0 >>>>> > ? The TCK challenge is open and might take some more time >>>>> until it is >>>>> > resolved, but I don't think, that we need to wait that long. >>>>> > >>>>> > wdyt? >>>>> > >>>>> > Gruß >>>>> > Richard >>>>> > >>>>> >>>
Re: Release of BatchEE ?
Great. Go for it, François :) TCK runs in GH actions. Am Dienstag, dem 19.03.2024 um 11:59 +0100 schrieb Francois Papon: > Sounds good :) > Let me give it a try. > regards, > François > On 19/03/2024 11:37, Romain Manni-Bucau wrote: > > > > > Hi, > > > > mainly just "mvn release:prepare release:perform" then standard ASF > > process (dist area), my totally unwritten and unofficial tip would > > be to 1. ensure the build passes (mvn install) with tcks then > > deactivate the tests (skipTests in a profile property of your > > settings.xml) since it is long and totally useless during the > > release. > > > > Romain Manni-Bucau > > @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book > > > > > > Le mar. 19 mars 2024 à 10:42, Francois Papon > > a écrit : > > > > > Hi, > > > > > > I never did release for BatchEE before but if it can help I can > > > try to > > > run the process. > > > > > > regards, > > > > > > François > > > > > > On 19/03/2024 09:34, Richard Zowalla wrote: > > > > Hey all, > > > > > > > > since the PR got merged, can anyone trigger a release for > > > BatchEE 2.0.0 > > > > ? The TCK challenge is open and might take some more time > > > until it is > > > > resolved, but I don't think, that we need to wait that long. > > > > > > > > wdyt? > > > > > > > > Gruß > > > > Richard > > > > > > > >
Release of BatchEE ?
Hey all, since the PR got merged, can anyone trigger a release for BatchEE 2.0.0 ? The TCK challenge is open and might take some more time until it is resolved, but I don't think, that we need to wait that long. wdyt? Gruß Richard
Re: Milestone / Alpha Release of geronimo-txmanager?
+1 Am Freitag, dem 20.10.2023 um 09:07 +0200 schrieb Francois Papon: > I can try to launch the release process if everyone is ok :) > > On 19/10/2023 21:48, Richard Zowalla wrote: > > > > > Sounds like consent for a final. Can anyone roll a release? :-) > > > > > > Am 19. Oktober 2023 21:43:20 MESZ schrieb Jean-Louis MONTEIRO > > : > > > > > +1 for final and then patch version if there is a bug > > > > > > Le jeu. 19 oct. 2023, 21:08, Francois Papon > > > a écrit : > > > > > > > +1 for a final :) > > > > On 19/10/2023 19:44, Romain Manni-Bucau wrote: > > > > > > > > > so let's do a final would be my 2 cts ;) > > > > > > > > > > Romain Manni-Bucau > > > > > @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book > > > > > > > > > > > > > > > Le jeu. 19 oct. 2023 à 19:17, Richard Zowalla > > > > > a écrit : > > > > > > > > > > > Don't think anything more than the jakarta migration (which > > > > > > is done) is planned at the moment, so I am fine either way > > > > > > ;-) > > > > > > > > > > > > > > > > > > Am 19. Oktober 2023 19:00:35 MESZ schrieb Romain Manni- > > > > > > Bucau : > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > How far are we from a final? > > > > > > > I'm generally quite hesitant regarding alpha/beta/M if > > > > > > > real work is not planned and AFAIK we don't plan anything > > > > > > > there so we can try to jump to the final directly. > > > > > > > > > > > > > > Romain Manni-Bucau > > > > > > > @rmannibucau | Blog | Old Blog | Github | LinkedIn | > > > > > > > Book > > > > > > > > > > > > > > > > > > > > > Le jeu. 19 oct. 2023 à 18:53, Richard Zowalla > > > > > > > a écrit : > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > can we do a a milestone release (4.0.0-M1 or similar) > > > > > > > > of > > > > > > > > https://github.com/apache/geronimo-txmanager ? > > > > > > > > > > > > > > > > I would like to build TomEE 10.x against a stable > > > > > > > > version of > > > > > > > > the txmanager, so we might be able to do a > > > > > > > > milestone/alpha release of a > > > > > > > > TomEE 10 since the normal build is looking good. > > > > > > > > > > > > > > > > Gruß > > > > > > > > Richard > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: Milestone / Alpha Release of geronimo-txmanager?
Sounds like consent for a final. Can anyone roll a release? :-) Am 19. Oktober 2023 21:43:20 MESZ schrieb Jean-Louis MONTEIRO : >+1 for final and then patch version if there is a bug > >Le jeu. 19 oct. 2023, 21:08, Francois Papon >a écrit : > >> +1 for a final :) >> On 19/10/2023 19:44, Romain Manni-Bucau wrote: >> >> so let's do a final would be my 2 cts ;) >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <https://rmannibucau.metawerx.net/> | Old Blog >> <http://rmannibucau.wordpress.com> | Github >> <https://github.com/rmannibucau> | LinkedIn >> <https://www.linkedin.com/in/rmannibucau> | Book >> <https://www.packtpub.com/application-development/java-ee-8-high-performance> >> >> >> Le jeu. 19 oct. 2023 à 19:17, Richard Zowalla a >> écrit : >> >>> Don't think anything more than the jakarta migration (which is done) is >>> planned at the moment, so I am fine either way ;-) >>> >>> >>> Am 19. Oktober 2023 19:00:35 MESZ schrieb Romain Manni-Bucau < >>> rmannibu...@gmail.com>: >>> >>>> Hi, >>>> >>>> How far are we from a final? >>>> I'm generally quite hesitant regarding alpha/beta/M if real work is not >>>> planned and AFAIK we don't plan anything there so we can try to jump to the >>>> final directly. >>>> >>>> Romain Manni-Bucau >>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog >>>> <https://rmannibucau.metawerx.net/> | Old Blog >>>> <http://rmannibucau.wordpress.com> | Github >>>> <https://github.com/rmannibucau> | LinkedIn >>>> <https://www.linkedin.com/in/rmannibucau> | Book >>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance> >>>> >>>> >>>> Le jeu. 19 oct. 2023 à 18:53, Richard Zowalla a >>>> écrit : >>>> >>>>> Hi all, >>>>> >>>>> can we do a a milestone release (4.0.0-M1 or similar) of >>>>> https://github.com/apache/geronimo-txmanager ? >>>>> >>>>> I would like to build TomEE 10.x against a stable version of >>>>> the txmanager, so we might be able to do a milestone/alpha release of a >>>>> TomEE 10 since the normal build is looking good. >>>>> >>>>> Gruß >>>>> Richard >>>>> >>>>> >>>>>
Re: Milestone / Alpha Release of geronimo-txmanager?
Don't think anything more than the jakarta migration (which is done) is planned at the moment, so I am fine either way ;-) Am 19. Oktober 2023 19:00:35 MESZ schrieb Romain Manni-Bucau : >Hi, > >How far are we from a final? >I'm generally quite hesitant regarding alpha/beta/M if real work is not >planned and AFAIK we don't plan anything there so we can try to jump to the >final directly. > >Romain Manni-Bucau >@rmannibucau <https://twitter.com/rmannibucau> | Blog ><https://rmannibucau.metawerx.net/> | Old Blog ><http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | >LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book ><https://www.packtpub.com/application-development/java-ee-8-high-performance> > > >Le jeu. 19 oct. 2023 à 18:53, Richard Zowalla a >écrit : > >> Hi all, >> >> can we do a a milestone release (4.0.0-M1 or similar) of >> https://github.com/apache/geronimo-txmanager ? >> >> I would like to build TomEE 10.x against a stable version of >> the txmanager, so we might be able to do a milestone/alpha release of a >> TomEE 10 since the normal build is looking good. >> >> Gruß >> Richard >> >> >>
Milestone / Alpha Release of geronimo-txmanager?
Hi all, can we do a a milestone release (4.0.0-M1 or similar) of https://github.com/apache/geronimo-txmanager ? I would like to build TomEE 10.x against a stable version of the txmanager, so we might be able to do a milestone/alpha release of a TomEE 10 since the normal build is looking good. Gruß Richard
Re: Status BatchEE-2.0.0
Hi, aside from the upgrade killing our active waiting strategy in the tests for the DirectEndpoint, I am seeing Caused by: java.lang.ClassNotFoundException: javax.activation.DataHandler at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClass Loader.java:641) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(Cla ssLoaders.java:188) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:520) ... 82 more with the 2.25.x version of camel during the tests (if I workaround the protected getConsumer() via a wrapper strategy, see [1]). However, the tests will pass... This gives me the impression, that Camel 2.x isn't jakarta ready. From looking into their Jira it seems, that Camel 4.x will be jakarta ready (Java 17 as baseline) but for now upgrading would make it rather useless (or we would need to relocate). Gruß Richard [1] https://github.com/rzo1/geronimo-batchee/commit/6cc27362b7a0bb34a8bd3d39a1fe35c4a5f834b3 Am Freitag, dem 21.04.2023 um 13:13 +0200 schrieb Mark Struberg via dev: > Hi folks! > > I've now finished the work on BatchEE-2.0.0. > I think we have to enable the TCK still, but all our internal tests > do work again. > > Note that I had to move back to an old Camel version due to getting > test errors with a newer version. > Would be great if someone could please take a look at it! > > LieGrue, > strub
[jira] [Commented] (GERONIMO-6846) Replace Dependency Towards SLF4J with JUL in TX Manager
[ https://issues.apache.org/jira/browse/GERONIMO-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675584#comment-17675584 ] Richard Zowalla commented on GERONIMO-6846: --- Related to https://github.com/apache/geronimo-txmanager/pull/8 > Replace Dependency Towards SLF4J with JUL in TX Manager > --- > > Key: GERONIMO-6846 > URL: https://issues.apache.org/jira/browse/GERONIMO-6846 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: transaction manager > Reporter: Richard Zowalla >Priority: Major > > as the title says -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GERONIMO-6847) Switch Language Level to 11 in TX Manager
[ https://issues.apache.org/jira/browse/GERONIMO-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675583#comment-17675583 ] Richard Zowalla commented on GERONIMO-6847: --- Related to https://github.com/apache/geronimo-txmanager/pull/8 > Switch Language Level to 11 in TX Manager > - > > Key: GERONIMO-6847 > URL: https://issues.apache.org/jira/browse/GERONIMO-6847 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: transaction manager > Reporter: Richard Zowalla >Priority: Major > > as the title says -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GERONIMO-6846) Replace Dependency Towards SLF4J with JUL in TX Manager
[ https://issues.apache.org/jira/browse/GERONIMO-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6846: -- Summary: Replace Dependency Towards SLF4J with JUL in TX Manager (was: Replace Dependency Towards SLF4J iwith JUL in TX Manager) > Replace Dependency Towards SLF4J with JUL in TX Manager > --- > > Key: GERONIMO-6846 > URL: https://issues.apache.org/jira/browse/GERONIMO-6846 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: transaction manager > Reporter: Richard Zowalla >Priority: Major > > as the title says -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GERONIMO-6846) Replace Dependency Towards SLF4J iwith JUL in TX Manager
[ https://issues.apache.org/jira/browse/GERONIMO-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6846: -- Summary: Replace Dependency Towards SLF4J iwith JUL in TX Manager (was: Remove Dependency Towards SLF4J in TX Manager) > Replace Dependency Towards SLF4J iwith JUL in TX Manager > > > Key: GERONIMO-6846 > URL: https://issues.apache.org/jira/browse/GERONIMO-6846 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: transaction manager > Reporter: Richard Zowalla >Priority: Major > > as the title says -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6847) Switch Language Level to 11 in TX Manager
Richard Zowalla created GERONIMO-6847: - Summary: Switch Language Level to 11 in TX Manager Key: GERONIMO-6847 URL: https://issues.apache.org/jira/browse/GERONIMO-6847 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: transaction manager Reporter: Richard Zowalla as the title says -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6846) Remove Dependency Towards SLF4J in TX Manager
Richard Zowalla created GERONIMO-6846: - Summary: Remove Dependency Towards SLF4J in TX Manager Key: GERONIMO-6846 URL: https://issues.apache.org/jira/browse/GERONIMO-6846 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: transaction manager Reporter: Richard Zowalla as the title says -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GERONIMO-6845) Provide Genesis Flava for Java 11
[ https://issues.apache.org/jira/browse/GERONIMO-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17669030#comment-17669030 ] Richard Zowalla commented on GERONIMO-6845: --- Yup - I am also open to just use `apache-parent` (for the specific use-case). Whatever the project decides :) > Provide Genesis Flava for Java 11 > - > > Key: GERONIMO-6845 > URL: https://issues.apache.org/jira/browse/GERONIMO-6845 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6845.patch > > > as the title says. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (GERONIMO-6845) Provide Genesis Flava for Java 11
[ https://issues.apache.org/jira/browse/GERONIMO-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6845: -- Attachment: GERONIMO-6845.patch > Provide Genesis Flava for Java 11 > - > > Key: GERONIMO-6845 > URL: https://issues.apache.org/jira/browse/GERONIMO-6845 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6845.patch > > > as the title says. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6845) Provide Genesis Flava for Java 11
Richard Zowalla created GERONIMO-6845: - Summary: Provide Genesis Flava for Java 11 Key: GERONIMO-6845 URL: https://issues.apache.org/jira/browse/GERONIMO-6845 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Reporter: Richard Zowalla as the title says. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (GERONIMO-6844) Jakarta Version of Geronimo TX Manager
[ https://issues.apache.org/jira/browse/GERONIMO-6844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17663212#comment-17663212 ] Richard Zowalla commented on GERONIMO-6844: --- https://github.com/apache/geronimo-txmanager/pull/8 > Jakarta Version of Geronimo TX Manager > -- > > Key: GERONIMO-6844 > URL: https://issues.apache.org/jira/browse/GERONIMO-6844 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: transaction manager > Reporter: Richard Zowalla >Priority: Major > > We should provide related standalone artifacts without the need to shade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (GERONIMO-6844) Jakarta Version of Geronimo TX Manager
Richard Zowalla created GERONIMO-6844: - Summary: Jakarta Version of Geronimo TX Manager Key: GERONIMO-6844 URL: https://issues.apache.org/jira/browse/GERONIMO-6844 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: transaction manager Reporter: Richard Zowalla We should provide related standalone artifacts without the need to shade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [DISCUSS] Move microprofile impl to Apache TomEE
Hi, CC'ing dev@tomee here to ensure the discussion is seen. It is true, that TomEE moved to smallrye to update MP to 5.0 (jakarta) due to a lack of contributors / resources to ramp up updated versions in Geronimo. I have no strong opinion about switching the project umbrella as it wouldn't change anything regarding contributions, I guess. Gruß Richard Am Dienstag, dem 14.06.2022 um 08:37 +0200 schrieb Romain Manni-Bucau: > Hi all, > > TomEE people didn't send much feedback and I know they are moving to > smallrye so can be great to know if we must continue this way or just > freeze the projects there? > Anyone able to comment? > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book > > > Le jeu. 9 juin 2022 à 11:32, Jean-Baptiste Onofré a > écrit : > > OK, it sounds good to me then. > > > > Regards > > JB > > > > On Thu, Jun 9, 2022 at 8:13 AM Romain Manni-Bucau < > > rmannibu...@gmail.com> wrote: > > > > > > Hi > > > > > > Next step is likely to ask tomee since for now we just get the > > consensus geronimo is a bad home for MP. > > > > > > If ok for them, I'd just move the project to tomee since, as > > mentionned, we didnt work much on these projects and tomee was > > driven last activity but guess it can be discussed on tomee thread > > once created. > > > > > > Le jeu. 9 juin 2022 à 07:50, Jean-Baptiste Onofré < > > j...@nanthrax.net> a écrit : > > >> > > >> +1, it makes sense to me. > > >> > > >> I guess we gonna do a vote. The question is about the > > governance/PMC : > > >> I do we plan to move PMC from Geronimo to Tomee or "just" use > > Tomee > > >> PMC ? > > >> > > >> Regards > > >> JB > > >> > > >> On Mon, Jun 6, 2022 at 10:59 AM fpapon > > wrote: > > >> > > > >> > Hi all, > > >> > > > >> > I would like to start a thread to discuss about the future of > > the Apache > > >> > Geronimo Microprofile implementation: > > >> > > > >> > https://geronimo.apache.org/microprofile/ > > >> > > > >> > As we can see, we don't have a lot of traction about the > > maintenance of > > >> > the implementation to be up-to-date with the Microprofile > > specification. > > >> > > > >> > The J2EE Geronimo server is no longer exist and at Apache, the > > active EE > > >> > server seems to be Apache TomEE. > > >> > > > >> > May be it could make more sense to move the Microprofile > > implementation > > >> > to the Apache TomEE umbrella. > > >> > > > >> > WDYT? > > >> > > > >> > regards, > > >> > > > >> > -- > > >> > -- > > >> > François > > >> >
[jira] [Comment Edited] (GERONIMO-6835) Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
[
https://issues.apache.org/jira/browse/GERONIMO-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541671#comment-17541671
]
Richard Zowalla edited comment on GERONIMO-6835 at 5/24/22 7:43 PM:
Bootstraping the mailbox "test1" from the TCK fails for one (mail no. 9) of the
mails:
https://github.com/eclipse-ee4j/mail-tck/blob/2.0.0/tests/mailboxes/test1/9
This specific mail fails with
{code:java}
a5 APPEND test1 () "8-Dec-1996 15:30:12 +0100" {150432}
a5 BAD APPEND failed. Illegal arguments.
Unexpected command IMAP command error
org.apache.geronimo.mail.util.InvalidCommandException: Unexpected command IMAP
command error
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.receiveResponse(IMAPConnection.java:412)
at
org.apache.geronimo.mail.store.imap.connection.IMAPCommand.writeTo(IMAPCommand.java:200)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendCommand(IMAPConnection.java:320)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendSimpleCommand(IMAPConnection.java:288)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.appendMessage(IMAPConnection.java:1455)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessage(IMAPFolder.java:1562)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessages(IMAPFolder.java:977)
at fpopulate.copyMessages(fpopulate.java:209)
at fpopulate.copy(fpopulate.java:136)
at fpopulate.main(fpopulate.java:107)
{code}
while it works for the reference impl:
{code:java}
A6 APPEND test1 () "08-Dec-1996 15:30:12 +0100" {153113+}
A6 OK [APPENDUID 466034631 1] APPEND completed.
Copied 1 messages
{code}
Targeting the same mail server. Note the difference in the literal header. Most
of the TCK tests fail with a similar exception.
* To reproduce follow the instructions in tck.adoc (docker-compose + starting
test mail)
* Copy "fpopulate" to the geronimo project.
* Add the message from above into a folder and call the file "1".
* Run "fpopulate" with arguments "-s -d
imap://user01%40james.local:1234@localhost:1143 -D"
The same procedere works for the RI, so there might be a difference somewhere.
was (Author: rzo1):
Bootstraping the mailbox "test1" from the TCK fails for one (mail no. 9) of the
mails contained in there:
{code:java}
{code}
This specific mail fails with
{code:java}
a5 APPEND test1 () "8-Dec-1996 15:30:12 +0100" {150432}
a5 BAD APPEND failed. Illegal arguments.
Unexpected command IMAP command error
org.apache.geronimo.mail.util.InvalidCommandException: Unexpected command IMAP
command error
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.receiveResponse(IMAPConnection.java:412)
at
org.apache.geronimo.mail.store.imap.connection.IMAPCommand.writeTo(IMAPCommand.java:200)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendCommand(IMAPConnection.java:320)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendSimpleCommand(IMAPConnection.java:288)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.appendMessage(IMAPConnection.java:1455)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessage(IMAPFolder.java:1562)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessages(IMAPFolder.java:977)
at fpopulate.copyMessages(fpopulate.java:209)
at fpopulate.copy(fpopulate.java:136)
at fpopulate.main(fpopulate.java:107)
{code}
while it works for the reference impl:
{code:java}
A6 APPEND test1 () "08-Dec-1996 15:30:12 +0100" {153113+}
A6 OK [APPENDUID 466034631 1] APPEND completed.
Copied 1 messages
{code}
Targeting the same mail server. Note the difference in the literal header. Most
of the TCK tests fail with a similar exception.
* To reproduce follow the instructions in tck.adoc (docker-compose + starting
test mail)
* Copy "fpopulate" to the geronimo project.
* Add the message from above into a folder and call the file "1".
* Run "fpopulate" with arguments "-s -d
imap://user01%40james.local:1234@localhost:1143 -D"
The same procedere works for the RI, so there might be a difference somewhere.
> Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
> -
>
> Key: GERONIMO-6835
> URL: https://issues.apache.org/jira/browse/GERONIMO-6835
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: mail
>Reporter: Richard Zowalla
>Priority: Major
>
> Current
[jira] [Comment Edited] (GERONIMO-6835) Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
[
https://issues.apache.org/jira/browse/GERONIMO-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541671#comment-17541671
]
Richard Zowalla edited comment on GERONIMO-6835 at 5/24/22 7:43 PM:
Bootstraping the mailbox "test1" from the TCK fails for one (mail no. 9) of the
mails contained in there:
{code:java}
{code}
This specific mail fails with
{code:java}
a5 APPEND test1 () "8-Dec-1996 15:30:12 +0100" {150432}
a5 BAD APPEND failed. Illegal arguments.
Unexpected command IMAP command error
org.apache.geronimo.mail.util.InvalidCommandException: Unexpected command IMAP
command error
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.receiveResponse(IMAPConnection.java:412)
at
org.apache.geronimo.mail.store.imap.connection.IMAPCommand.writeTo(IMAPCommand.java:200)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendCommand(IMAPConnection.java:320)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendSimpleCommand(IMAPConnection.java:288)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.appendMessage(IMAPConnection.java:1455)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessage(IMAPFolder.java:1562)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessages(IMAPFolder.java:977)
at fpopulate.copyMessages(fpopulate.java:209)
at fpopulate.copy(fpopulate.java:136)
at fpopulate.main(fpopulate.java:107)
{code}
while it works for the reference impl:
{code:java}
A6 APPEND test1 () "08-Dec-1996 15:30:12 +0100" {153113+}
A6 OK [APPENDUID 466034631 1] APPEND completed.
Copied 1 messages
{code}
Targeting the same mail server. Note the difference in the literal header. Most
of the TCK tests fail with a similar exception.
* To reproduce follow the instructions in tck.adoc (docker-compose + starting
test mail)
* Copy "fpopulate" to the geronimo project.
* Add the message from above into a folder and call the file "1".
* Run "fpopulate" with arguments "-s -d
imap://user01%40james.local:1234@localhost:1143 -D"
The same procedere works for the RI, so there might be a difference somewhere.
was (Author: rzo1):
Bootstraping the mailbox "test1" from the TCK fails for one of the mails
contained in there:
{code:java}
>From jmk@cochin Thu Feb 12 14:06:35 1998 -0800
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javamail@rita
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
{code}
This specific mail fails with
{code:java}
a5 APPEND test1 () "9-Aug-1997 02:23:05 +0200" {1399}
a5 BAD APPEND failed. Illegal arguments.
Unexpected command IMAP command error
org.apache.geronimo.mail.util.InvalidCommandException: Unexpected command IMAP
command error
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.receiveResponse(IMAPConnection.java:412)
at
org.apache.geronimo.mail.store.imap.connection.IMAPCommand.writeTo(IMAPCommand.java:200)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendCommand(IMAPConnection.java:320)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendSimpleCommand(IMAPConnection.java:288)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.appendMessage(IMAPConnection.java:1455)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessage(IMAPFolder.java:1562)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessages(IMAPFolder.java:977)
at fpopu
[jira] [Comment Edited] (GERONIMO-6835) Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
[
https://issues.apache.org/jira/browse/GERONIMO-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541671#comment-17541671
]
Richard Zowalla edited comment on GERONIMO-6835 at 5/24/22 7:31 PM:
Bootstraping the mailbox "test1" from the TCK fails for one of the mails
contained in there:
{code:java}
>From jmk@cochin Thu Feb 12 14:06:35 1998 -0800
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javamail@rita
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
{code}
This specific mail fails with
{code:java}
a5 APPEND test1 () "9-Aug-1997 02:23:05 +0200" {1399}
a5 BAD APPEND failed. Illegal arguments.
Unexpected command IMAP command error
org.apache.geronimo.mail.util.InvalidCommandException: Unexpected command IMAP
command error
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.receiveResponse(IMAPConnection.java:412)
at
org.apache.geronimo.mail.store.imap.connection.IMAPCommand.writeTo(IMAPCommand.java:200)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendCommand(IMAPConnection.java:320)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendSimpleCommand(IMAPConnection.java:288)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.appendMessage(IMAPConnection.java:1455)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessage(IMAPFolder.java:1562)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessages(IMAPFolder.java:977)
at fpopulate.copyMessages(fpopulate.java:209)
at fpopulate.copy(fpopulate.java:136)
at fpopulate.main(fpopulate.java:107)
{code}
while it works for the reference impl:
{code:java}
A6 APPEND test1 () "09-Aug-1997 02:23:05 +0200" {1418+}
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javamail@rita
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
A6 OK [APPENDUID 207446323 1] APPEND completed.
{code}
Targeting the same mail server. Note the difference in the literal header. Most
of the TCK tests fail with a similar exception.
* To reproduce follow the instructions in tck.adoc (docker-compose + starting
test mail)
* Copy "fpopulate" to the geronimo project.
* Add the message from above into a folder and call the file "1".
* Run "fpopulate"
[jira] [Comment Edited] (GERONIMO-6835) Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
[
https://issues.apache.org/jira/browse/GERONIMO-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541671#comment-17541671
]
Richard Zowalla edited comment on GERONIMO-6835 at 5/24/22 7:30 PM:
Bootstraping the mailbox "test1" from the TCK fails for one of the mails
contained in there:
{code:java}
>From jmk@cochin Thu Feb 12 14:06:35 1998 -0800
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javamail@rita
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
{code}
This specific mail fails with
{code:java}
a5 APPEND test1 () "9-Aug-1997 02:23:05 +0200" {1399}
a5 BAD APPEND failed. Illegal arguments.
Unexpected command IMAP command error
org.apache.geronimo.mail.util.InvalidCommandException: Unexpected command IMAP
command error
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.receiveResponse(IMAPConnection.java:412)
at
org.apache.geronimo.mail.store.imap.connection.IMAPCommand.writeTo(IMAPCommand.java:200)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendCommand(IMAPConnection.java:320)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendSimpleCommand(IMAPConnection.java:288)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.appendMessage(IMAPConnection.java:1455)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessage(IMAPFolder.java:1562)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessages(IMAPFolder.java:977)
at fpopulate.copyMessages(fpopulate.java:209)
at fpopulate.copy(fpopulate.java:136)
at fpopulate.main(fpopulate.java:107)
{code}
while it works for the reference impl:
{code:java}
A6 APPEND test1 () "09-Aug-1997 02:23:05 +0200" {1418+}
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javam...@rita.de
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
A6 OK [APPENDUID 207446323 1] APPEND completed.
{code}
Targeting the same mail server. Note the difference in the literal header. Most
of the TCK tests fail with a similar exception.
* To reproduce follow the instructions in tck.adoc (docker-compose + starting
test mail)
* Copy "fpopulate" to the geronimo project.
* Add the message from above into a folder and call the file "1".
* Run "fpopulate"
[jira] [Comment Edited] (GERONIMO-6835) Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
[
https://issues.apache.org/jira/browse/GERONIMO-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541671#comment-17541671
]
Richard Zowalla edited comment on GERONIMO-6835 at 5/24/22 7:03 PM:
Bootstraping the mailbox "test1" from the TCK fails for one of the mails
contained in there:
{code:java}
>From jmk@cochin Thu Feb 12 14:06:35 1998 -0800
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javam...@rita.de
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
{code}
This specific mail fails with
{code:java}
a5 APPEND test1 () "9-Aug-1997 02:23:05 +0200" {1399}
a5 BAD APPEND failed. Illegal arguments.
Unexpected command IMAP command error
org.apache.geronimo.mail.util.InvalidCommandException: Unexpected command IMAP
command error
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.receiveResponse(IMAPConnection.java:412)
at
org.apache.geronimo.mail.store.imap.connection.IMAPCommand.writeTo(IMAPCommand.java:200)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendCommand(IMAPConnection.java:320)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendSimpleCommand(IMAPConnection.java:288)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.appendMessage(IMAPConnection.java:1455)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessage(IMAPFolder.java:1562)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessages(IMAPFolder.java:977)
at fpopulate.copyMessages(fpopulate.java:209)
at fpopulate.copy(fpopulate.java:136)
at fpopulate.main(fpopulate.java:107)
{code}
while it works for the reference impl:
{code:java}
A6 APPEND test1 () "09-Aug-1997 02:23:05 +0200" {1418+}
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javam...@rita.de
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
A6 OK [APPENDUID 207446323 1] APPEND completed.
{code}
Targeting the same mail server. Note the difference in the literal header. Most
of the TCK tests fail with a similar exception.
* To reproduce follow the instructions in tck.adoc (docker-compose + starting
test mail)
* Copy "fpopulate" to the geronimo project.
* Add the message from above into a folder and call the file "1".
* Run "fpopul
[jira] [Comment Edited] (GERONIMO-6835) Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
[
https://issues.apache.org/jira/browse/GERONIMO-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541671#comment-17541671
]
Richard Zowalla edited comment on GERONIMO-6835 at 5/24/22 7:02 PM:
Bootstraping the mailbox "test1" from the TCK fails for one of the mails
contained in there:
{code:java}
>From jmk@cochin Thu Feb 12 14:06:35 1998 -0800
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javam...@rita.de
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
{code}
This specific mail fails with
{code:java}
a5 APPEND test1 () "9-Aug-1997 02:23:05 +0200" {1399}
a5 BAD APPEND failed. Illegal arguments.
Unexpected command IMAP command error
org.apache.geronimo.mail.util.InvalidCommandException: Unexpected command IMAP
command error
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.receiveResponse(IMAPConnection.java:412)
at
org.apache.geronimo.mail.store.imap.connection.IMAPCommand.writeTo(IMAPCommand.java:200)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendCommand(IMAPConnection.java:320)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendSimpleCommand(IMAPConnection.java:288)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.appendMessage(IMAPConnection.java:1455)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessage(IMAPFolder.java:1562)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessages(IMAPFolder.java:977)
at fpopulate.copyMessages(fpopulate.java:209)
at fpopulate.copy(fpopulate.java:136)
at fpopulate.main(fpopulate.java:107)
{code}
while it works for the reference impl:
{code:java}
A6 APPEND test1 () "09-Aug-1997 02:23:05 +0200" {1418+}
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javam...@rita.de
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
A6 OK [APPENDUID 207446323 1] APPEND completed.
{code}
Targeting the same mail server. Note the difference in the literal header. Most
of the TCK tests fail with a similar exception.
* To reproduce follow the instructions in tck.adoc (docker-compose + starting
test mail)
* Copy "fpopulate" to the geronimo project.
* Add the message from above into a folder
* Run "fpopulate" with arguments "-s -d
[jira] [Commented] (GERONIMO-6835) Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
[
https://issues.apache.org/jira/browse/GERONIMO-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541671#comment-17541671
]
Richard Zowalla commented on GERONIMO-6835:
---
Bootstraping the mailbox "test1" from the TCK fails for one of the mails
contained in there:
{code:java}
>From jmk@cochin Thu Feb 12 14:06:35 1998 -0800
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javam...@rita.de
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
{code}
This specific mail fails with
{code:java}
a5 APPEND test1 () "9-Aug-1997 02:23:05 +0200" {1399}
a5 BAD APPEND failed. Illegal arguments.
Unexpected command IMAP command error
org.apache.geronimo.mail.util.InvalidCommandException: Unexpected command IMAP
command error
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.receiveResponse(IMAPConnection.java:412)
at
org.apache.geronimo.mail.store.imap.connection.IMAPCommand.writeTo(IMAPCommand.java:200)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendCommand(IMAPConnection.java:320)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.sendSimpleCommand(IMAPConnection.java:288)
at
org.apache.geronimo.mail.store.imap.connection.IMAPConnection.appendMessage(IMAPConnection.java:1455)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessage(IMAPFolder.java:1562)
at
org.apache.geronimo.mail.store.imap.IMAPFolder.appendMessages(IMAPFolder.java:977)
at fpopulate.copyMessages(fpopulate.java:209)
at fpopulate.copy(fpopulate.java:136)
at fpopulate.main(fpopulate.java:107)
{code}
while it works for the reference impl:
{code:java}
A6 APPEND test1 () "09-Aug-1997 02:23:05 +0200" {1418+}
Return-Path:
Received: from rita.eng.sun.com by shorter.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA10322; Fri, 8 Aug 1997 17:23:07 -0700
Received: from jumanji.eng.sun.com by rita.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA06403; Fri, 8 Aug 1997 17:23:03 -0700
Received: by jumanji.eng.sun.com (SMI-8.6/SMI-SVR4)
id RAA22671; Fri, 8 Aug 1997 17:23:05 -0700
Date: Fri, 8 Aug 1997 17:23:05 -0700
From: ptn@jumanji (Phuong T. Nguyen)
Message-Id: <199708090023.raa22...@jumanji.eng.sun.com>
To: javam...@rita.de
Subject: Code Manager notification
Precedence: bulk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Length: 682
Status: RO
X-Status:
X-Keywords:
X-UID: 19
Event:putback-to
Parent workspace: /net/icdev/export1/ic/krakatoa/ws/jdt1.1-master
(icdev:/export1/ic/krakatoa/ws/jdt1.1-master)
Child workspace: /export0/ws/jdt1.1-ptn
(jumanji:/export0/ws/jdt1.1-ptn)
User: ptn
Comment:
- Fixed bug 4064017
HJV I18N: do not use System.getProperty("jdt.locale") to get Help
locale dir
Files:
update: src/share/lib/textmessages.properties
update: src/share/lib/props/default/jdt.props
update: src/share/sunw/sunw/hotjava/sw/applets/HomePageApplet.java
update: src/share/sunw/sunw/hotjava/sw/misc/swBrowserProperties.java
update: src/share/sunw/sunw/hotjava/sw/ui/SwEditorFrame.java
A6 OK [APPENDUID 207446323 1] APPEND completed.
{code}
Targeting the same mail server. Note the difference in the literal header. Most
of the TCK tests fail with a similar exception.
> Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
> -
>
> Key: GERONIMO-6835
> URL: https://issues.apache.org/jira/browse/GERONIMO-6835
> Project: Geron
[jira] [Commented] (GERONIMO-6835) Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
[
https://issues.apache.org/jira/browse/GERONIMO-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541482#comment-17541482
]
Richard Zowalla commented on GERONIMO-6835:
---
Note, that we are already passing the
[com.sun.ts.tests.javamail.ee|http://com.sun.ts.tests.javamail.ee/] in TomEE
with the current snapshot impl. This issue relates to the standalone mail tck.
> Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
> -
>
> Key: GERONIMO-6835
> URL: https://issues.apache.org/jira/browse/GERONIMO-6835
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: mail
> Reporter: Richard Zowalla
>Priority: Major
>
> Currently, we have some failing TCK tests for our Jakarta Mail implementation
> with https://jakarta.ee/specifications/mail/2.0/ (TCK 2.0.1).
> See attached output. Difference between 8 and 11 are the sigtests.
> Java 8
> {code:java}
> [javatest.batch] Completed running 321 tests.
> [javatest.batch] Number of Tests Passed = 166
> [javatest.batch] Number of Tests Failed = 155
> [javatest.batch] Number of Tests with Errors = 0
> [javatest.batch] Number of Tests Not Run = 0
> [javatest.batch]
> ---
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/Address/equals_Test.java#equals_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/Address/getType_Test.java#getType_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/Address/toString_Test.java#toString_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/event/ConnectionEvent/addConnectionListener_Test.java#addConnectionListener_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/event/FolderEvent/addFolderListener_Test.java#addFolderListener_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/event/FolderEvent/addMsgChangeList_Test.java#addMsgChangeList_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/event/FolderEvent/addMsgCntList_Test.java#addMsgCntList_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/event/StoreEvent/addStoreListener_Test.java#addStoreListener_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/event/TransportEvent/addTransportListener_Test.java#addTransportListener_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/exception/authenFailExp_Test.java#authenFailExp_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/exception/folderClosedException_Test.java#folderClosedException_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/exception/folderNotFoundExp_Test.java#folderNotFoundExp_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/exception/illegalWriteException_Test.java#illegalWriteException_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/exception/msgRemoveExp_Test.java#msgRemoveExp_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/exception/noSuchProvExp_Test.java#noSuchProvExp_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/add_Test.java#add_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/contains_Test.java#contains_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/fetchProfile_Test.java#fetchProfile_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/getHeaderNames_Test.java#getHeaderNames_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/getItems_Test.java#getItems_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/Flags/add_Test.java#add_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/Flags/clear_Test.java#clear_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/Flags/clone_Test.java#clone_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/Flags/contains_Test.java#contains_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/Flags/equals_Test.java#equals_Test
> [javatest.batch]
> PASSEDjavasoft/sqe/tests/jakarta/mail/Flags/Flags_Test.java#Flags_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/tests/jakarta/mail/Flags/getSystemFlags_Test.java#getSystemFlags_Test
> [javatest.batch]
> FAILEDjavasoft/sqe/te
[jira] [Created] (GERONIMO-6835) Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
Richard Zowalla created GERONIMO-6835:
-
Summary: Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
Key: GERONIMO-6835
URL: https://issues.apache.org/jira/browse/GERONIMO-6835
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: mail
Reporter: Richard Zowalla
Currently, we have some failing TCK tests for our Jakarta Mail implementation
with https://jakarta.ee/specifications/mail/2.0/ (TCK 2.0.1).
See attached output. Difference between 8 and 11 are the sigtests.
Java 8
{code:java}
[javatest.batch] Completed running 321 tests.
[javatest.batch] Number of Tests Passed = 166
[javatest.batch] Number of Tests Failed = 155
[javatest.batch] Number of Tests with Errors = 0
[javatest.batch] Number of Tests Not Run = 0
[javatest.batch] ---
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Address/equals_Test.java#equals_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Address/getType_Test.java#getType_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Address/toString_Test.java#toString_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/event/ConnectionEvent/addConnectionListener_Test.java#addConnectionListener_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/event/FolderEvent/addFolderListener_Test.java#addFolderListener_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/event/FolderEvent/addMsgChangeList_Test.java#addMsgChangeList_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/event/FolderEvent/addMsgCntList_Test.java#addMsgCntList_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/event/StoreEvent/addStoreListener_Test.java#addStoreListener_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/event/TransportEvent/addTransportListener_Test.java#addTransportListener_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/exception/authenFailExp_Test.java#authenFailExp_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/exception/folderClosedException_Test.java#folderClosedException_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/exception/folderNotFoundExp_Test.java#folderNotFoundExp_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/exception/illegalWriteException_Test.java#illegalWriteException_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/exception/msgRemoveExp_Test.java#msgRemoveExp_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/exception/noSuchProvExp_Test.java#noSuchProvExp_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/add_Test.java#add_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/contains_Test.java#contains_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/fetchProfile_Test.java#fetchProfile_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/getHeaderNames_Test.java#getHeaderNames_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/FetchProfile/getItems_Test.java#getItems_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/Flags/add_Test.java#add_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/Flags/clear_Test.java#clear_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Flags/clone_Test.java#clone_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/Flags/contains_Test.java#contains_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Flags/equals_Test.java#equals_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/Flags/Flags_Test.java#Flags_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Flags/getSystemFlags_Test.java#getSystemFlags_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Flags/getUserFlags_Test.java#getUserFlags_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/jakarta/mail/Flags/remove_Test.java#remove_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Flags/retainAll_Test.java#retainAll_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Folder/appendMessages_Test.java#appendMessages_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Folder/autoclose_Test.java#autoclose_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Folder/close_Test.java#close_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Folder/create_Test.java#create_Test
[javatest.batch]
FAILEDjavasoft/sqe/tests/jakarta/mail/Folder/delete_Test.java#delete_Test
[javatest.batch]
PASSED
[jira] [Commented] (GERONIMO-6834) geronimo-jakartamail_2.1_spec (1.0.0-M1) does not pass Jakarta Mail TCK SigTests for Java 11
[
https://issues.apache.org/jira/browse/GERONIMO-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541470#comment-17541470
]
Richard Zowalla commented on GERONIMO-6834:
---
The difference arises from the fact, that we are overriding Object#finalize()
to do some work in our spec. SigTests run with 11+ expect a @Deprecated
annotation to be present, which is only available in Java 9+. If we want to
comply with that, we will need to switch the target to 11 (or stick with 1.8
atm until EE10 is around the corner).
> geronimo-jakartamail_2.1_spec (1.0.0-M1) does not pass Jakarta Mail TCK
> SigTests for Java 11
>
>
> Key: GERONIMO-6834
> URL: https://issues.apache.org/jira/browse/GERONIMO-6834
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Richard Zowalla
>Priority: Major
>
> We have failing signature tests on *geronimo-jakartamail_2.1_spec* (1.0.0-M1)
> {code:java}
> Missing Methods
> ---
> jakarta.mail.util.SharedByteArrayInputStream: method public
> byte[] java.io.ByteArrayInputStream.readAllBytes()
> jakarta.mail.util.SharedByteArrayInputStream: method public
> byte[] java.io.InputStream.readNBytes(int) throws java.io.IOException
> jakarta.mail.util.SharedByteArrayInputStream: method public int
> java.io.ByteArrayInputStream.readNBytes(byte[],int,int)
> jakarta.mail.util.SharedByteArrayInputStream: method public
> long java.io.ByteArrayInputStream.transferTo(java.io.OutputStream) throws
> java.io.IOException
> jakarta.mail.util.SharedByteArrayInputStream: method public
> static java.io.InputStream java.io.InputStream.nullInputStream()
> jakarta.mail.util.SharedFileInputStream:method public byte[]
> java.io.InputStream.readAllBytes() throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public byte[]
> java.io.InputStream.readNBytes(int) throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public int
> java.io.InputStream.readNBytes(byte[],int,int) throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public long
> java.io.InputStream.transferTo(java.io.OutputStream) throws
> java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public static
> java.io.InputStream java.io.InputStream.nullInputStream()
> Missed Annotations
> --
> jakarta.mail.Address: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Authenticator: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.BodyPart: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.FetchProfile: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.FetchProfile$Item: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Flags: finalize():anno 0 java.lang.Deprecated(boolean
> forRemoval=false, java.lang.String since="9")
> jakarta.mail.Flags$Flag:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Header:finalize():anno 0 java.lang.Deprecated(boolean
> forRemoval=false, java.lang.String since="9")
> jakarta.mail.Message: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Message$RecipientType: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.MessageContext:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.MessagingException:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Multipart: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.PasswordAuthentication:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Provider: finalize():anno 0
>
[jira] [Updated] (GERONIMO-6834) geronimo-jakartamail_2.1_spec (1.0.0-M1) does not pass Jakarta Mail TCK SigTests for Java 11
[
https://issues.apache.org/jira/browse/GERONIMO-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla updated GERONIMO-6834:
--
Summary: geronimo-jakartamail_2.1_spec (1.0.0-M1) does not pass Jakarta
Mail TCK SigTests for Java 11 (was: geronimo-jakartamail_2.1_spec does not
pass Jakarta Mail TCK SigTests for Java 11)
> geronimo-jakartamail_2.1_spec (1.0.0-M1) does not pass Jakarta Mail TCK
> SigTests for Java 11
>
>
> Key: GERONIMO-6834
> URL: https://issues.apache.org/jira/browse/GERONIMO-6834
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Richard Zowalla
>Priority: Major
>
> We have failing signature tests on *geronimo-jakartamail_2.1_spec* (1.0.0-M1)
> {code:java}
> Missing Methods
> ---
> jakarta.mail.util.SharedByteArrayInputStream: method public
> byte[] java.io.ByteArrayInputStream.readAllBytes()
> jakarta.mail.util.SharedByteArrayInputStream: method public
> byte[] java.io.InputStream.readNBytes(int) throws java.io.IOException
> jakarta.mail.util.SharedByteArrayInputStream: method public int
> java.io.ByteArrayInputStream.readNBytes(byte[],int,int)
> jakarta.mail.util.SharedByteArrayInputStream: method public
> long java.io.ByteArrayInputStream.transferTo(java.io.OutputStream) throws
> java.io.IOException
> jakarta.mail.util.SharedByteArrayInputStream: method public
> static java.io.InputStream java.io.InputStream.nullInputStream()
> jakarta.mail.util.SharedFileInputStream:method public byte[]
> java.io.InputStream.readAllBytes() throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public byte[]
> java.io.InputStream.readNBytes(int) throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public int
> java.io.InputStream.readNBytes(byte[],int,int) throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public long
> java.io.InputStream.transferTo(java.io.OutputStream) throws
> java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public static
> java.io.InputStream java.io.InputStream.nullInputStream()
> Missed Annotations
> --
> jakarta.mail.Address: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Authenticator: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.BodyPart: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.FetchProfile: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.FetchProfile$Item: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Flags: finalize():anno 0 java.lang.Deprecated(boolean
> forRemoval=false, java.lang.String since="9")
> jakarta.mail.Flags$Flag:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Header:finalize():anno 0 java.lang.Deprecated(boolean
> forRemoval=false, java.lang.String since="9")
> jakarta.mail.Message: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Message$RecipientType: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.MessageContext:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.MessagingException:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Multipart: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.PasswordAuthentication:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Provider: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Provider$Type: finalize():anno 0
> java.lang.Deprecated(
[jira] [Updated] (GERONIMO-6834) geronimo-jakartamail_2.1_spec does not pass Jakarta Mail TCK SigTests for Java 11
[
https://issues.apache.org/jira/browse/GERONIMO-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla updated GERONIMO-6834:
--
Description:
We have failing signature tests on *geronimo-jakartamail_2.1_spec* (1.0.0-M1)
{code:java}
Missing Methods
---
jakarta.mail.util.SharedByteArrayInputStream: method public
byte[] java.io.ByteArrayInputStream.readAllBytes()
jakarta.mail.util.SharedByteArrayInputStream: method public
byte[] java.io.InputStream.readNBytes(int) throws java.io.IOException
jakarta.mail.util.SharedByteArrayInputStream: method public int
java.io.ByteArrayInputStream.readNBytes(byte[],int,int)
jakarta.mail.util.SharedByteArrayInputStream: method public long
java.io.ByteArrayInputStream.transferTo(java.io.OutputStream) throws
java.io.IOException
jakarta.mail.util.SharedByteArrayInputStream: method public
static java.io.InputStream java.io.InputStream.nullInputStream()
jakarta.mail.util.SharedFileInputStream:method public byte[]
java.io.InputStream.readAllBytes() throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public byte[]
java.io.InputStream.readNBytes(int) throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public int
java.io.InputStream.readNBytes(byte[],int,int) throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public long
java.io.InputStream.transferTo(java.io.OutputStream) throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public static
java.io.InputStream java.io.InputStream.nullInputStream()
Missed Annotations
--
jakarta.mail.Address: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Authenticator: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.BodyPart: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.FetchProfile: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.FetchProfile$Item: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Flags: finalize():anno 0 java.lang.Deprecated(boolean
forRemoval=false, java.lang.String since="9")
jakarta.mail.Flags$Flag:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Header:finalize():anno 0 java.lang.Deprecated(boolean
forRemoval=false, java.lang.String since="9")
jakarta.mail.Message: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Message$RecipientType: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.MessageContext:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.MessagingException:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Multipart: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.PasswordAuthentication:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Provider: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Provider$Type: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Quota: finalize():anno 0 java.lang.Deprecated(boolean
forRemoval=false, java.lang.String since="9")
jakarta.mail.Quota$Resource:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Session: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.URLName: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.event.ConnectionAdapter: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.event.FolderAdapter: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.event.MailEvent: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="
[jira] [Commented] (GERONIMO-6834) geronimo-jakartamail_2.1_spec does not pass Jakarta Mail TCK SigTests for Java 11
[
https://issues.apache.org/jira/browse/GERONIMO-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541465#comment-17541465
]
Richard Zowalla commented on GERONIMO-6834:
---
Signature tests work fine for Java 8
{code:java}
[javatest.batch] PASSEDcom/sun/tdk/signaturetest/SignatureTest.java
{code}
> geronimo-jakartamail_2.1_spec does not pass Jakarta Mail TCK SigTests for
> Java 11
> -
>
> Key: GERONIMO-6834
> URL: https://issues.apache.org/jira/browse/GERONIMO-6834
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Richard Zowalla
>Priority: Major
>
> We have failing signature tests on *geronimo-jakartamail_2.1_spec*
> {code:java}
> Missing Methods
> ---
> jakarta.mail.util.SharedByteArrayInputStream: method public
> byte[] java.io.ByteArrayInputStream.readAllBytes()
> jakarta.mail.util.SharedByteArrayInputStream: method public
> byte[] java.io.InputStream.readNBytes(int) throws java.io.IOException
> jakarta.mail.util.SharedByteArrayInputStream: method public int
> java.io.ByteArrayInputStream.readNBytes(byte[],int,int)
> jakarta.mail.util.SharedByteArrayInputStream: method public
> long java.io.ByteArrayInputStream.transferTo(java.io.OutputStream) throws
> java.io.IOException
> jakarta.mail.util.SharedByteArrayInputStream: method public
> static java.io.InputStream java.io.InputStream.nullInputStream()
> jakarta.mail.util.SharedFileInputStream:method public byte[]
> java.io.InputStream.readAllBytes() throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public byte[]
> java.io.InputStream.readNBytes(int) throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public int
> java.io.InputStream.readNBytes(byte[],int,int) throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public long
> java.io.InputStream.transferTo(java.io.OutputStream) throws
> java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public static
> java.io.InputStream java.io.InputStream.nullInputStream()
> Missed Annotations
> --
> jakarta.mail.Address: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Authenticator: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.BodyPart: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.FetchProfile: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.FetchProfile$Item: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Flags: finalize():anno 0 java.lang.Deprecated(boolean
> forRemoval=false, java.lang.String since="9")
> jakarta.mail.Flags$Flag:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Header:finalize():anno 0 java.lang.Deprecated(boolean
> forRemoval=false, java.lang.String since="9")
> jakarta.mail.Message: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Message$RecipientType: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.MessageContext:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.MessagingException:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Multipart: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.PasswordAuthentication:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Provider: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Provider$Type: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jaka
[jira] [Updated] (GERONIMO-6834) geronimo-jakartamail_2.1_spec does not pass Jakarta Mail TCK SigTests for Java 11
[
https://issues.apache.org/jira/browse/GERONIMO-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla updated GERONIMO-6834:
--
Summary: geronimo-jakartamail_2.1_spec does not pass Jakarta Mail TCK
SigTests for Java 11 (was: geronimo-jakartamail_2.1_spec does not pass Jakarta
Mail TCK SigTests)
> geronimo-jakartamail_2.1_spec does not pass Jakarta Mail TCK SigTests for
> Java 11
> -
>
> Key: GERONIMO-6834
> URL: https://issues.apache.org/jira/browse/GERONIMO-6834
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Richard Zowalla
>Priority: Major
>
> We have failing signature tests on *geronimo-jakartamail_2.1_spec*
> {code:java}
> Missing Methods
> ---
> jakarta.mail.util.SharedByteArrayInputStream: method public
> byte[] java.io.ByteArrayInputStream.readAllBytes()
> jakarta.mail.util.SharedByteArrayInputStream: method public
> byte[] java.io.InputStream.readNBytes(int) throws java.io.IOException
> jakarta.mail.util.SharedByteArrayInputStream: method public int
> java.io.ByteArrayInputStream.readNBytes(byte[],int,int)
> jakarta.mail.util.SharedByteArrayInputStream: method public
> long java.io.ByteArrayInputStream.transferTo(java.io.OutputStream) throws
> java.io.IOException
> jakarta.mail.util.SharedByteArrayInputStream: method public
> static java.io.InputStream java.io.InputStream.nullInputStream()
> jakarta.mail.util.SharedFileInputStream:method public byte[]
> java.io.InputStream.readAllBytes() throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public byte[]
> java.io.InputStream.readNBytes(int) throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public int
> java.io.InputStream.readNBytes(byte[],int,int) throws java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public long
> java.io.InputStream.transferTo(java.io.OutputStream) throws
> java.io.IOException
> jakarta.mail.util.SharedFileInputStream:method public static
> java.io.InputStream java.io.InputStream.nullInputStream()
> Missed Annotations
> --
> jakarta.mail.Address: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Authenticator: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.BodyPart: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.FetchProfile: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.FetchProfile$Item: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Flags: finalize():anno 0 java.lang.Deprecated(boolean
> forRemoval=false, java.lang.String since="9")
> jakarta.mail.Flags$Flag:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Header:finalize():anno 0 java.lang.Deprecated(boolean
> forRemoval=false, java.lang.String since="9")
> jakarta.mail.Message: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Message$RecipientType: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.MessageContext:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.MessagingException:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Multipart: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.PasswordAuthentication:finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Provider: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jakarta.mail.Provider$Type: finalize():anno 0
> java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
> jaka
[jira] [Updated] (GERONIMO-6834) geronimo-jakartamail_2.1_spec does not pass Jakarta Mail TCK SigTests
[
https://issues.apache.org/jira/browse/GERONIMO-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla updated GERONIMO-6834:
--
Description:
We have failing signature tests on *geronimo-jakartamail_2.1_spec*
{code:java}
Missing Methods
---
jakarta.mail.util.SharedByteArrayInputStream: method public
byte[] java.io.ByteArrayInputStream.readAllBytes()
jakarta.mail.util.SharedByteArrayInputStream: method public
byte[] java.io.InputStream.readNBytes(int) throws java.io.IOException
jakarta.mail.util.SharedByteArrayInputStream: method public int
java.io.ByteArrayInputStream.readNBytes(byte[],int,int)
jakarta.mail.util.SharedByteArrayInputStream: method public long
java.io.ByteArrayInputStream.transferTo(java.io.OutputStream) throws
java.io.IOException
jakarta.mail.util.SharedByteArrayInputStream: method public
static java.io.InputStream java.io.InputStream.nullInputStream()
jakarta.mail.util.SharedFileInputStream:method public byte[]
java.io.InputStream.readAllBytes() throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public byte[]
java.io.InputStream.readNBytes(int) throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public int
java.io.InputStream.readNBytes(byte[],int,int) throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public long
java.io.InputStream.transferTo(java.io.OutputStream) throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public static
java.io.InputStream java.io.InputStream.nullInputStream()
Missed Annotations
--
jakarta.mail.Address: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Authenticator: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.BodyPart: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.FetchProfile: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.FetchProfile$Item: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Flags: finalize():anno 0 java.lang.Deprecated(boolean
forRemoval=false, java.lang.String since="9")
jakarta.mail.Flags$Flag:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Header:finalize():anno 0 java.lang.Deprecated(boolean
forRemoval=false, java.lang.String since="9")
jakarta.mail.Message: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Message$RecipientType: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.MessageContext:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.MessagingException:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Multipart: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.PasswordAuthentication:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Provider: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Provider$Type: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Quota: finalize():anno 0 java.lang.Deprecated(boolean
forRemoval=false, java.lang.String since="9")
jakarta.mail.Quota$Resource:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Session: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.URLName: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.event.ConnectionAdapter: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.event.FolderAdapter: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.event.MailEvent: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
ja
[jira] [Created] (GERONIMO-6834) geronimo-jakartamail_2.1_spec does not pass SigTests
Richard Zowalla created GERONIMO-6834:
-
Summary: geronimo-jakartamail_2.1_spec does not pass SigTests
Key: GERONIMO-6834
URL: https://issues.apache.org/jira/browse/GERONIMO-6834
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: specs
Reporter: Richard Zowalla
We have failing signature tests on *geronimo-jakartamail_2.1_spec *
{code:java}
Missing Methods
---
jakarta.mail.util.SharedByteArrayInputStream: method public
byte[] java.io.ByteArrayInputStream.readAllBytes()
jakarta.mail.util.SharedByteArrayInputStream: method public
byte[] java.io.InputStream.readNBytes(int) throws java.io.IOException
jakarta.mail.util.SharedByteArrayInputStream: method public int
java.io.ByteArrayInputStream.readNBytes(byte[],int,int)
jakarta.mail.util.SharedByteArrayInputStream: method public long
java.io.ByteArrayInputStream.transferTo(java.io.OutputStream) throws
java.io.IOException
jakarta.mail.util.SharedByteArrayInputStream: method public
static java.io.InputStream java.io.InputStream.nullInputStream()
jakarta.mail.util.SharedFileInputStream:method public byte[]
java.io.InputStream.readAllBytes() throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public byte[]
java.io.InputStream.readNBytes(int) throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public int
java.io.InputStream.readNBytes(byte[],int,int) throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public long
java.io.InputStream.transferTo(java.io.OutputStream) throws java.io.IOException
jakarta.mail.util.SharedFileInputStream:method public static
java.io.InputStream java.io.InputStream.nullInputStream()
Missed Annotations
--
jakarta.mail.Address: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Authenticator: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.BodyPart: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.FetchProfile: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.FetchProfile$Item: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Flags: finalize():anno 0 java.lang.Deprecated(boolean
forRemoval=false, java.lang.String since="9")
jakarta.mail.Flags$Flag:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Header:finalize():anno 0 java.lang.Deprecated(boolean
forRemoval=false, java.lang.String since="9")
jakarta.mail.Message: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Message$RecipientType: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.MessageContext:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.MessagingException:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Multipart: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.PasswordAuthentication:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Provider: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Provider$Type: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Quota: finalize():anno 0 java.lang.Deprecated(boolean
forRemoval=false, java.lang.String since="9")
jakarta.mail.Quota$Resource:finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.Session: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.URLName: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.event.ConnectionAdapter: finalize():anno 0
java.lang.Deprecated(boolean forRemoval=false, java.lang.String since="9")
jakarta.mail.event.FolderAdapter: finalize():anno
[jira] [Comment Edited] (GERONIMO-6832) Fix TCK + Signature Tests for geronimo-activation_2.0_spec
[
https://issues.apache.org/jira/browse/GERONIMO-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541138#comment-17541138
]
Richard Zowalla edited comment on GERONIMO-6832 at 5/23/22 7:48 PM:
{code:java}
[javatest.batch] Number of tests completed: 90 (90 pass, 0 fail, 0 errors)
[javatest.batch] ***
[javatest.batch] Completed running 90 tests.
[javatest.batch] Number of Tests Passed = 90
[javatest.batch] Number of Tests Failed = 0
[javatest.batch] Number of Tests with Errors = 0
[javatest.batch] Number of Tests Not Run = 0
[javatest.batch] ---
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/ActivationDataFlavor_Test.java#ActivationDataFlavor_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/equals_Test.java#equals_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/getHumanPresentableName_Test.java#getHumanPresentableName_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/getMimeType_Test.java#getMimeType_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/getRepresentationClass_Test.java#getRepresentationClass_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/isMimeTypeEqual_Test.java#isMimeTypeEqual_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/normalizeMimeType_Test.java#normalizeMimeType_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/normalizeMimeTypeParameter_Test.java#normalizeMimeTypeParameter_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/setHumanPresentableName_Test.java#setHumanPresentableName_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandInfo/CommandInfo_Test.java#CommandInfo_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandInfo/getCommandClass_Test.java#getCommandClass_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandInfo/getCommandName_Test.java#getCommandName_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandInfo/getCommandObject_Test.java#getCommandObject_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/getAllCommands_Test.java#getAllCommands_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/getCommand_Test.java#getCommand_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/getDefaultCommandMap_Test.java#getDefaultCommandMap_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/getPreferredCommands_Test.java#getPreferredCommands_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/setDefaultCommandMap_Test.java#setDefaultCommandMap_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/DataHandler_Test.java#DataHandler_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getAllCommands_Test.java#getAllCommands_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getBean_Test.java#getBean_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getCommand_Test.java#getCommand_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getContent_Test.java#getContent_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getContentType_Test.java#getContentType_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getDataSource_Test.java#getDataSource_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getInputStream_Test.java#getInputStream_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getName_Test.java#getName_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getOutputStream_Test.java#getOutputStream_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getPreferredCommands_Test.java#getPreferredCommands_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getTransferData_Test.java#getTransferData_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getTransferDataFlavors_Test.java
[jira] [Commented] (GERONIMO-6832) Fix TCK + Signature Tests for geronimo-activation_2.0_spec
[
https://issues.apache.org/jira/browse/GERONIMO-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17541138#comment-17541138
]
Richard Zowalla commented on GERONIMO-6832:
---
{code:java}
[javatest.batch] Number of tests completed: 90 (90 pass, 0 fail, 0 errors)
[javatest.batch] ***
[javatest.batch] Completed running 90 tests.
[javatest.batch] Number of Tests Passed = 90
[javatest.batch] Number of Tests Failed = 0
[javatest.batch] Number of Tests with Errors = 0
[javatest.batch] Number of Tests Not Run = 0
[javatest.batch] ---
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/ActivationDataFlavor_Test.java#ActivationDataFlavor_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/equals_Test.java#equals_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/getHumanPresentableName_Test.java#getHumanPresentableName_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/getMimeType_Test.java#getMimeType_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/getRepresentationClass_Test.java#getRepresentationClass_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/isMimeTypeEqual_Test.java#isMimeTypeEqual_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/normalizeMimeType_Test.java#normalizeMimeType_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/normalizeMimeTypeParameter_Test.java#normalizeMimeTypeParameter_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/ActivationDataFlavor/setHumanPresentableName_Test.java#setHumanPresentableName_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandInfo/CommandInfo_Test.java#CommandInfo_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandInfo/getCommandClass_Test.java#getCommandClass_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandInfo/getCommandName_Test.java#getCommandName_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandInfo/getCommandObject_Test.java#getCommandObject_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/getAllCommands_Test.java#getAllCommands_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/getCommand_Test.java#getCommand_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/getDefaultCommandMap_Test.java#getDefaultCommandMap_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/getPreferredCommands_Test.java#getPreferredCommands_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/CommandMap/setDefaultCommandMap_Test.java#setDefaultCommandMap_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/DataHandler_Test.java#DataHandler_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getAllCommands_Test.java#getAllCommands_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getBean_Test.java#getBean_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getCommand_Test.java#getCommand_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getContent_Test.java#getContent_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getContentType_Test.java#getContentType_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getDataSource_Test.java#getDataSource_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getInputStream_Test.java#getInputStream_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getName_Test.java#getName_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getOutputStream_Test.java#getOutputStream_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getPreferredCommands_Test.java#getPreferredCommands_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getTransferData_Test.java#getTransferData_Test
[javatest.batch]
PASSEDjavasoft/sqe/tests/api/jakarta/activation/DataHandler/getTransferDataFlavors_Test.java#getTransferDataFlavors_Test
[javatest.batch]
PASSED
[jira] [Updated] (GERONIMO-6832) Fix TCK + Signature Tests for geronimo-activation_2.0_spec
[ https://issues.apache.org/jira/browse/GERONIMO-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6832: -- Attachment: GERONIMO-6832.diff > Fix TCK + Signature Tests for geronimo-activation_2.0_spec > -- > > Key: GERONIMO-6832 > URL: https://issues.apache.org/jira/browse/GERONIMO-6832 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6832.diff > > > Did run the sigtests + TCK and found some issues. > Sigtests currently fail due to some issues regarding the removal of the > depenency towards java.desktop + TCK also have has issues. > Did test with the milestone version. I will try to fix them. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GERONIMO-6832) Fix TCK + Signature Tests for geronimo-activation_2.0_spec
Richard Zowalla created GERONIMO-6832: - Summary: Fix TCK + Signature Tests for geronimo-activation_2.0_spec Key: GERONIMO-6832 URL: https://issues.apache.org/jira/browse/GERONIMO-6832 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Reporter: Richard Zowalla Did run the sigtests + TCK and found some issues. Sigtests currently fail due to some issues regarding the removal of the depenency towards java.desktop + TCK also have has issues. Did test with the milestone version. I will try to fix them. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GERONIMO-6829) Create geronimo-jakartamail_2.1_spec & geronimo-activation_2.0_spec
[ https://issues.apache.org/jira/browse/GERONIMO-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528874#comment-17528874 ] Richard Zowalla commented on GERONIMO-6829: --- https://github.com/apache/geronimo-specs/pull/20 > Create geronimo-jakartamail_2.1_spec & geronimo-activation_2.0_spec > --- > > Key: GERONIMO-6829 > URL: https://issues.apache.org/jira/browse/GERONIMO-6829 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > > Task for adding jakartmail 2.1 spec > Impl / API are a bit tied together. We can start with 1.6 & package renamings > and figure out potential gaps later. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GERONIMO-6829) Create geronimo-jakartamail_2.1_spec & geronimo-activation_2.0_spec
[ https://issues.apache.org/jira/browse/GERONIMO-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6829: -- Summary: Create geronimo-jakartamail_2.1_spec & geronimo-activation_2.0_spec (was: Create geronimo-jakartamail_2.1_spec) > Create geronimo-jakartamail_2.1_spec & geronimo-activation_2.0_spec > --- > > Key: GERONIMO-6829 > URL: https://issues.apache.org/jira/browse/GERONIMO-6829 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > > Task for adding jakartmail 2.1 spec > Impl / API are a bit tied together. We can start with 1.6 & package renamings > and figure out potential gaps later. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (GERONIMO-6829) Create geronimo-jakartamail_2.1_spec
Richard Zowalla created GERONIMO-6829: - Summary: Create geronimo-jakartamail_2.1_spec Key: GERONIMO-6829 URL: https://issues.apache.org/jira/browse/GERONIMO-6829 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: mail Reporter: Richard Zowalla Task for adding jakartmail 2.1 spec Impl / API are a bit tied together. We can start with 1.6 & package renamings and figure out potential gaps later. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (GERONIMO-6800) MimeBodyPart.setText ignores subtype
[
https://issues.apache.org/jira/browse/GERONIMO-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17423891#comment-17423891
]
Richard Zowalla commented on GERONIMO-6800:
---
Hi [~Argannor] - any news? Would love to see a new javamail release soon :)
> MimeBodyPart.setText ignores subtype
>
>
> Key: GERONIMO-6800
> URL: https://issues.apache.org/jira/browse/GERONIMO-6800
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Argannor
>Assignee: Francois Papon
>Priority: Minor
> Fix For: Javamail_1.6_1.0.1
>
> Attachments: setText-subtype-ignored.patch
>
>
> Hi there,
> the following method from MimeBodyPart in geonimo-javamail_1.6_spec ignores
> the parameter subtype, and always sets the mime type to text/plain.
> {code:java}
> public void setText(final String text, String charset, final String subtype)
> {code}
> I've written a small patch, including a test case. Please let me know if I
> need to sign any legal documents to donate this code.
> Kind regards
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Pending patches
Thx for the ticket id !
Am Dienstag, den 08.06.2021, 14:07 +0200 schrieb Francois Papon:
> Hi,
>
> Migration is still pending, waiting for infra:
>
> https://issues.apache.org/jira/browse/INFRA-21908
> <https://issues.apache.org/jira/browse/INFRA-21908>
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 08/06/2021 à 13:56, Richard Zowalla a écrit :
> > Hi François,
> >
> > any updates from INFRA on this? Couldnt find the ticket id anymore,
> > sry.
> >
> > Gruss
> > Richard
> >
> > Am Mittwoch, den 19.05.2021, 09:38 +0200 schrieb Francois Papon:
> > > Hi,
> > >
> > > Yes, we plan to do this just after the migration to git ;)
> > >
> > > regards,
> > >
> > > François
> > > fpa...@apache.org
> > >
> > > Le 19/05/2021 à 09:09, Zowalla, Richard a écrit :
> > > > Hi,
> > > >
> > > > thanks for your response! I think, that [1] might also affect
> > > > the
> > > > hard-
> > > > coded TLS1.0 in GERONIMO-6792 [2], so the pending patch would
> > > > be
> > > > very
> > > > appreciated.
> > > >
> > > > Maybe after the migration to git? ;)
> > > >
> > > > Gruss
> > > > Richard
> > > >
> > > > [1] https://bugs.openjdk.java.net/browse/JDK-8202343
> > > > [2] https://issues.apache.org/jira/browse/GERONIMO-6792
> > > >
> > > > Am Samstag, den 01.05.2021, 08:20 +0200 schrieb
> > > > fpa...@apache.org:
> > > > > Hi,
> > > > >
> > > > > I think I can take a look to the Jira and merge the PRs.
> > > > >
> > > > > regards,
> > > > >
> > > > > François
> > > > > fpa...@apache.org
> > > > >
> > > > > Le 28/04/2021 à 11:09, Zowalla, Richard a écrit :
> > > > > > Just to follow up on this thread:
> > > > > >
> > > > > > Do we have any plans for moving forward with the mail-
> > > > > > related
> > > > > > patches?
> > > > > > The hard-coded TLS config in mail is a bit "pain" ;)
> > > > > >
> > > > > > Gruss
> > > > > > Richard
> > > > > >
> > > > > > Am Dienstag, den 23.03.2021, 08:50 +0100 schrieb Romain
> > > > > > Manni-
> > > > > > Bucau:
> > > > > > > Well it can use a singleton but from a factory method. So
> > > > > > > immediate
> > > > > > > solution is to add a public static X getInstance();.
> > > > > > > But as mentionned it means, to keep the pluggability we
> > > > > > > should
> > > > > > > target
> > > > > > > with such a spi, you will enforce all other impl to use
> > > > > > > such
> > > > > > > a
> > > > > > > pattern (you cant' just switch with -D easily since
> > > > > > > adding is
> > > > > > > easy
> > > > > > > but dropping system props is almost impossible).
> > > > > > > A noarg public constructor is trivial and more natural
> > > > > > > with
> > > > > > > resources
> > > > > > > IMHO - but once again tomee can does all the work to
> > > > > > > makes it
> > > > > > > equivalent, just requires to duplicate/wrap the impls of
> > > > > > > the
> > > > > > > SPI
> > > > > > > in
> > > > > > > tomee codebase which sounds weird to me ("we have an impl
> > > > > > > but
> > > > > > > you
> > > > > > > need to use another one").
> > > > > > >
> > > > > > > On a more personal note I think this pattern is no more
> > > > > > > relevant
> > > > > > > and
> > > > > > > has more pitfalls since you enforce a static instance as
> > > > > > > soon
> > > > > > > as
> > > > > > > the
> > > > > > > class is loaded whereas it is not needed depending the
> > > > > > > lifecycle
> > > > > > > of
> >
Re: Pending patches
Hi François,
any updates from INFRA on this? Couldnt find the ticket id anymore,
sry.
Gruss
Richard
Am Mittwoch, den 19.05.2021, 09:38 +0200 schrieb Francois Papon:
> Hi,
>
> Yes, we plan to do this just after the migration to git ;)
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 19/05/2021 à 09:09, Zowalla, Richard a écrit :
> > Hi,
> >
> > thanks for your response! I think, that [1] might also affect the
> > hard-
> > coded TLS1.0 in GERONIMO-6792 [2], so the pending patch would be
> > very
> > appreciated.
> >
> > Maybe after the migration to git? ;)
> >
> > Gruss
> > Richard
> >
> > [1] https://bugs.openjdk.java.net/browse/JDK-8202343
> > [2] https://issues.apache.org/jira/browse/GERONIMO-6792
> >
> > Am Samstag, den 01.05.2021, 08:20 +0200 schrieb fpa...@apache.org:
> > > Hi,
> > >
> > > I think I can take a look to the Jira and merge the PRs.
> > >
> > > regards,
> > >
> > > François
> > > fpa...@apache.org
> > >
> > > Le 28/04/2021 à 11:09, Zowalla, Richard a écrit :
> > > > Just to follow up on this thread:
> > > >
> > > > Do we have any plans for moving forward with the mail-related
> > > > patches?
> > > > The hard-coded TLS config in mail is a bit "pain" ;)
> > > >
> > > > Gruss
> > > > Richard
> > > >
> > > > Am Dienstag, den 23.03.2021, 08:50 +0100 schrieb Romain Manni-
> > > > Bucau:
> > > > > Well it can use a singleton but from a factory method. So
> > > > > immediate
> > > > > solution is to add a public static X getInstance();.
> > > > > But as mentionned it means, to keep the pluggability we
> > > > > should
> > > > > target
> > > > > with such a spi, you will enforce all other impl to use such
> > > > > a
> > > > > pattern (you cant' just switch with -D easily since adding is
> > > > > easy
> > > > > but dropping system props is almost impossible).
> > > > > A noarg public constructor is trivial and more natural with
> > > > > resources
> > > > > IMHO - but once again tomee can does all the work to makes it
> > > > > equivalent, just requires to duplicate/wrap the impls of the
> > > > > SPI
> > > > > in
> > > > > tomee codebase which sounds weird to me ("we have an impl but
> > > > > you
> > > > > need to use another one").
> > > > >
> > > > > On a more personal note I think this pattern is no more
> > > > > relevant
> > > > > and
> > > > > has more pitfalls since you enforce a static instance as soon
> > > > > as
> > > > > the
> > > > > class is loaded whereas it is not needed depending the
> > > > > lifecycle
> > > > > of
> > > > > your main - it is not much but still, I see it as a leak in
> > > > > terms
> > > > > of
> > > > > design (indeed this one is not important and not a blocker
> > > > > but
> > > > > all
> > > > > implies to move to the noarg public constructor on my side).
> > > > > Maybe a habit and personal choice so would be great to have
> > > > > another
> > > > > opinion to move forward :).
> > > > >
> > > > > Le mar. 23 mars 2021 à 08:38, Zowalla, Richard <
> > > > > richard.zowa...@hs-heilbronn.de> a écrit :
> > > > > > Hi,
> > > > > >
> > > > > > I think, it is about the configuration flexibility in
> > > > > > tomee's
> > > > > > definitions, which wouldn't allow the use of a
> > > > > > singleton
> > > > > > instance. Hence, the consuming project would need to
> > > > > > implement
> > > > > > the
> > > > > > interface to make it possible. But I am not that deep as
> > > > > > Romain
> > > > > > in
> > > > > > the
> > > > > > TomEE codebase, so it is still a guess from my side.
> > > > > >
> > > > > > Gruss
> > > > > > Richard
> > > > > >
> > > > > > Am Montag, den 22.03.2021, 23:14 +0100 schrieb Florent
> > > > > > Guillaume:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I can drop the private constructor if you want.
> > > > > > > I'm surprised it's needed though, as the default instance
> > > > > > > is
> > > > > > already
> > > > > > > used by the code if no value is provided for the
> > > > > > > timeProvider
> > > > > > > parameter of TransactionImpl.
> > > > > > >
> > > > > > > Florent
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Mar 22, 2021 at 5:49 PM Romain Manni-Bucau <
> > > > > > > rmannibu...@gmail.com> wrote:
> > > > > > > > Hi Richard,
> > > > > > > >
> > > > > > > > I still think SystemCurrentTime should have a public
> > > > > > > > noarg
> > > > > > > > constructor (or just drop the private one) since it
> > > > > > > > will
> > > > > > > > enable
> > > > > > > > tomee to fully configure dynamically the tx mgr with
> > > > > > > > this
> > > > > > > > new
> > > > > > > > feature but otherwise +1 to apply them all.
> > > > > > > >
> > > > > > > > Romain Manni-Bucau
> > > > > > > > @rmannibucau | Blog | Old Blog | Github | LinkedIn |
> > > > > > > > Book
> > > > > > > >
> > > > > > > >
> > > > > > > > Le lun. 22 mars 2021 à 17:03, Zowalla, Richard <
> > > > > > > > richard.zowa...@hs-heilbronn.de> a écrit :
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > wanted to raise attention on
[jira] [Commented] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354881#comment-17354881 ] Richard Zowalla commented on GERONIMO-6793: --- [~romain.manni-bucau] I get the point :) I have added a *diff* based on the current trunk to allow custom ciphers + documentation as discussed (defaults to supported cipher list if no property is set). If the repository is migrated to GitHub, I can also create a related pull request (instead of the SVN diff). There is some overlap towards GERONIMO-6792, so we can reduce some code duplication in parsing the whitespace sepearated list of ciphers / protocols once GERONIMO-6792 is integrated. > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6793.diff > > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6793: -- Attachment: (was: GERONIMO-6793.diff) > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6793.diff > > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6793: -- Attachment: GERONIMO-6793.diff > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6793.diff > > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6793: -- Flags: Patch Patch Info: Patch Available > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6793.diff > > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6793: -- Attachment: GERONIMO-6793.diff > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6793.diff > > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354824#comment-17354824 ] Richard Zowalla commented on GERONIMO-6793: --- Provider scanning is maybe an enhancement / follow-up. We would need to gather a list of prominent mail providers first (Gmail, Yahoo, Outlook, AOL, Zoho, Mail.com, ProtonMail, ...) - there might be others around. Scanning the ciphers itself can be done in bulk via testssl.sh (for example) , which can store JSON and subsequently parsed to get an aggegated cipher list. Possible problem would be, that the ciphers are subject to change - so we would need to monitor them reliably (if they are hard-coded) > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354492#comment-17354492 ] Richard Zowalla edited comment on GERONIMO-6793 at 5/31/21, 4:54 PM: - What about: # Use the JVM _enabled_ cyphers by default to be consistent with GERONIMO-6792 # Allow to override the default via _mail.protocol.xx.mail.ciphersuites_ # Provide appropriate logging (show which ciphers are used) # Update the README.txt to document the new behaviour and give some hints on how to determine the list of supported ciphers of a mail server [~romain.manni-bucau] what do you mean by aliases exactly? was (Author: rzo1): What about: # Use the JVM _enabled_ cyphers by default to be consistent with GERONIMO-6792 # Allow to override the default via _mail.protocol.smtp.mail.ciphersuites_ # Provide appropriate logging (show which ciphers are used) # Update the README.txt to document the new behaviour and give some hints on how to determine the list of supported ciphers of a mail server [~romain.manni-bucau] what do you mean by aliases exactly? > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354555#comment-17354555 ] Richard Zowalla edited comment on GERONIMO-6793 at 5/31/21, 4:54 PM: - I agree, that tuning ciphers is a very special case and requires a lot of (background) knowledge to find a concise and working solution / list of ciphers. Even, if you are managing self-hosted mail infrastructure, every small cipher change can break multiple clients (we experienced it in the past ...). So the non-breaking way would probably be # Allow to override the default via _mail.protocol.xx.mail.ciphersuites_ (and leave the current default as is) # Provide appropriate logging (show which ciphers are used) - maybe also give a hint, that all supported ciphers are used, if the property is not set # Update the README.txt to document the new behaviour and give some hints on how to determine the list of supported ciphers of a mail server Personally, I can live with both ways as long as I can specify the ciphers easily ... ;) was (Author: rzo1): I agree, that tuning ciphers is a very special case and requires a lot of (background) knowledge to find a concise and working solution / list of ciphers. Even, if you are managing self-hosted mail infrastructure, every small cipher change can break multiple clients (we experienced it in the past ...). So the non-breaking way would probably be # Allow to override the default via _mail.protocol.smtp.mail.ciphersuites_ (and leave the current default as is) # Provide appropriate logging (show which ciphers are used) - maybe also give a hint, that all supported ciphers are used, if the property is not set # Update the README.txt to document the new behaviour and give some hints on how to determine the list of supported ciphers of a mail server Personally, I can live with both ways as long as I can specify the ciphers easily ... ;) > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354555#comment-17354555 ] Richard Zowalla commented on GERONIMO-6793: --- I agree, that tuning ciphers is a very special case and requires a lot of (background) knowledge to find a concise and working solution / list of ciphers. Even, if you are managing self-hosted mail infrastructure, every small cipher change can break multiple clients (we experienced it in the past ...). So the non-breaking way would probably be # Allow to override the default via _mail.protocol.smtp.mail.ciphersuites_ (and leave the current default as is) # Provide appropriate logging (show which ciphers are used) - maybe also give a hint, that all supported ciphers are used, if the property is not set # Update the README.txt to document the new behaviour and give some hints on how to determine the list of supported ciphers of a mail server Personally, I can live with both ways as long as I can specify the ciphers easily ... ;) > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354492#comment-17354492 ] Richard Zowalla commented on GERONIMO-6793: --- What about: # Use the JVM _enabled_ cyphers by default to be consistent with GERONIMO-6792 # Allow to override the default via _mail.protocol.smtp.mail.ciphersuites_ # Provide appropriate logging (show which ciphers are used) # Update the README.txt to document the new behaviour and give some hints on how to determine the list of supported ciphers of a mail server [~romain.manni-bucau] what do you mean by aliases exactly? > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354488#comment-17354488 ] Richard Zowalla commented on GERONIMO-6792: --- I just updated the README.txt of *GERONIMO-6792-v4-no-hardcoding.diff* which I forgot to update at the time providing this patch. It now correctly states the fallback to JVM defaults. > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4-no-hardcoding.diff, > GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6792: -- Attachment: GERONIMO-6792-v4-no-hardcoding.diff > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4-no-hardcoding.diff, > GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6792: -- Attachment: (was: GERONIMO-6792-v4-no-hardcoding.diff) > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4-no-hardcoding.diff, > GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258241#comment-17258241 ] Richard Zowalla commented on GERONIMO-6792: --- Nice :) - thanks for the update. > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4-no-hardcoding.diff, > GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6792: -- Comment: was deleted (was: Hi @rmannibucau any plans to include this in an upcoming minor release of geronimo java mail? Thanks im advance :)) > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4-no-hardcoding.diff, > GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258239#comment-17258239 ] Richard Zowalla commented on GERONIMO-6792: --- Hi [~rmannibucau] any plans to include this in an upcoming minor release of geronimo java mail? Thanks in advance :) > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4-no-hardcoding.diff, > GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17258238#comment-17258238 ] Richard Zowalla commented on GERONIMO-6792: --- Hi @rmannibucau any plans to include this in an upcoming minor release of geronimo java mail? Thanks im advance :) > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4-no-hardcoding.diff, > GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
[ https://issues.apache.org/jira/browse/GERONIMO-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17243842#comment-17243842 ] Richard Zowalla commented on GERONIMO-6793: --- > If we have time we should probably review most mail provider to ensure they >all work by default and tuning is only needed for custom company mail servers >for example. Yup, I agree with that. At least, a tuning option should be possible instead of an allow-all policy. Overall, mail servers are known to be outdated or implementing TLS in a sloopy way :) For that reason: If we get the most common providers (gmail, proton, etc.) to work and allow a custom way to adjust the cyphers, I would be happy. Problem is, that cyphers do change with the time, so we would need to monitor this changes and reflect it in the code base. Maybe [~b.eckenfels] also has some thoughts on this? :) > Do not auto-enable all available Cyphers in TLS/SSL protocol handling in > MailConnection > --- > > Key: GERONIMO-6793 > URL: https://issues.apache.org/jira/browse/GERONIMO-6793 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: mail >Reporter: Richard Zowalla >Priority: Major > > Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL > protocol handling in MailConnection.java > Some cyphers are deprecated for good reasons and shouldn't be used. > This enhancement might possibily include > * Allow users to specifiy cyphers via properties (custom factory is already > possible) > * If we have no user defined cyphers available, fallback to the JVMs default > cyphers. > > This is a follow up issue raised from the discussion on the dev mailing list, > see > http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GERONIMO-6793) Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection
Richard Zowalla created GERONIMO-6793: - Summary: Do not auto-enable all available Cyphers in TLS/SSL protocol handling in MailConnection Key: GERONIMO-6793 URL: https://issues.apache.org/jira/browse/GERONIMO-6793 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: mail Reporter: Richard Zowalla Check and discuss, if it is a good idea to enable all cyphers in TLS/SSL protocol handling in MailConnection.java Some cyphers are deprecated for good reasons and shouldn't be used. This enhancement might possibily include * Allow users to specifiy cyphers via properties (custom factory is already possible) * If we have no user defined cyphers available, fallback to the JVMs default cyphers. This is a follow up issue raised from the discussion on the dev mailing list, see http://mail-archives.apache.org/mod_mbox/geronimo-dev/202012.mbox/%3C096fbb867eda8e090eddf80fbd81cf787ac87945.camel%40hs-heilbronn.de%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17243205#comment-17243205 ] Richard Zowalla commented on GERONIMO-6792: --- Based on the discussion on the mailing list and the comments by [~b.eckenfels], I have provided an alternative diff (*GERONIMO-6792-v4-no-hardcoding.diff*), which uses the enabled protocols of the SSLSockets *as is* (and logs them as debug output). Reason(s): * SSLSocket might be created by a custom factory. Consequently, we shouldn't simply override the enabled protocols by a static list. * In the most common case (no custom factory), the SSLSocket is created with JVM defaults, which are continously updated. Thx [~b.eckenfels] for the hint. > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4-no-hardcoding.diff, > GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6792: -- Attachment: GERONIMO-6792-v4-no-hardcoding.diff > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4-no-hardcoding.diff, > GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242448#comment-17242448 ] Richard Zowalla commented on GERONIMO-6792: --- Updated the patch proposal to contain the three ways of configuring custom protocols # Using mail..ssl.socketFactory.class (Reflection-based) # Using mail..ssl.socketFactory (Pre-configured instance in the Mail Session) # Using mail..ssl.protocols (list of tls protocols, whitespace separatet) > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6792: -- Attachment: (was: GERONIMO-6792-v3.diff) > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GERONIMO-6792) Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6
[ https://issues.apache.org/jira/browse/GERONIMO-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zowalla updated GERONIMO-6792: -- Attachment: GERONIMO-6792-v4.diff > Fix hard-coded TLSv1 version in MailConnection.java for Java Mail 1.6 > - > > Key: GERONIMO-6792 > URL: https://issues.apache.org/jira/browse/GERONIMO-6792 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: mail > Reporter: Richard Zowalla >Priority: Major > Attachments: GERONIMO-6792-v4.diff > > > Hi, > I encountered some issues when using Geronimo Java Mail 1.6 (1.0.0) bundled > with TomEE 8.0.5. The related thread [1] can be found on the > [us...@tomee.apache.org|mailto:us...@tomee.apache.org] Mailing-List. > In short: > * Our mail server does only support TLS 1.2 or TLS 1.3 > * Geronimo Java Mail 1.6 in version 1.0.0 has TLS 1.0 hard-coded in the > source and does not use the default protocols or the specified ones via > *mail.smtp.ssl.protocols* for a TLS connection. > I have attached a patch created via SVN DIFF. > [1] [https://www.mail-archive.com/users@tomee.apache.org/msg17544.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
