You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sis.apache.org by "Martin Desruisseaux (Jira)" <ji...@apache.org> on 2022/12/12 15:23:00 UTC

[jira] [Closed] (SIS-106) Verify the Modules constants against the OSGi symbolic names

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

Martin Desruisseaux closed SIS-106.
-----------------------------------
    Resolution: Won't Fix

OSGi support has been abandoned a few releases ago. There is a few remaining trace in {{sis-webapp}} module, maybe to be removed in a future version as well.

> Verify the Modules constants against the OSGi symbolic names
> ------------------------------------------------------------
>
>                 Key: SIS-106
>                 URL: https://issues.apache.org/jira/browse/SIS-106
>             Project: Spatial Information Systems
>          Issue Type: Test
>          Components: Utilities
>            Reporter: Martin Desruisseaux
>            Priority: Minor
>
> The {{org.apache.sis.internal.system.Modules}} class defines a set of constants for the OSGi bundle names. Those constants need to be equal to the values of the {{Bundle-SymbolicName}} entry of the {{META-INF/MANIFEST.MF}} file in each JAR files. However there is no JUnit test for ensuring that at this time.
> The difficulty is that the Maven surefire tests against the {{.class}} files, while we need to test against the {{.jar}} files. It may be possible to do that at the Maven "verify" phase, but this need more investigation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)