[jira] [Created] (EMAIL-111) Update the current trunk to be binary compatible with the commons-email-1.2 release

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (EMAIL-111) Update the current trunk to be binary compatible with the commons-email-1.2 release

ASF GitHub Bot (Jira)
Update the current trunk to be binary compatible with the commons-email-1.2 release
-----------------------------------------------------------------------------------

                 Key: EMAIL-111
                 URL: https://issues.apache.org/jira/browse/EMAIL-111
             Project: Commons Email
          Issue Type: Task
            Reporter: Siegfried Goeschl
            Assignee: Siegfried Goeschl
             Fix For: 1.3


The last RC was rejected because the RC is not binary compatible with commons-email-1.2

* some getter methods return "Email" instead of "void" which breaks binary compatibility
* two protected member variable (SSL & TLS related) were removed since their name was misleading

The goals of the task is to get rid of those Clirr warnings in order to avoid a new major release



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (EMAIL-111) Update the current trunk to be binary compatible with the commons-email-1.2 release

ASF GitHub Bot (Jira)

    [ https://issues.apache.org/jira/browse/EMAIL-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184132#comment-13184132 ]

Sebb commented on EMAIL-111:
----------------------------

The method MultiPartEmail#addPart(String, String) was changed to return MultiPartEmail rather than Email.

That also needs to be reverted.

[Reminder: re-open any JIRA fixes that had to be reverted; also update release notes/changes]
               

> Update the current trunk to be binary compatible with the commons-email-1.2 release
> -----------------------------------------------------------------------------------
>
>                 Key: EMAIL-111
>                 URL: https://issues.apache.org/jira/browse/EMAIL-111
>             Project: Commons Email
>          Issue Type: Task
>            Reporter: Siegfried Goeschl
>            Assignee: Siegfried Goeschl
>             Fix For: 1.3
>
>
> The last RC was rejected because the RC is not binary compatible with commons-email-1.2
> * some getter methods return "Email" instead of "void" which breaks binary compatibility
> * two protected member variable (SSL & TLS related) were removed since their name was misleading
> The goals of the task is to get rid of those Clirr warnings in order to avoid a new major release

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (EMAIL-111) Update the current trunk to be binary compatible with the commons-email-1.2 release

ASF GitHub Bot (Jira)
In reply to this post by ASF GitHub Bot (Jira)

    [ https://issues.apache.org/jira/browse/EMAIL-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184222#comment-13184222 ]

Siegfried Goeschl commented on EMAIL-111:
-----------------------------------------

You are absolutely right ... thx Sebastian
               

> Update the current trunk to be binary compatible with the commons-email-1.2 release
> -----------------------------------------------------------------------------------
>
>                 Key: EMAIL-111
>                 URL: https://issues.apache.org/jira/browse/EMAIL-111
>             Project: Commons Email
>          Issue Type: Task
>            Reporter: Siegfried Goeschl
>            Assignee: Siegfried Goeschl
>             Fix For: 1.3
>
>
> The last RC was rejected because the RC is not binary compatible with commons-email-1.2
> * some getter methods return "Email" instead of "void" which breaks binary compatibility
> * two protected member variable (SSL & TLS related) were removed since their name was misleading
> The goals of the task is to get rid of those Clirr warnings in order to avoid a new major release

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (EMAIL-111) Update the current trunk to be binary compatible with the commons-email-1.2 release

ASF GitHub Bot (Jira)
In reply to this post by ASF GitHub Bot (Jira)

     [ https://issues.apache.org/jira/browse/EMAIL-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Florian Pirchner updated EMAIL-111:
-----------------------------------

    Attachment: sslTls.diff
                returntypes.diff

Two patches provided by hackergarten vienna.

Best,
Flo and Peter
               

> Update the current trunk to be binary compatible with the commons-email-1.2 release
> -----------------------------------------------------------------------------------
>
>                 Key: EMAIL-111
>                 URL: https://issues.apache.org/jira/browse/EMAIL-111
>             Project: Commons Email
>          Issue Type: Task
>            Reporter: Siegfried Goeschl
>            Assignee: Siegfried Goeschl
>             Fix For: 1.3
>
>         Attachments: returntypes.diff, sslTls.diff
>
>
> The last RC was rejected because the RC is not binary compatible with commons-email-1.2
> * some getter methods return "Email" instead of "void" which breaks binary compatibility
> * two protected member variable (SSL & TLS related) were removed since their name was misleading
> The goals of the task is to get rid of those Clirr warnings in order to avoid a new major release

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (EMAIL-111) Update the current trunk to be binary compatible with the commons-email-1.2 release

ASF GitHub Bot (Jira)
In reply to this post by ASF GitHub Bot (Jira)

     [ https://issues.apache.org/jira/browse/EMAIL-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siegfried Goeschl resolved EMAIL-111.
-------------------------------------

    Resolution: Fixed

Applied patch to trunk
               

> Update the current trunk to be binary compatible with the commons-email-1.2 release
> -----------------------------------------------------------------------------------
>
>                 Key: EMAIL-111
>                 URL: https://issues.apache.org/jira/browse/EMAIL-111
>             Project: Commons Email
>          Issue Type: Task
>            Reporter: Siegfried Goeschl
>            Assignee: Siegfried Goeschl
>             Fix For: 1.3
>
>         Attachments: returntypes.diff, sslTls.diff
>
>
> The last RC was rejected because the RC is not binary compatible with commons-email-1.2
> * some getter methods return "Email" instead of "void" which breaks binary compatibility
> * two protected member variable (SSL & TLS related) were removed since their name was misleading
> The goals of the task is to get rid of those Clirr warnings in order to avoid a new major release

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira