Uploaded image for project: 'Felix'
  1. Felix
  2. FELIX-546

Import-Package version inconsistencies.

    Details

      Description

      There is an inconsistency in how versions are handled in Import-Package statements.

      Style 1: <Import-Package>com.ea.bugtest1;version=1.0.0-SNAPSHOT</Import-Package>

      ...produces...

      Import-Package: com.ea.bugtest1;version="1.0.0.SNAPSHOT"

      Style 2: <Import-Package>com.ea.bugtest1;version="1.0.0-SNAPSHOT"</Import-Package>

      ...produces...

      Import-Package: com.ea.bugtest1;version="1.0.0.SNAPSHOT"

      Style 3: <Import-Package>com.ea.bugtest1;version="[1.0.0-SNAPSHOT,1.0.0-SNAPSHOT]"</Import-Package>

      ...produces...

      Import-Package: com.ea.bugtest1;version="[1.0.0-SNAPSHOT,1.0.0-SNAPSHOT]"

      Note that the 1.0.0-SNAPSHOT has not been converted to 1.0.0.SNAPSHOT. Also, this form breaks the OBR pieces of the plugin. The OBR repository must be set to NONE for this to work at all. I'll file a separate bug on this issue

      I realize that having 1.0.0-SNAPSHOT in the import statment isn't exactly ideal, but it is coming in through a maven property. We're trying to find a way to maintain some consistency between our declared maven dependencies and our import-package statements by sharing a single property value.

      I will attach a small demo project that will allow you to easily demonstrate the issue.

        Attachments

        1. bugtest.tar.gz
          2 kB
          Thomas Dewire

          Activity

            People

            • Assignee:
              mcculls Stuart McCulloch
              Reporter:
              tomdewire Thomas Dewire
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: