java - pimp up a plain jar to be a maven jar with internal pom.xml for Artifactory -
i need use xyz.jar wich generated ant. hence, transitive dependencies missing. had idea, modify xyz.jar add internal meta-inf/maven/groupid/artifactid/pom.xml , pom.properties files.
when deployed artifactory, ignored them , generated it's own pom.xml without dependencies.
what has 1 do, artifactory deploys pom.xml lying in same folder xyz.jar file?
lost way time on allready...
chances artifactory skips deployment of internal pom because cannot read pom's physical size archive (done historical reasons); can verify looking @ log warning message along lines of:
"found pom.xml file size -1 inside zip. ignoring"
if you've gone lengths of creating customized pom file, can paste it's contents in pom content editor of artifact deployer or deploy independently; though first option give benefit of auto detecting deployment coordinates jar file.
Comments
Post a Comment