Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.0-m5
-
Fix Version/s: 3.0.0-m5
-
Component/s: Maven, Repository
-
Labels:None
-
Environment:(Chrome MacOSX)
-
Story Points:0.5
-
Sprint:Sprint 47
Description
While testing NEXUS-8255, Stuart McCulloch noticed that in one of my tests, I had uploaded a SNAPSHOT pom and then uploaded it again to see if the fields were updating in the UI but that LastModified was not being updated either in the DB or in the UI.
He writes:
"looking at the code in MavenFacetImpl it only updates the last-modified time if this is the first time the file was deployed, or the content attributes passed along with the payload contain a last-modified time. I couldn't spot anywhere that sets the last-modified time in the content attributes before they reached the put method, so this looks like a bug (or there's some code missing). This explains why you didn't see the last-modified time change when you deployed the file again. Also note that when you re-deploy a Maven artifact it will keep the same asset record, but update the blob field in that record to point to the new content."
Since this is a deeper issue than just asset details, I am filing seperately.
I have not checked older NX3 at this time, nor have I checked NX2.
I also haven't checked other repo types at this time either so only put the Maven component above.
Attachments
Issue Links
- fixed by
-
NEXUS-8914 NX3 proxy fetches more than should
-
- Closed
-