Deployment of site.xml

Description

The distribution module deploys a file called site.xml. The "pom" packaging lifecycle automatically deploys this file to be used for site inheritance. Nexus complains about this because the file deployed during the release is identical to the file in the snapshots repository, and this violates a Nexus validation that checks that every deployed artifact is unique.

One solution to this is to add a current version string to the site.xml file.

Attachments

1
  • 04 Aug 2010, 11:47 PM

Activity

Show:
Steve Ebersole
changed the StatusAugust 5, 2010 at 5:53 PM
In Progress
Closed
Steve Ebersole
updated the Fix versionsAugust 5, 2010 at 5:53 PM
None
3.5.5
Steve Ebersole
updated the ResolutionAugust 5, 2010 at 5:53 PM
None
Fixed
Steve Ebersole
updated the Remaining EstimateAugust 5, 2010 at 5:52 PM
0h
0h
Steve Ebersole
updated the Time SpentAugust 5, 2010 at 5:52 PM
0h
0.58h
Steve Ebersole
changed the StatusAugust 5, 2010 at 5:17 PM
Open
In Progress
Steve Ebersole
changed the AssigneeAugust 5, 2010 at 5:05 PM
Unassigned
Steve Ebersole
Steve Ebersole
updated the Fix versionsAugust 5, 2010 at 5:05 PM
None
3.6.0.Beta3
Steve Ebersole
updated the LinkAugust 5, 2010 at 5:05 PM
None
This issue relates to HHH-5438
Former user
added an AttachmentAugust 4, 2010 at 11:47 PM
None
HHH-5439-site-xml.patch
Former user
created the IssueAugust 4, 2010 at 11:46 PM
Fixed

Details

Assignee

Reporter

Time tracking

0.58h logged

Fix versions

Priority

Created August 4, 2010 at 11:46 PM
Updated August 5, 2010 at 5:53 PM
Resolved August 5, 2010 at 5:53 PM

Flag notifications