You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[MASSEMBLY-1033] Optionally create an accompanying checksum file #1240
For me this violates a basic principal: do one thing and do it good. The same applies to m-source/jar/javadoc-p. There is a specialized plugin for the usecase depicted here.
The plugin Michael Osipov pointed at creates checksum for attached artifacts, while user asks for "a file containing a checksum line for each file in assembly.zip". That does not seems related to me, nor provides the information for user. Or do I miss something?
Activity
jira-importer commentedon Mar 10, 2025
Michael Osipov commented
For me this violates a basic principal: do one thing and do it good. The same applies to m-source/jar/javadoc-p. There is a specialized plugin for the usecase depicted here.
jira-importer commentedon Mar 11, 2025
Martin Lichtin commented
Which one do you have in mind? I did quite a bit of searching around, but couldn't find one.
The assembly plugin seemed like an ideal place to do this, as it creates the assembly and with it the sha file.
jira-importer commentedon Mar 12, 2025
Michael Osipov commented
https://github.com/apache/maven-apache-parent/blob/f613f1ab0ddc5060401a17806674d4ca685161f3/pom.xml#L454-L481
jira-importer commentedon Mar 12, 2025
Tamas Cservenak commented
The plugin Michael Osipov pointed at creates checksum for attached artifacts, while user asks for "a file containing a checksum line for each file in assembly.zip". That does not seems related to me, nor provides the information for user. Or do I miss something?
jira-importer commentedon Mar 12, 2025
Michael Osipov commented
Darn, I have totally misread the usecase...
jira-importer commentedon Mar 12, 2025
Martin Lichtin commented
currently we're doing this with the help of two other plugins