commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <>
Subject [jira] [Updated] (IO-333) Export packages at version 1.x in addition to 2.x
Date Thu, 07 Jun 2012 12:12:23 GMT


Felix Meschberger updated IO-333:

    Attachment: IO-333.patch

Proposed patch adding export at version 1.5 in addition to current project version.

We have to explicitly list the packages due to how the BND library (used by the bundle plugin)
creates the list of packages exported.

So, this patch lists all packages already existing in the 1.4 release and exports it at 1.5.
This accounts for new functionality built into those packages since 1.4.

The list is duplicated for the regular export at the library version. In addition there is
a pattern export to add all new packages in.

This patch assumes the 2.x export is more correct and the 1.x export version is for backwards

Anyway going forward, proper semantic versioning should probably be applied to the exported
packages and update the export version according to the changes.
> Export packages at version 1.x in addition to 2.x
> -------------------------------------------------
>                 Key: IO-333
>                 URL:
>             Project: Commons IO
>          Issue Type: Improvement
>    Affects Versions: 2.3
>            Reporter: Felix Meschberger
>         Attachments: IO-333.patch
> As discussed on the list [1], I propose to export the provided packages twice, once with
the default version being the project version and once with a
> version complying more with OSGi semantic versioning [2].
> I will attach proposed patch.
> There seems to be one single problematic change since the 1.4 release: IO-318.
> Strictly speaking this is an incompatible change because consumers would
> catch a different exception and thus would fail to handle exceptions correctly. But according
to IO-318, this is rare.
> [1]
> [2]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message