Dev - Nexus
  1. Dev - Nexus
  2. NEXUS-3743

Bad SHA1 created for ivy.xml artifact

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Not A Bug
    • Affects Version/s: 1.7.2
    • Fix Version/s: None
    • Component/s: Repository
    • Labels:
      None
    • Environment:
      Uname -a: 5.11 snv_111b i86pc i386 i86pc Solaris

      Description

      Artifact 'ivy.xml' has a SHA1 checksum of: 'e779e3e74363e546fc22e1550b3655fd6684d4a3' when created by the Ant task '<checksum algorithm="sha1">' This checksum is also recognized by Ivy (2.1.0) as correct.

      When 'Rebuild Metadata' is called from the Nexus GUI, a bad SHA1 checksum is created: 'b3357dd9e151664bdea85112311448957ec8f51f'

      This problem ONLY occurs if the artifact is named 'ivy.xml'. If you rename the file to anything else the checksum is correctly generated by the 'Rebuild Metadata' call in Nexus.

      The ivy.xml file is attached.

      1. ivy.xml
        0.9 kB
        Todd Merrill
      2. test.ivy.xml
        1 kB
        Christian Höfig

        Activity

        Hide
        Tamás Cservenák added a comment -

        Yes, deleting the attribute along with content (or deleting the attribute along with modifying content) should "fix" this.

        "Fix", as in a moment you think about potential concurrency issues... (Nexus might be serving up the exact file you are modifying/deleting).

        Show
        Tamás Cservenák added a comment - Yes, deleting the attribute along with content (or deleting the attribute along with modifying content) should "fix" this. "Fix", as in a moment you think about potential concurrency issues... (Nexus might be serving up the exact file you are modifying/deleting).
        Hide
        Todd Merrill added a comment -

        Not really a problem for us, since if we're having to edit the file our inbox is already full to the brim with messages from angry developers

        Thanks very much for the help, Tamás!

        I realize this isn't how Nexus is normally used, but I doubt many Nexus users serve both ivy and maven descriptors to their teams either. Despite directly messing with the repository, Nexus is mostly stable.

        Show
        Todd Merrill added a comment - Not really a problem for us, since if we're having to edit the file our inbox is already full to the brim with messages from angry developers Thanks very much for the help, Tamás! I realize this isn't how Nexus is normally used, but I doubt many Nexus users serve both ivy and maven descriptors to their teams either. Despite directly messing with the repository, Nexus is mostly stable.
        Hide
        Tamás Cservenák added a comment -

        One thing you should consider: same stands for Nexus as for Maven (in broadest sense): I believe what you have there should be a Nexus plugin (same is said for Maven, Mojo mojo mojo...)

        You problem is perfect fit for "capabilities", similar to one that publishes Maven artifacts as OSGi bundles. Not really related, but you can read more about it here:
        https://docs.sonatype.org/display/Nexus/Nexus+OSGi+Experimental+Features+-+Bundle+Maker

        With "similar", I meant, that this plugin above does similar, as in it exposes OSGi bundles "on top" of a Maven2 repository... just like you do with Ivy on top of Maven2 repo...

        Show
        Tamás Cservenák added a comment - One thing you should consider: same stands for Nexus as for Maven (in broadest sense): I believe what you have there should be a Nexus plugin (same is said for Maven, Mojo mojo mojo...) You problem is perfect fit for "capabilities", similar to one that publishes Maven artifacts as OSGi bundles. Not really related, but you can read more about it here: https://docs.sonatype.org/display/Nexus/Nexus+OSGi+Experimental+Features+-+Bundle+Maker With "similar", I meant, that this plugin above does similar, as in it exposes OSGi bundles "on top" of a Maven2 repository... just like you do with Ivy on top of Maven2 repo...
        Hide
        Todd Merrill added a comment -

        Yes, ideally a more integrated solution would be better. Nexus should be controlling all the interactions with the repository. But as usual, it's hard to find the time...

        Show
        Todd Merrill added a comment - Yes, ideally a more integrated solution would be better. Nexus should be controlling all the interactions with the repository. But as usual, it's hard to find the time...
        Hide
        Peter Lynch added a comment -

        After the reading the long set of comments, this looks like Nexus is performing as designed and that this is acceptable.

        Show
        Peter Lynch added a comment - After the reading the long set of comments, this looks like Nexus is performing as designed and that this is acceptable.

          People

          • Assignee:
            Peter Lynch
            Reporter:
            Todd Merrill
            Last Updated By:
            Peter Lynch
          • Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

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