Uploaded image for project: 'Dev - Nexus'
  1. Dev - Nexus
  2. NEXUS-3915

When artifacts are blocked if they fail content validation - no entry is made in the RSS feeds

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.8
    • Fix Version/s: 1.9.1
    • Component/s: System Feeds
    • Labels:
      None

      Description

      Our websense decided that some jars where adult content (Yay!) and nexus detected that the jar was not a jar.
      However nexus made the follwoign entry in the log files

      2010-11-04 17:42:11 INFO [tp-31596370-427] - o.s.n.i.c.MavenArch~ - Failed to parse Maven artifact /home/software/nexus/nexus-pro
      fessional-webapp-1.8.0/./../sonatype-work/nexus/storage/central/org/eclipse/text/3.3.0-v20070606-0010/text-3.3.0-v20070606-0010.jar due to
      error in opening zip file
      2010-11-04 17:42:11 INFO [tp-31596370-427] - o.s.n.i.c.MavenArch~ - Failed to parse Maven artifact /home/software/nexus/nexus-pro
      fessional-webapp-1.8.0/./../sonatype-work/nexus/storage/central/org/eclipse/text/3.3.0-v20070606-0010/text-3.3.0-v20070606-0010.jar due to
      error in opening zip file

      But there was no entry in any of the following feeds
      Error and Warning events
      Broken artifacts in all Nexus repositories (...)
      Broken files in all Nexus repositories (...)

      So if you are monitoring these feeds then everything looks healthy, and it is not until you resort to the logs that you see something is wrong.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cstamas Tamás Cservenák
                Reporter:
                teilo James Nord
                Last Updated By:
                Jason Dillon
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: