You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rick McGuire (JIRA)" <ji...@apache.org> on 2007/03/09 11:26:24 UTC
[jira] Created: (GERONIMO-2945) Reorganized the geronimo-javamail
tree so that the 1.3.1 and 1.4 providers can be release separately.
Reorganized the geronimo-javamail tree so that the 1.3.1 and 1.4 providers can be release separately.
-----------------------------------------------------------------------------------------------------
Key: GERONIMO-2945
URL: https://issues.apache.org/jira/browse/GERONIMO-2945
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: mail
Affects Versions: 1.2, 2.0
Reporter: Rick McGuire
Assigned To: Rick McGuire
Fix For: 1.2, 2.0
Now that the javamail spec jars are released on their own separate release cycles. a new release of the 1.3.1 jar does not necessarily coincide with a release of the 1.4 spec jars. However, the 1.3.1 and 1.4 mail and provider jars share a common parent pom, which makes it difficult to release the two parts separately. This should be reworked so that these are no longer so tightly coupled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2945) Reorganized the geronimo-javamail
tree so that the 1.3.1 and 1.4 providers can be release separately.
Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick McGuire closed GERONIMO-2945.
----------------------------------
> Reorganized the geronimo-javamail tree so that the 1.3.1 and 1.4 providers can be release separately.
> -----------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2945
> URL: https://issues.apache.org/jira/browse/GERONIMO-2945
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: mail
> Affects Versions: 1.2, 2.0
> Reporter: Rick McGuire
> Assigned To: Rick McGuire
> Fix For: 1.2, 2.0
>
>
> Now that the javamail spec jars are released on their own separate release cycles. a new release of the 1.3.1 jar does not necessarily coincide with a release of the 1.4 spec jars. However, the 1.3.1 and 1.4 mail and provider jars share a common parent pom, which makes it difficult to release the two parts separately. This should be reworked so that these are no longer so tightly coupled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2945) Reorganized the geronimo-javamail
tree so that the 1.3.1 and 1.4 providers can be release separately.
Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick McGuire resolved GERONIMO-2945.
------------------------------------
Resolution: Fixed
Committed revision 516366.
> Reorganized the geronimo-javamail tree so that the 1.3.1 and 1.4 providers can be release separately.
> -----------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-2945
> URL: https://issues.apache.org/jira/browse/GERONIMO-2945
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: mail
> Affects Versions: 1.2, 2.0
> Reporter: Rick McGuire
> Assigned To: Rick McGuire
> Fix For: 1.2, 2.0
>
>
> Now that the javamail spec jars are released on their own separate release cycles. a new release of the 1.3.1 jar does not necessarily coincide with a release of the 1.4 spec jars. However, the 1.3.1 and 1.4 mail and provider jars share a common parent pom, which makes it difficult to release the two parts separately. This should be reworked so that these are no longer so tightly coupled.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.