Hi!
I came across MRM-799 (Better handling of artifacts with missing pom). I
suggest that a POM is created with at least the basic information such
as the groupId, artifactId, and version whenever an artifact (without
POM) is selected in Browse. The POM created is not necessarily put in
the filesystem so that it will not violate the purpose of "Generate POM"
option in Upload when not selected. This should allow the users to
view/download the artifact even without the presence of the POM.
Another approach is to have a field in the database that would track
artifacts with no POM. This field can also be used to monitor repository
health and also be able to deal with this issue before an exception is
thrown (not allowing artifacts to be viewed/downloaded).
--
Thanks
Jevica Arianne B. Zurbano
Software Engineer | Exist Global | +6332 412 1155 | YM: exst_jzurbano |
www.exist.com | Innovation Delivered
