My Maven projects all include configuration to produce a DEB and an RPM (rpm-maven-plugin, of course). I'm not terribly excited about pouring over the maven docs in as much detail as required to answer this myself, but is there anything special about how the jdeb plugin identifies it's .deb artifact to the maven project? I ask because jdeb associates the package it creates as a formal build artifact. My Jenkins server provides direct link to it alongside the JAR. Is there any configuration that I can include to have this plugin do the same?
My Maven projects all include configuration to produce a DEB and an RPM (rpm-maven-plugin, of course). I'm not terribly excited about pouring over the maven docs in as much detail as required to answer this myself, but is there anything special about how the jdeb plugin identifies it's .deb artifact to the maven project? I ask because jdeb associates the package it creates as a formal build artifact. My Jenkins server provides direct link to it alongside the JAR. Is there any configuration that I can include to have this plugin do the same?