Uploaded image for project: 'Archiva'
  1. Archiva
  2. MRM-615

When scanning, Archiva doesn't resolve properties/variables of POMs in managed repositories

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0
    • Fix Version/s: 1.2-M1
    • Component/s: repository scanning
    • Labels:
      None

      Description

      If you have a JAR with a POM that contains variables (like "pom.version") or properties, Archiva doesn't resolve them when scanning and analysing the repository. Some of the multiple consequences are that the "Dependencies" tab can list dependencies without "real" versions, and that the "Dependency Tree" tabs can break with an exception "Unable to generate graph for [XXX] : Unable to create ArchivaArtifact with empty version".

      A consequence of this bug can be seen by following these steps:

      This bug breaks other functionalities like the "Used by" tab.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                fabemn Fabrice Bellingard
              • Votes:
                5 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: